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 |
references/install-commands.md
View on GitHub# Install commands & scope mechanics
The full menu skill-scout emits once it has a verdict. The SKILL.md body keeps only the three
common forms; the rest lives here so the body stays a decision tool.
## Where Claude Code looks for skills
The available-skills list is built by scanning, in order:
- **User scope** — `~/.claude/skills/<id>/SKILL.md`. Available in *every* project on this machine.
- **Project scope** — `.claude/skills/<id>/SKILL.md`. Version-controlled with the repo; available
only inside it. A project-scope skill of the same id shadows a user-scope one.
- **Plugin-provided** — skills bundled in an installed plugin/marketplace.
- **Built-ins** — shipped with the harness.
"Present but not here" is therefore a real gap: a skill at user scope is invisible inside a repo
that doesn't pick it up, and a skill committed to one repo's `.claude/skills/` does not follow you
to another.
## Choosing scope (the only decision that matters here)
| Choose **User** (`~/.claude/skills/`) when… | Choose **Project** (`.claude/skills/`) when… |
| --- | --- |
| The skill is general-purpose — you'll want it across repos | The skill encodes this repo's conventions / endpoints |
| It is your personal tooling, not the team's | It should travel with the code for everyone who clones |
| You don't want it in version control | You want it reviewed and versioned in the repo |
Default heuristic: **broad reuse → user; repo-specific → project, committed.**
## Form 1 — plugin marketplace
When the skill is published in a marketplace repo:
```bash
/plugin marketplace add <user>/<repo> # register the marketplace once
/plugin install <name>@<marketplace> # install the named skill from it
```
## Form 2 — interactive browser
When you'd rather browse and pick scope by hand:
```bash
/plugin # opens the plugin UI
# → Discover tab → find the skill → Install
# → choose User (all projects) or Project (this repo) scope
```
## Form 3 — direct file drop
When you already hold the `SKILL.md` (e.g. copying from another project or a tarball):
```bash
# project scope (committed with the repo)
mkdir -p .claude/skills/<id>
cp -R <source>/<id>/* .claude/skills/<id>/
# user scope (all projects)
mkdir -p ~/.claude/skills/<id>
cp -R <source>/<id>/* ~/.claude/skills/<id>/
```
## Form 4 — curl | tar (remote tarball)
When the skill ships as a downloadable archive rather than a marketplace entry:
```bash
mkdir -p .claude/skills/<id>
curl -fsSL <url>/<id>.tar.gz | tar -xz -C .claude/skills/<id> --strip-components=1
```
## After installing
The new skill is picked up on the next session/scan. Confirm the description is trigger-rich enough
to actually fire — a freshly installed skill with a weak description is still an invisible gap.
If the description is vague, that is an author-skill job, not a re-install.
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 |