agentleFS
Sign inStart free
amtiYoamtiYo/agents/.agents/skills/skill-guide/SKILL.md

skill-guide

Skill102 starsChanged 2 months agoApache-2.0View on GitHub

Explain how to create, organize, and maintain skills in .agents/skills when the user asks about skills.

6 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions6 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 6

    1. VV1NN/skill-guide★ 5same name
    2. AttackXiaoJinJin/best-claude-skills★ 1same name
    3. gtskevin/skill-guide★ 1same name
    4. psw7205/skills★ 1same name
    5. taecontrol/skills★ 1same name
    6. vancebs/skills★ 1same 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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    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:

    When asked about skills:

    line 6
  2. Distinctive:

    put large references/examples in separate files.

    line 23
  3. Distinctive:

    no secrets in skill files,

    line 28

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

When asked about skills:

  1. Explain required structure:
  • One directory per skill under .agents/skills.
  • A required SKILL.md file with YAML frontmatter.
  1. Explain required frontmatter:
  • name: short unique identifier.
  • description: explicit trigger guidance for when the skill should be used.
  1. Provide a minimal starter template and ask for:
  • the task scope,
  • expected input/output,
  • success criteria.
  1. Recommend progressive disclosure:
  • keep SKILL.md concise,
  • put large references/examples in separate files.
  1. Suggest validation checklist:
  • clear trigger description,
  • deterministic steps,
  • no secrets in skill files,
  • tested with at least one real prompt.

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