agentleFS
Sign inStart free
lc-rezendelc-rezende/AI-Custom-Skills/sample-skill/SKILL.md

sample-skill

Skill1 starsChanged 8 months agoApache-2.0View on GitHub

Provide a short, repeatable workflow for adding and documenting a new skill in this repository. Use when creating a new skill folder or updating skill documentation.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. microsoft/win-dev-skills★ 469same name
    2. awaku7/agentcli★ 12same name
    3. Sdinzsh/PowerHou53★ 4same name
    4. agent-plaza/agent-plaza★ 3same 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a new folder using lowercase letters, numbers, and hyphens.

    line 8
  2. Very specific:

    Add a SKILL.md with required frontmatter and concise instructions.

    line 9
  3. Distinctive:

    Keep the file under 500 lines and under 5,000 tokens.

    line 10
  4. Very specific:

    Add optional references/, scripts/, or assets/ only if needed.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Workflow

  1. Create a new folder using lowercase letters, numbers, and hyphens.
  2. Add a SKILL.md with required frontmatter and concise instructions.
  3. Keep the file under 500 lines and under 5,000 tokens.
  4. Add optional references/, scripts/, or assets/ only if needed.
  5. Validate the skill with skills-ref validate ./path-to-skill.

Output expectations

  • The skill folder follows the Agent Skills specification.
  • The SKILL.md description states what the skill does and when to use it.

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