use-cli-scout
Web search, page fetch, and GitHub repo exploration via scout CLI.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Web search, page fetch, and GitHub repo exploration via scout CLI.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
issue が build に投入できる形かを検分し、verdict (build-ready / needs-plan / needs-fix) と指摘を返す。起票には使わない (/issue)。PR のスクリーニングには使わない (/preview)。
Inspect whether an issue is in shape to hand to build, returning a verdict (build-ready / needs-plan / needs-fix) and the findings. Do NOT use to file an issue (use /issue) or to screen a PR (use /preview).
critic-design による敵対的批判を伴う設計探索。生き残った案を構造化 plan にまとめ、自己点検して呼び出し元に返す。plan の永続先は issue の Plan 節が唯一。計画意図のないコードベース調査には使わない (代わりに /research)。
Design exploration with adversarial critique by critic-design. Assembles the surviving approach into a structured plan, self-checks it, and returns it to the caller. The issue's Plan section is the plan's only persistent home. Do NOT use for codebase investigation without planning intent (use /research instead).
構造化されたタイトルと本文で GitHub Issue を生成する。単独で成立し、前段を要求しない。challenge / research の成果物が会話にあれば本文の根拠に使い、/think の plan 下書きがあれば `## Plan` 節へ移設する。issue 番号を渡すと、起票済みで Plan 節を持たない issue へ plan を転記する。
Generate GitHub Issue with structured title and body. Standalone; requires no upstream stage. When challenge / research artifacts exist in the conversation, they feed the body's evidence; when a /think plan draft exists, it is transferred into the `## Plan` section. Given an issue number, it transfers a plan into a filed issue that has no Plan section.
| name | use-cli-scout |
| description | Web search, page fetch, and GitHub repo exploration via scout CLI. |
| when_to_use | web search, page fetch, deep research, GitHub repo exploration, latest docs, release notes, library docs, external info, WebFetch alternative, WebSearch alternative, 最新ドキュメント, リリースノート, 外部情報 |
| allowed-tools | Bash Read |
| user-invocable | false |
| Purpose | Command |
|---|---|
| Web search | scout search "query" |
| Fetch page | scout fetch <url> |
| Deep research | scout research "topic" |
| Repo tree | scout repo-tree <owner/repo> |
| Repo read | scout repo-read <owner/repo> <path> |
| Repo overview | scout repo-overview <owner/repo> |
Required environment variables, options, the --json envelope, exit codes, stdin input, and examples are all written in scout --help and scout <subcommand> --help. When answering about scout itself, answer from the installed version's help output rather than from this skill or from training knowledge. When the two disagree, help wins.
| Situation | Command to run |
|---|---|
| Environment variables, exit codes, global flags | scout --help |
| A subcommand's arguments and flags | scout <subcommand> --help |
| A run failed with exit 64 (missing API key too) | Read the Environment section of scout --help |
| use-cli-scout | Built-in WebFetch / WebSearch |
|---|---|
| Latest docs, release notes | Never; scout preferred |
| GitHub repository exploration | Never; scout repo-* preferred |
| Deep research with compiled report | Unavailable; use scout research |
| Markdown-clean page extraction | WebFetch lacks Markdown conversion |