agentleFS
farky-techfarky-tech/containers/skills/capability-audit/SKILL.md

capability-audit

Skill1 starsChanged 4 months agoMITView on GitHub

Use to compare declared container capabilities with actual skills, subagents, hooks, tools, and recent fallback reports.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Rtur2003/Claude-Code-Promts-Skills★ 53same name
    2. snapsynapse/ai-tool-watch★ 11same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when capabilities feel forgotten, routing is noisy, fallback repeats, or the container's project files drift from actual runtime …

    line 15
  2. Very specific:

    Read memory/CAN.md if present.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Capability Audit

When To Use

Use when capabilities feel forgotten, routing is noisy, fallback repeats, or the container's project files drift from actual runtime support.

Procedure

  1. Read memory/CAN.md if present.
  2. Compare against available skills/subagents/hooks/tools — verify availability from the real runtime (settings, agent list, ls, tool search), not from memory or from what an index claims.
  3. Review recent fallback reports.
  4. Identify dead, missing, noisy, or un-routed capabilities.
  5. Propose patches, not broad rewrites.

Rule: separate "not available" from "not checked" from "written from memory." A capability that is listed but was never verified against the real runtime is itself an audit finding.

Output

Capability audit:
- Declared but missing:
- Available but not routed:
- Routed but too noisy:
- Repeated fallback:
- Patch candidates:

Run

From the plugin root, run:

bash scripts/capability_audit.sh

This script is the executable enforcement of the declared-vs-actual rule described by this skill. It compares the declarations in manifest.yaml with the plugin files and supported runtime checks.

Exit codes:

  • 0 = no drift.
  • 1 = drift found, including missing declared capabilities.

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.