agentleFS
Sign inStart free
milad-ahmdmilad-ahmd/agent-skills/skills/skill-creator-pro/SKILL.md

skill-creator-pro

Skill5 starsChanged 16 days agoMITView on GitHub

Designs and writes new Agent Skills (SKILL.md) from a described workflow. It produces a precise trigger description, a step-by-step workflow, rules, an output format, optional helper scripts, and a README, then checks the new skill before handing it over. Use when the user wants to create, write, improve, or package an agent skill, SKILL.md, Claude skill, or reusable agent workflow.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use fetch-library-docs, interview and 7 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.
  • Rehan-Ul-HaqSkill

    fetch-library-docs

    Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.

    Also in 6 projects that use this

  • dazuckSkill

    interview

    Interview me about a plan to flesh out requirements before implementation. Asks non-obvious questions one at a time until all ambiguities are resolved.

    Also in 4 projects that use this

  • JetBrainsSkill

    doc-coauthoring

    Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

    Also in 4 projects that use this

  • GoogleSkill

    internal-comms

    A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

    Also in 4 projects that use this

  • JetBrainsSkill

    theme-factory

    Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

    Also in 4 projects that use this

  • AnthropicSkill

    xlsx

    Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify existing spreadsheets while preserving formulas, (4) Data analysis and visualization in spreadsheets, or (5) Recalculating formulas

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test it in your head: would this description match the 3 example requests?

    line 21
  2. Distinctive:

    Write instructions, not an essay.

    line 33
  3. Distinctive:

    Put fragile, repetitive or exact operations (parsing, API calls) in scripts.

    line 34
  4. Distinctive:

    Add guardrails: confirm before destructive or public actions, never invent facts, cite evidence.

    line 35
  5. Very specific:

    Write a README with a one-line pitch, install steps (~/.claude/skills/ or the project's .claude/skills/), example prompts and a license.

    line 47
  6. Distinctive:

    Never embed secrets. Read them from environment variables instead.

    line 52

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

Turn "I keep explaining this to my agent" into a reusable skill.

1. Interview (keep it short)

  1. What task should this automate? Ask for 2–3 real example requests the user would type.
  2. What does a great result look like? What do agents usually get wrong today?
  3. Which tools, commands, files or APIs are involved? Are there any irreversible actions?
  4. Who will use it (personal, team, public) and in which agents?

2. Write the description first (it controls when the skill triggers)

<What it does, concretely, with key nouns>. Use when the user asks to <trigger phrases 1>, <2>, <3>.

  • Third person, specific, at most about 1024 characters, and including the words users actually type.
  • Test it in your head: would this description match the 3 example requests? Would it wrongly match unrelated requests?

3. Structure

<skill-name>/                 # kebab-case, ≤ 64 chars, same as `name`
├── SKILL.md                  # frontmatter (name, description) + instructions, ideally < 500 lines
├── scripts/                  # deterministic helpers (stdlib-only where possible)
└── references/               # long docs loaded only when needed

SKILL.md body: purpose (1 line) → workflow (numbered steps) → output format (template) → rules (safety and quality).

  • Write instructions, not an essay. Use imperative steps and concrete commands.
  • Put fragile, repetitive or exact operations (parsing, API calls) in scripts. Keep judgment in the instructions.
  • Add guardrails: confirm before destructive or public actions, never invent facts, cite evidence.

4. Validate

python3 scripts/lint_skill.py path/to/<skill-name>

Fix every ❌ and review the ⚠️ warnings. Then dry-run the skill against the user's 3 example requests and refine.

5. Package (optional)

Write a README with a one-line pitch, install steps (~/.claude/skills/ or the project's .claude/skills/), example prompts and a license. Offer to publish it as a GitHub repo, and to submit it to an awesome list.

Rules

  • Each skill does one job. Split skills that try to do everything.
  • Never embed secrets. Read them from environment variables instead.

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