ericrisco/rsc-harness / skills/skill-scout
skill-scout
VerifiedUse when a specialized skill probably exists but is not loaded, when a task feels harder than it should because generic reasoning is doing a domain skill's job, when the work just delivered was a repeatable procedure worth turning into a skill or an agent, or when auditing coverage for holes. Resolves against what already exists — installed skills, catalog skills and agent files — then names the gap and emits the install command. NOT routing among skills you already have (that is `suggest`), NOT writing the artifact when none exists (that is `author-skill` for skills, `building-agents` for agents).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.2 KB |
| evals/README.md | markdown | 1010 B |
| evals/cases.yaml | config | 4.0 KB |
| references/install-commands.md | markdown | 2.9 KB |
| scripts/verify.shexecutable | script | 7.6 KB |
evals/README.md
View on GitHub# skill-scout evals — how to run
`cases.yaml` is read by the catalog eval runner. The `should_trigger` / `should_not_trigger` sets
check the description's routing precision: each `should_trigger` prompt should pull this skill in,
and each `should_not_trigger` prompt should route to its named sibling instead (the sharp edges are
against `suggest` — routing among skills you already have — and `author-skill` — writing the skill
that doesn't exist; the rest guard `context-budget`, `continuous-learning`, and `knowledge-ops`).
The `capability` case is a manual/LLM-graded rubric: run the scenario with the skill loaded and
confirm every `must_include` line is satisfied — especially that it never fabricates a catalog id
and never does the implementation itself. No network or credentials needed; everything is local and
static. To sanity-check the optional artifact path, run `scripts/verify.sh` against a directory
containing a `skill-gaps.jsonl` (it is a clean no-op on an empty or absent file).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |