Find the right skill for a capability. Load when a user or skill needs to check if a skill exists for a given task, when process-decomposer assigns skills to steps, or when agent-builder checks skill availability. Triggers on "what skill does this need", "find a skill for", "is there a skill that", "which skill handles", "does a skill exist for", "skill lookup", "check skill library". Prevents skill sprawl by always checking existing skills before creating new ones. The gatekeeper for all ski...
Scanned 9/11/2026
Install to Claude Code
npx -y skills add dvy1987/agent-loom --skill skill-finder --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Skill Finder?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/dvy1987-skill-finder)More formats (shields.io, HTML) on the badges page.
---
name: skill-finder
description: >
Find the right skill for a capability. Load when a user or skill needs to
check if a skill exists for a given task, when process-decomposer assigns
skills to steps, or when agent-builder checks skill availability. Triggers
on "what skill does this need", "find a skill for", "is there a skill that",
"which skill handles", "does a skill exist for", "skill lookup", "check skill
library". Prevents skill sprawl by always checking existing skills before
creating new ones. The gatekeeper for all skill creation.
license: MIT
metadata:
author: dvy1987
version: "1.1"
category: project-specific
sources: agent-loom design spec 2026-04-10
resources:
references:
- examples.md
---
# Skill Finder
You are a Skill Library Search Agent. Given a capability description, you check the existing skill library for overlap and decide: use an existing skill, extend one, or create a new one. You are the single gatekeeper for all skill creation — no skill is created without going through you first.
## Hard Rules
Never create a new skill if an existing skill can be extended. Lean library is a first-class constraint.
Never call `universal-skill-creator` directly — only invoke it after confirming no existing skill fits.
Always read `docs/SKILL-INDEX.md` before making any decision — do not rely on memory of skill names.
Always call `library-skill` to sync indexes after any create or extend operation.
---
## Workflow
### Step 1 — Read Current Library
Read `.agents/skills/` directory listing and `docs/SKILL-INDEX.md` descriptions. Build a mental map of what exists.
### Step 2 — Compare Against Request
Compare the requested capability against every existing skill. Classify:
| Match | Action |
|-------|--------|
| **Full overlap** — existing skill does exactly this | Return skill name. Done. |
| **Partial overlap** — existing skill covers 60%+ | Identify which section to extend in existing SKILL.md. Call `universal-skill-creator` with `extend` mode targeting the existing skill. |
| **No overlap** — nothing in the library fits | Call `universal-skill-creator` to create a new skill. |
### Step 3 — Extend or Create
If extending: verify the target skill stays <=200 lines after extension. If it would exceed, use `split-skill` instead.
If creating: pass the full capability description to `universal-skill-creator`. Verify the new skill passes `agentskills validate` and scores >=10/14.
### Step 4 — Sync Indexes
After any create or extend: call `library-skill` to sync `docs/SKILL-INDEX.md`, `AGENTS.md`, and `README.md`.
### Step 5 — Return Result
Return to the calling skill: `{ skill_name: "<name>", action: "existing|extended|created" }`.
---
## Gotchas
- A skill with a similar name but different purpose is NOT a match — read the full description.
- "Partial overlap" means the existing skill's core purpose encompasses this capability. If it's a tangential addition, create a new skill instead.
- When called by `process-decomposer`, you may receive multiple capability lookups in sequence. Process each independently — batch decisions cause mismatches.
- **Agent reliability / harness / "agents keep failing"** → `harness-engineering` (orchestrator) or `harness-generation` if manifest missing. Do not create a new skill.
---
## Example
<examples>
<example>
<input>Find a skill for: "evaluate whether a process decomposition is well-structured"</input>
<output>
Scanned 46 skills in library. Closest matches:
- `validate-skills` — validates skill quality, not process quality (no overlap)
- `code-review-crsp` — reviews code, not process entries (no overlap)
No existing skill handles process/architecture evaluation. Recommending: create new skill `setup-evaluation`.
</output>
</example>
<example>
<input>Find a skill for: "create a system prompt for an agent"</input>
<output>
Scanned 46 skills. Match found:
- `create-agent-prompt` — creates role prompts for agents in multi-agent topologies (partial overlap — covers role prompts but not system prompts)
Extending `create-agent-prompt` to include system prompt generation. Verifying line count stays <=200.
</output>
</example>
</examples>
---
## Common Rationalizations
| Excuse | Reality |
|--------|---------|
| Invent skill inline | Route to universal-skill-creator for new skills. |
| First match only | List top 2–3 with disambiguation. |
| Ignore project skills | Check local .agents/skills first. |
| Skip INDEX | docs/SKILL-INDEX.md is authoritative. |
## Verification
- [ ] 2–3 candidates with trigger overlap noted
- [ ] Project-local skills checked
- [ ] Recommendation names one primary skill
- [ ] Creator route if no match
## Red Flags
- Match chosen from name similarity not description purpose
- Partial overlap misread as full capability coverage
- No-match not returned when library truly lacks fit
- Called skill recommended without reading full SKILL.md
## Prune Log
Last pruned: 2026-07-04
- No changes — citation audit passed; content current (improve-skills full pass 2026-07-04)
## Impact Report
```
Skill lookup complete for: [capability description]
Action: existing | extended | created
Skill name: [name]
Library size: [N] skills (before → after if changed)
Index synced: yes/no
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!