agentleFS
Sign inStart free
AndyTechnologiesAndyTechnologies/my-own-skills/skills/skill-improver/SKILL.md

skill-improver

Skill0 starsChanged 38 days agoApache-2.0View on GitHub

Trigger: improve skills, audit skills, refactor skills, skill quality. Audit and upgrade existing LLM-first skills.

19 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 2 are distinctive, and 7 are very specific to this project.

  • 0

    Common

    Most of the 19 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

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

    Use this skill when asked to audit, refactor, normalize, or improve existing SKILL.md files.

    line 12
  2. Very specific:

    Treat docs/skill-style-guide.md as the normative style contract when it exists.

    line 16
  3. Very specific:

    Treat SKILL.md as the source of truth.

    line 18
  4. Very specific:

    Use .atl/skill-registry.md as an index of skill names, triggers, scopes, and exact paths.

    line 19
  5. Distinctive:

    Default to audit-only. Modify files only when the user explicitly asks to apply improvements.

    line 20
  6. Very specific:

    Never delete meaningful content silently.

    line 21
  7. Distinctive:

    Do not invent triggers, policies, or domain rules.

    line 22
  8. Very specific:

    Read docs/skill-style-guide.md.

    line 36
  9. Very specific:

    Read .atl/skill-registry.md.

    line 37

“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

Activation Contract

Use this skill when asked to audit, refactor, normalize, or improve existing SKILL.md files. Use skill-creator instead when creating a brand-new skill from a reusable pattern.

Hard Rules

  • Treat docs/skill-style-guide.md as the normative style contract when it exists.
  • For installed global skills, use references/skill-style-guide.md as the bundled local copy when docs/skill-style-guide.md is unavailable.
  • Treat SKILL.md as the source of truth; preserve author intent, critical rules, activation semantics, and output requirements.
  • Use .atl/skill-registry.md as an index of skill names, triggers, scopes, and exact paths; do not expect generated summaries.
  • Default to audit-only. Modify files only when the user explicitly asks to apply improvements.
  • Never delete meaningful content silently; move long explanation, examples, templates, or schemas into local references/ or assets/.
  • Do not invent triggers, policies, or domain rules. Mark ambiguous cases for human review.

Decision Gates

SituationAction
Missing or invalid frontmatterFix name, quoted one-line description, license, and metadata
Skill reads like tutorial docsConvert to runtime instructions and move background to references/
Body exceeds budgetPreserve rules, move examples/background to supporting files
Branching logic hidden in proseConvert to a compact decision table
Rules conflict or intent is unclearReport the issue; do not rewrite that rule automatically

Execution Steps

  1. Read docs/skill-style-guide.md; if unavailable, read references/skill-style-guide.md; if neither exists, enforce the core LLM-first structure: frontmatter, Activation Contract, Hard Rules, Decision Gates, Execution Steps, Output Contract, References.
  2. Read .atl/skill-registry.md; use listed paths to select skills. If missing, scan known skill directories for */SKILL.md.
  3. For each selected skill, audit metadata, trigger clarity, section order, body budget, actionability, decision gates, output contract, and local references.
  4. Return an audit report grouped by skill with severity and exact proposed changes.
  5. In apply mode, edit only safe issues, preserve content, create supporting files when needed, then rerun or request gentle-ai skill-registry refresh.

Output Contract

Return:

  • Skills audited and paths used.
  • Issues found, grouped by severity.
  • Files changed, if apply mode was requested.
  • Registry refresh recommendation when skill metadata or paths changed.
  • Ambiguities that need human review.

References

  • docs/skill-style-guide.md — normative LLM-first skill style guide for this repo.
  • references/skill-style-guide.md — bundled local copy for installed global skills when the repo doc is unavailable.

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.

Check your setup, free