agentleFS
HerbertGaoHerbertGao/herbertgao-skills/.agents/skills/skill-creator/SKILL.md

skill-creator

Skill0 starsChanged 4 months agoMITView on GitHub

Authors and structures professional-grade agent skills following the agentskills.io spec. Use when creating new skill directories, drafting procedural instructions, or optimizing metadata for discoverability. Don't use for general documentation, non-agentic library code, or README files.

189 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use taskflow-inbox-triage, community-led-growth 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

  • 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

  • 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

  • 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

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • +5 more from naman10parikh
  • +1 more from nicepkg

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 5 are distinctive, and 8 are very specific to this project.

  • 0

    Common

    Most of the 185 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 8

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow these steps to generate a skill that adheres to the agentskills.io specification and progressive disclosure principles.

    line 8
  2. Very specific:

    Execute Validation Script: Run the validation script to ensure compliance before proceeding: python3 scripts/validate-metadata.py --name …

    line 13
  3. Very specific:

    If the script returns an error, self-correct the metadata based on the stderr output and re-run until successful.

    line 15
  4. Very specific:

    Create the root directory using the validated name.

    line 18
  5. Distinctive:

    Ensure no human-centric files (README.md, INSTALLATION.md) are created.

    line 23
  6. Very specific:

    Use the template in assets/skill-template.md as the starting point.

    line 26
  7. Distinctive:

    Write all instructions in the third-person imperative (e.g., "Extract the text," "Run the build").

    line 27
  8. Distinctive:

    Keep the main logic under 500 lines.

    line 29
  9. Very specific:

    If a procedure requires a large schema or complex rule set, move it to references/.

    line 30
  10. Distinctive:

    Ensure the script uses standard output (stdout/stderr) to communicate success or failure to the agent.

    line 36
  11. Very specific:

    Verify all file paths are relative and use forward slashes (/).

    line 40
  12. Very specific:

    Metadata Failure: If scripts/validate-metadata.py fails, identify the specific error (e.g., "STYLE ERROR") and rewrite the field to remove …

    line 44
  13. Very specific:

    Context Bloat: If the draft exceeds 500 lines, extract the largest procedural block and move it to a file in references/.

    line 45

“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 Authoring Procedure

Follow these steps to generate a skill that adheres to the agentskills.io specification and progressive disclosure principles.

Step 1: Initialize and Validate Metadata

  1. Define a unique name: 1-64 characters, lowercase, numbers, and single hyphens only.
  2. Draft a description: Max 1,024 characters, written in the third person, including negative triggers.
  3. Execute Validation Script: Run the validation script to ensure compliance before proceeding: python3 scripts/validate-metadata.py --name "[name]" --description "[description]"
  4. If the script returns an error, self-correct the metadata based on the stderr output and re-run until successful.

Step 2: Structure the Directory

  1. Create the root directory using the validated name.
  2. Initialize the following subdirectories:
    • scripts/: For tiny CLI tools and deterministic logic.
    • references/: For flat (one-level deep) context like schemas or API docs.
    • assets/: For output templates, JSON schemas, or static files.
  3. Ensure no human-centric files (README.md, INSTALLATION.md) are created.

Step 3: Draft Core Logic (SKILL.md)

  1. Use the template in assets/skill-template.md as the starting point.
  2. Write all instructions in the third-person imperative (e.g., "Extract the text," "Run the build").
  3. Enforce Progressive Disclosure:
    • Keep the main logic under 500 lines.
    • If a procedure requires a large schema or complex rule set, move it to references/.
    • Command the agent to read the specific file only when needed: "Read references/api-spec.md to identify the correct endpoint."

Step 4: Identify and Bundle Scripts

  1. Identify "fragile" tasks (regex, complex parsing, or repetitive boilerplate).
  2. Outline a single-purpose script for the scripts/ directory.
  3. Ensure the script uses standard output (stdout/stderr) to communicate success or failure to the agent.

Step 5: Final Logic Validation

  1. Review the SKILL.md for "hallucination gaps" (points where the agent is forced to guess).
  2. Verify all file paths are relative and use forward slashes (/).
  3. Cross-reference the final output against references/checklist.md.

Error Handling

  • Metadata Failure: If scripts/validate-metadata.py fails, identify the specific error (e.g., "STYLE ERROR") and rewrite the field to remove first/second person pronouns.
  • Context Bloat: If the draft exceeds 500 lines, extract the largest procedural block and move it to a file in references/.

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.