agentleFS
dvy1987dvy1987/agent-loom/.agents/skills/skill-finder/SKILL.md

skill-finder

Skill4 starsChanged 3 months agoMITView on GitHub

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.

28 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 1 is distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never create a new skill if an existing skill can be extended.

    line 28
  2. Very specific:

    Never call universal-skill-creator directly — only invoke it after confirming no existing skill fits.

    line 29
  3. Very specific:

    Always read docs/SKILL-INDEX.md before making any decision — do not rely on memory of skill names.

    line 30
  4. Very specific:

    Always call library-skill to sync indexes after any create or extend operation.

    line 31
  5. Very specific:

    Read .agents/skills/ directory listing and docs/SKILL-INDEX.md descriptions.

    line 39
  6. Very specific:

    If extending: verify the target skill stays <=200 lines after extension.

    line 53
  7. Very specific:

    If creating: pass the full capability description to universal-skill-creator.

    line 55
  8. Very specific:

    After any create or extend: call library-skill to sync docs/SKILL-INDEX.md, AGENTS.md, and README.md.

    line 59
  9. Very specific:

    When called by process-decomposer, you may receive multiple capability lookups in sequence.

    line 71
  10. Very specific:

    No existing skill handles process/architecture evaluation.

    line 86
  11. Distinctive:

    No changes — citation audit passed.

    line 127

“Common” is measured: kept by at least 6 in 10 of the 26 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.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:

MatchAction
Full overlap — existing skill does exactly thisReturn 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 fitsCall 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

ExcuseReality
Invent skill inlineRoute to universal-skill-creator for new skills.
First match onlyList top 2–3 with disambiguation.
Ignore project skillsCheck local .agents/skills first.
Skip INDEXdocs/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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.