agentleFS
LandonTomaineLandonTomaine/LT-Agents/skills/audit-skills/SKILL.md

audit-skills

Skill0 starsChanged 4 months agoMITView on GitHub

Audit Codex skills for DRYness, brevity, trigger quality, progressive disclosure, and unnecessary duplication of always-loaded or tool-provided guidance. Use when the user asks to review, trim, tighten, de-duplicate, or improve one or more skills, especially when deciding what belongs in SKILL.md versus nearby references, scripts, or assets.

9 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

12 rules. 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Read only the targeted SKILL.md files and directly relevant nearby resources.

    line 20
  2. Distinctive:

    Use only the sections that match the current audit.

    line 24
  3. Distinctive:

    Prefer short bullets or fragments when clear.

    line 37
  4. Very specific:

    Keep core workflow guidance in SKILL.md.

    line 40
  5. Distinctive:

    Verify before calling something redundant.

    line 44
  6. Distinctive:

    Do not assume a rule is always loaded.

    line 46
  7. Distinctive:

    If the task includes fixes, make focused edits.

    line 49
  8. Distinctive:

    Prefer deletion over rewriting, and rewriting over expansion.

    line 50
  9. Very specific:

    If the skill is already concise and useful, say no change needed.

    line 51
  10. Distinctive:

    Do not manufacture low-value findings.

    line 63
  11. Distinctive:

    Do not preserve full sentences just because they read better.

    line 64
  12. Distinctive:

    Do not create cosmetic edits to avoid an empty audit.

    line 65

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

Audit Skills

Primary lens: Review.

Goal

Review skills as compact operating guides, not mini handbooks.

Bias hard toward brevity. Keep only wording that changes behavior, routing, or risk.

Workflow

  1. Scope first.
    • Identify the skill or skill set to review.
    • Read only the targeted SKILL.md files and directly relevant nearby resources.
  2. Load the checklist after the scope is clear.
    • Read references/audit-checklist.md.
    • Use only the sections that match the current audit.
  3. Audit for trigger quality.
    • Description says what the skill does and when to use it.
    • Invocation is not broader than the workflow.
  4. Audit for DRYness and context discipline.
    • Repeated always-loaded rules.
    • Repo guidance that belongs in repo docs.
    • Duplicated text across SKILL.md, references/, and scripts.
  5. Audit for brevity first, not style polish.
    • Cut filler, throat-clearing, duplicated framing, and obvious statements.
    • Prefer short bullets or fragments when clear.
  6. Audit for progressive disclosure.
    • Keep core workflow guidance in SKILL.md.
    • Move details, examples, and checklists to nearby references/.
    • Move repeatable deterministic work to scripts/ instead of spending tokens on long instructions.
  7. Verify before calling something redundant.
    • Point to where the duplicated guidance already lives.
    • Do not assume a rule is always loaded.
  8. Edit or report.
    • If the task includes fixes, make focused edits.
    • Prefer deletion over rewriting, and rewriting over expansion.
    • If the skill is already concise and useful, say no change needed.

Output

  • the skills reviewed
  • findings ordered by impact
  • file paths that support each finding
  • whether each issue is trigger drift, repeated always-loaded guidance, repeated repo guidance, over-verbose body content, misplaced detail that should move to references/ or scripts/, duplication, or template residue
  • a final conclusion: fix now, defer with rationale, or no change needed

Do Not

  • Do not manufacture low-value findings.
  • Do not preserve full sentences just because they read better.
  • Do not create cosmetic edits to avoid an empty audit.

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.