agentleFS
TerminalSkillsTerminalSkills/skills/.github/PULL_REQUEST_TEMPLATE/skill.md

PULL_REQUEST_TEMPLATE

Skill150 starsChanged 9 months agoApache-2.0View on GitHub

Before submitting, ensure your skill meets these requirements:

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. Chili-Piper/mcp-assets★ 8same name
    2. hofstatter/prometheus-memory★ 2same name
    3. tqnonline/agent-forge★ 2same 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.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    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 submitting, ensure your skill meets these requirements:

    line 5

≈ “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

Add Skill: your-skill-name

Checklist

Before submitting, ensure your skill meets these requirements:

Frontmatter (SKILL.md YAML header)

  • name — Lowercase kebab-case only (a-z, 0-9, -), max 64 chars
  • description — States WHAT it does and WHEN to use it, includes trigger words, max 1024 chars, third person (no "I"/"you"/"we")
  • license — Present (e.g., Apache-2.0)
  • compatibility — Concrete system requirements (e.g., "Requires Python 3.9+") or "No special requirements"
  • metadata.author — Your GitHub username
  • metadata.version — Semantic version ("1.0.0")
  • metadata.category — One of: documents, development, data-ai, devops, business, design, automation, research, productivity, content
  • metadata.tags — Array of 3–5 relevant tags

Body Sections

  • Overview — 2–3 sentence summary
  • Instructions — Step-by-step actionable workflow (not prose), each step tells the agent what to DO
  • Examples — At least 2 concrete input/output examples with realistic data (no lorem ipsum / foo / bar)
  • Guidelines — Best practices, edge cases, error handling

Quality

  • Under 300 lines total
  • Instructions are specific enough that an AI agent can follow them without guessing
  • Works cross-platform (no vendor lock-in or proprietary APIs without a free tier)
  • Solves a real, recurring problem a developer would encounter at least weekly

Files

  • skills/your-skill-name/SKILL.md added
  • Use-case article added in use-cases/ (optional but recommended)

Which use case does this skill serve?

<!-- Link to an existing use case, or describe the real-world problem this skill addresses -->

Example usage

<!-- Show a concrete example of the skill in action -->

Category

<!-- Which category does this skill belong to? -->

Additional context

<!-- Any other information reviewers should know -->

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.