implementation-scoutlisted
Install: claude install-skill shouvik12/implementation-scout
# Implementation Scout
Find the smallest set of verified existing implementations that
covers the user's workflow — repo, file, function, and a version pin
(tagged release when available) — plus license, and where the fix
actually belongs versus adjacent layers that look plausible but
aren't it.
**This is Phase 1 (MVP).** It relies on `api.github.com` and
`web_fetch`/`web_search` — no semantic search, no AST parsing, no
vector DB. Earlier testing sessions found `api.github.com/search/code`
returning 401 without a token, and raw file / commit-history URLs
unreachable via `web_fetch` unless they'd already appeared in a
`web_search` result — but **tool behavior can change between runs,
and these must be re-verified fresh each session, not assumed from
this note** (see "Tool capability is a runtime fact," below). Evidence
precision — whether line ranges, commit SHAs, and provenance are
achievable — depends on what actually works *this run*, tested at the
time, not on a fixed rule about tokens. The skill should work well
either way, citing the strongest evidence path that actually succeeds.
## Hard rule: no unverified claims
This is the most important part of the skill. Every one of these must
come from an actual tool call result in this run, not from training
knowledge:
- repository name / owner
- star count
- file path
- function/class name
- license
If something can't be verified with a tool call, do not state it as
fact. Write `not verified` and say what would need to ha