agentleFS
zcacereszcaceres/skills/_template/SKILL.md

__SKILL_NAME__

Skill7 starsChanged 3 months agoMITView on GitHub

__ONE_LINE_DESCRIPTION__

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

SKILL_NAME

Replace this body with the skill's instructions. The name above MUST match the parent folder name exactly. The description is what Claude Code reads to decide whether to activate the skill — say both what it does and when to use it.

Optional frontmatter fields:

  • when_to_use — extended activation rules
  • allowed-tools — restrict which tools the skill may call
  • context: fork — run as an isolated subagent
  • effort: low | medium | high
  • disable-model-invocation: true — only activates via explicit /__SKILL_NAME__
  • hooks — event-driven triggers
  • license, compatibility, metadata

Directory layout

  • scripts/ — executables this skill can call
  • references/ — docs the skill reads for additional context
  • assets/ — templates, sample files, other resources

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.