agentleFS
zhiyuzizhiyuzi/Signex/.claude/skills/skill-creator/SKILL.md

skill-creator

Skill98 starsChanged 9 months agoAGPL-3.0View on GitHub

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

223 other projects use a version of this, 78 of them edited; 47 of 78 edited versions we compared changed its rules; 6 new projects in the last 4 weeks, against 11 the 4 before.

How people change it

47 of 78 edited versions changed its rules, and some changes recur.

Of the 78 edited versions we compared: 31 keep every rule, 47 made changes of their own.

Rules people drop

  1. After initialization, customize or remove the generated SKILL.md and example files as needed.dropped by 25 of 47
  2. Key principle: When a skill supports multiple variations, frameworks, or options, keep only the core workflow and selection guidance in SKILL.md. Move variant-specific details (patterns, examples, configuration) into separate reference files.dropped by 23 of 47
  3. Default assumption: Claude is already very smart. Only add context Claude doesn't already have. Challenge each piece of information: "Does Claude really need this explanation?" and "Does this paragraph justify its token cost?"dropped by 22 of 47
  4. Low freedom (specific scripts, few parameters): Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed.dropped by 22 of 47
  5. Avoid deeply nested references - Keep references one level deep from SKILL.md. All reference files should link directly from SKILL.md.dropped by 22 of 47
  6. High freedom (text-based instructions): Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach.dropped by 20 of 47
  7. Medium freedom (pseudocode or scripts with parameters): Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior.dropped by 20 of 47
  8. Do not include any other fields in YAML frontmatter.dropped by 19 of 47

Rules people add

  1. When generating names, generate a name under 64 characters (letters, digits, hyphens).added by 24 of 47
  2. Prefer short, verb-led phrases that describe the action.added by 24 of 47
  3. Use lowercase letters, digits, and hyphens only; normalize user-provided titles to hyphen-case (e.g., "Plan Mode" -> plan-mode).added by 23 of 47
  4. After initialization, customize the SKILL.md and add resources as needed. If you used --examples, replace or delete placeholder files.added by 23 of 47
  5. If you used --examples, delete any placeholder files that are not needed for the skill. Only create resource directories that are actually required.added by 23 of 47
  6. A rule we can't quote: its licence doesn't allow itadded by 12 of 47
  7. A rule we can't quote: its licence doesn't allow itadded by 7 of 47
  8. A rule we can't quote: its licence doesn't allow itadded by 7 of 47

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 6 new projects took it in the last 4 weeks, 0.5× the 4 weeks before.

Week of Sep 20: 2 new projectsWeek of Sep 27: 3 new projectsWeek of Oct 4: 4 new projectsWeek of Oct 11: 2 new projectsWeek of Oct 18: 2 new projectsWeek of Oct 25: 2 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 2 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

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

Show its rules and text

We split this skill into the rules it gives an agent

26 rules. 0 are common, 17 are distinctive, and 9 are very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 17

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.