agentleFS
Sign inStart free
ahmadammarmahmadammarm/musyskills/templates/SKILL.md

skill-name

Skill1 starsChanged 12 days agoMITView on GitHub

One or two sentences on what the skill does and when to use it. Include the phrases a user would actually say, because the agent uses this text to decide when to run the skill.

39 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use git-workflow and frontend-design.

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.
  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 2

    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:

    Before doing anything, perform the following in order:

    line 21
  2. Distinctive:

    Read-only checks that gather context (for example, git status).

    line 23

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

Purpose

What the skill achieves and why it exists, in two or three sentences.

Trigger

Activate this skill when the user:

  • Runs the slash command /skill-name.
  • Says "..." or any similar phrase.

Pre-flight Checks

Before doing anything, perform the following in order:

  1. Read-only checks that gather context (for example, git status).
  2. Conditions that must stop the skill, and what to tell the user when they do.

Workflow

Step 1: ...

  • Concrete actions, in order.

Step 2: ...

  • Points where the user must confirm before continuing.

Rules

  • Hard constraints the agent must never break.

Output Format

What the agent reports at the end, as a numbered list of parts.

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