tool-sourcinglisted

# Sourcing a tool When work stalls on a missing capability, the ecosystem has probably already solved it. This skill sources an existing skill and installs it, rather than building one - creating from scratch (`/self-extension`) is the fallback for when nothing adequate turns up, not the first move. The `skills` CLI (`npx skills find | use | add`) does the heavy lifting: its installer is genuinely hardened (path-traversal and digest guards, agent-agnostic, symlink-with-copy-fallback), so ride it rather than rebuild it. But its *discovery* is thin - it searches one central index, ranks purely by install count, and returns an empty list on any error, so an outage looks identical to "no such skill." The care in this skill is all in wrapping that discovery: search wider, distrust the ranking, and never let an empty result quietly conclude the capability doesn't exist. Read `.better-dev/overrides.md` first and honor any project override - a repo may pin an internal skills registry, forbid third-party installs, or already name the tool it wants for a given job. ## 1. Name the gap Write down, in one line, the capability that's missing and what would prove it filled - the observable check the sourced tool has to pass (e.g. "drives a headless browser and returns a screenshot", "runs the iOS simulator"). That line is both the search query and the acceptance test; without it, "found something" drifts into "found anything." ## 2. Discover - widen past the one index Start with `npx