メニュー
Replacement for the built-in WebFetch tool on backends where it is unavailable (this platform's non-Anthropic backends). Fetches a URL and extracts its main content as markdown. Use it when WebFetch is denied and the harness tells you to use this skill, or when you otherwise need to fetch a page.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement a feature from the plan that plan-feature produced under docs/plan/<feature>/, one reviewed sub-issue at a time. Use when the user wants to implement or build a feature from a docs/plan/<feature>/ plan or a planned GitHub issue.
Turn a GitHub issue into an implementation plan under docs/plan/<feature>/: a feature spec decomposed into context-window-sized sub-issues, committed as the first commit of the feature branch with a draft PR. Use when the user wants to plan a feature, decompose a GitHub issue into sub-issues, or produce an implementation plan from an issue.
Template and writing guidelines for a GitHub issue. Every issue is one of epic, feature, task, bug, or research task — the user decides the type, and each type has its own template. Non-epic types can suggest a parent epic from the project board.
Draft a GitHub issue, get explicit user approval, and file it via the `gh` CLI. TRIGGER when: user wants to file or "drop" a GitHub issue / ticket.
Check and align a repo's .claude/settings.json and CLAUDE.md with team conventions. Use when the user wants to standardize a repo, align conventions, check settings, or bootstrap Claude Code config in a new project.
Use this skill whenever writing, editing, reviewing, or refactoring TypeScript React code — components, custom hooks, state stores, forms, queries, mutations, API clients, or styling. Trigger it for any task touching a `.ts` or `.tsx` file in a React project, including when the user says "add a feature", "fix this bug", or "clean this up" inside a component or hook. Also use it for architectural questions about React codebases: where state should live, whether a component is too big, how to organize modules, when to reach for TanStack Query, Zustand, React Context, or React Hook Form.
| name | webfetch |
| description | Replacement for the built-in WebFetch tool on backends where it is unavailable (this platform's non-Anthropic backends). Fetches a URL and extracts its main content as markdown. Use it when WebFetch is denied and the harness tells you to use this skill, or when you otherwise need to fetch a page. |
| allowed-tools | Bash(node *) |
On this platform's non-Anthropic model backends the built-in WebFetch tool
doesn't work (it relies on an Anthropic server-side capability), so the harness
denies it and directs you here. This skill fetches the page locally and
extracts the readable content as markdown. (On genuine Anthropic backends the
built-in works and this skill is unnecessary.)
Pipe a JSON request to the fetch script on stdin:
echo '{"url":"URL","prompt":"QUESTION"}' | node /opt/cc-websearch/webfetch.cjs
The request accepts:
url (string, required, must be a valid URL) — the page to fetchprompt (string, required) — the question to answer about the pageThe script writes the extracted page content to stdout; errors and diagnostics go to stderr. HTTP URLs are upgraded to HTTPS. Cross-host redirects are reported but not followed. Only HTML content types are supported.
Fetching an arbitrary host may require a one-time egress approval for that host before it succeeds. Use the returned content to answer the user's question.