agentleFS
cryptofish7cryptofish7/claude-skills/skills/skill-reviewer/SKILL.md

skill-reviewer

Skill1 starsChanged 9 months agoMITView on GitHub

Audit installed skills and agents for bloat, overlap, and improvement opportunities. Use when the user wants to review, audit, list, or improve their skills and agents. Triggers on "review skills", "audit skills", "list skills", "skill review", "improve skills".

24 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use skill-builder, security-review and 2 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • BlockSkill

    skill-builder

    Create, edit, or inspect Berd skills stored as skill folders with SKILL.md files. Use when the user wants to build a new skill, update an existing skill, convert a workflow into a reusable skill, or decide whether instructions, scripts, references, or assets belong in a skill.

    Also in 3 projects that use this

  • SentrySkill

    security-review

    Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.

    Also in 3 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 6 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After presenting all findings, ask the user which changes to apply.

    line 53
  2. Distinctive:

    Don't review this skill (skill-reviewer) unless explicitly asked.

    line 59
  3. Distinctive:

    When estimating tokens, use the rough formula: word count * 1.3.

    line 60
  4. Distinctive:

    If a skill has no issues worth flagging, say so briefly and move on.

    line 61

“Common” is measured: kept by at least 6 in 10 of the 19 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 Reviewer

Inventory all installed skills and agents, then deep-review selected ones for conciseness, clarity, overlap, and token efficiency.

Workflow

Phase 1: Build inventory

Scan all skill and agent locations. For each item, count lines in the main file and any reference files.

Locations:

  • Global skills: ~/.claude/skills/*/SKILL.md + references/*.md
  • Global agents: ~/.claude/agents/*.md
  • Project skills: .claude/skills/*/SKILL.md + references/*.md
  • Project agents: .claude/agents/*.md

Build a table sorted by total lines (largest first):

| Scope   | Name             | Type  | Main Lines | Ref Lines | Total |
|---------|------------------|-------|------------|-----------|-------|
| global  | ci-cd-pipeline   | skill | 120        | 45        | 165   |
| project | bug-bash-update  | skill | 109        | 0         | 109   |
| global  | debugger         | agent | 98         | 0         | 98    |

Phase 2: Ask what to review

Present the table. Ask the user which items to deep-review. They can pick one, several, or "all".

Phase 3: Deep review

For each selected item, read the full content and analyze:

  1. Conciseness — Verbose sections, redundant instructions, unnecessary examples. Flag anything that could be shorter without losing meaning.
  2. Clarity — Ambiguous instructions, missing context, unclear phase transitions. Would another LLM session interpret this correctly?
  3. Scope overlap — Responsibilities duplicated with other skills/agents in the inventory. Note which items overlap and what to consolidate.
  4. Token efficiency — Estimate token count (words * 1.3). Flag sections that consume disproportionate tokens relative to their value.
  5. Structural consistency — Does it follow the same patterns (frontmatter, phases, guidelines) as other skills? Note deviations.

Phase 4: Present findings with rewrites

For each issue, show:

  • Current text (quoted)
  • Problem (one sentence)
  • Suggested rewrite (the improved version)

After presenting all findings, ask the user which changes to apply. Then apply the approved edits.

Guidelines

  • Be specific. "This section is verbose" is useless. "Lines 12-18 repeat the trigger list from the frontmatter" is actionable.
  • Preserve intent. Compress prose, don't change behavior.
  • Don't review this skill (skill-reviewer) unless explicitly asked.
  • When estimating tokens, use the rough formula: word count * 1.3.
  • If a skill has no issues worth flagging, say so briefly and move on.

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.