agentleFS
Sign inStart free
yacb2yacb2/aidex/skills/skill/SKILL.md

skill

Skill2 starsChanged 33 days agoMITView on GitHub

Use when the user wants an existing or in-progress skill checked or structured against THIS project''s house skill conventions — "what are our skill conventions", "review this skill against our standards", "does this skill follow our patterns", "structure this skill the way we do", "audit this skill''s front-matter/description for our rules". Not for: creating a skill from scratch, optimizing a skill''s description for triggering, or running skill evals (all skill-creator); planning (/aidex:plan); decisions (/aidex:decision); requests (/aidex:request); research (/aidex:research); references (/aidex:reference); ecosystem audits (/aidex:aidex).

62 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-slop-cleaner, ralplan and 10 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.
  • Jurel89Skill

    ai-slop-cleaner

    Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

    Also in 5 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 5 projects that use this

  • ibahgatSkill

    hud

    Control omi visual HUD profile and keep status output readable in normal, compact, or hidden mode.

    Also in 5 projects that use this

  • Jurel89Skill

    ultraqa

    QA cycling loop — build/lint/test, fix, retry up to 5 cycles

    Also in 3 projects that use this

  • LucasCooperBeySkill

    visual-verdict

    Structured visual QA verdict for screenshot-to-reference comparisons. Returns JSON scores driving edit iterations. Use after any UI implementation to verify visual fidelity.

    Also in 3 projects that use this

  • Yeachan-HeoSkill

    ultragoal

    Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    Read the skill conventions canon: ${CLAUDE_PLUGIN_ROOT}/skills/conventions/references/skill-conventions.md (or the .claude/skills/...

    line 16

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

Surface and apply this project's house skill conventions to an existing or in-progress skill. This skill COMPLEMENTS skill-creator (it does not create skills from scratch).

Workflow

  1. Read the skill conventions canon: ${CLAUDE_PLUGIN_ROOT}/skills/conventions/references/skill-conventions.md (or the .claude/skills/... project-level copy if one exists).
  2. Identify the target skill the user is reviewing or structuring.
  3. Produce a gap report against the canon: front-matter (trigger-first description, char budget, English-only description, disable-model-invocation, allowed-tools), body structure, evals/ presence, no per-skill CHANGELOG.md/README.md.
    • English-only check (canon skill-conventions.md rule 2): the description must contain no Spanish/other-language phrasings or accented tokens. The matcher bridges cross-lingually, so an English description still fires on non-English queries; native-language queries belong in the evals/ query set, not the description. Flag any non-English phrasing as a gap and rewrite the description English-only, preserving semantic coverage (drop the foreign phrasings; keep their English equivalents).
  4. Writes go only to the target skill's own files (SKILL.md, evals/) — never to the canon under references/, which this skill reads read-only.

Boundaries

The user wants to…Route to
Create a skill from scratch / optimize a description / run skill evalsskill-creator
Plan multi-step / multi-phase implementation workplan
Record a decision / ADRdecision
Capture a stakeholder/client requestrequest
Investigate / research how something worksresearch
Document a settled system referencereference
Audit the Claude Code ecosystemaidex

Related

  • skill-creator — owns skill creation, description optimization, and eval running; this skill only checks/applies house conventions.
  • conventions — owns the shared documentation canon (this skill reads its references/skill-conventions.md).

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