agentleFS
Sign inStart free
eddmanneddmann/jeeves/skills/skill-creator/SKILL.md

skill-creator

Skill2 starsChanged 9 months agoMITView on GitHub

Create or update skills. Use when designing, structuring, or packaging new skills with SKILL.md files.

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, mermaid-diagram-generator and 10 more.

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.
  • AtomicBot-aiSkill

    taskflow-inbox-triage

    Also in 6 projects that use this

  • shalombSkill

    mermaid-diagram-generator

    Guide on creating and editing Mermaid charts safely. Use when asked to draw a diagram, flowchart, or architecture chart. Triggers on: 'mermaid', 'diagram', 'flowchart', 'visualize'.

    Also in 5 projects that use this

  • naman10parikhSkill

    ecosystem-reference

    Quick-access directory of Claude Code ecosystem repos, skills, plugins, MCPs, and patterns. Use when improving the harness.

    Also in 5 projects that use this

  • naman10parikhSkill

    fractal-delegation

    Also in 5 projects that use this

  • Liang-MHSkill

    stock_analysis

    获取 A 股、基金和港股的实时行情和技术分析数据

    Also in 5 projects that use this

  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • +6 more from naman10parikh

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 185 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create new skills by writing SKILL.md files to the workspace skills/ directory.

    line 8
  2. Very specific:

    Write SKILL.md with YAML frontmatter

    line 22
  3. Very specific:

    Keep SKILL.md under 500 lines

    line 44
  4. Distinctive:

    Only add information the agent doesn't already know

    line 47
  5. Distinctive:

    Don't create README.md, CHANGELOG.md, or other auxiliary files

    line 49

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

Create new skills by writing SKILL.md files to the workspace skills/ directory.

Skill Structure

skill-name/
├── SKILL.md (required)
└── references/ (optional)

Creating a Skill

  1. Choose a name: lowercase letters, digits, and hyphens only (max 64 chars)
  2. Create directory: workspace/skills/<skill-name>/
  3. Write SKILL.md with YAML frontmatter

SKILL.md Format

---
name: my-skill
description: What this skill does and when to use it
---

# My Skill

Instructions for using this skill...

Frontmatter Fields

  • name (required): Must match the directory name, lowercase [a-z0-9-]
  • description (required): Clear description of what the skill does AND when to trigger it

Guidelines

  • Keep SKILL.md under 500 lines
  • Be concise — the context window is shared
  • Include examples over verbose explanations
  • Only add information the agent doesn't already know
  • Split large reference material into references/*.md files
  • Don't create README.md, CHANGELOG.md, or other auxiliary files

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