agentleFS
PromptPartnerPromptPartner/agentsmith/skills/example-skill/SKILL.md

example-skill

Skill173 starsChanged 17 days agoMITView on GitHub

Template/example skill showing the minimal structure. Replace or delete it. Use as a starting point when you want to capture a repeatable workflow as a skill.

50 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use code-review.

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.
  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 37 edited versions we read keep these.

  • 1

    Distinctive

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

    Do the work, following the project's core/ rules (verify before done, no secrets, etc.).

    line 19
  2. Very specific:

    Put supporting files (scripts, references, longer instructions) next to this SKILL.md.

    line 23
  3. Distinctive:

    Delete this example once you've added your own skills.

    line 25

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

Example Skill

This is a working but trivial skill, here to show the shape. Copy this folder, rename it, and rewrite the body with your real workflow.

When this fires

The agent loads this when the task matches the description above, or when you invoke it using the client's supported skill syntax. Keep the description precise — it's the only thing the agent matches on.

Steps

  1. State the goal in one line.
  2. Do the work, following the project's core/ rules (verify before done, no secrets, etc.).
  3. Report the outcome with evidence.

Notes

  • Put supporting files (scripts, references, longer instructions) next to this SKILL.md; they load only when referenced (progressive disclosure — keeps context lean).
  • Delete this example once you've added your own skills.

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.