agentleFS
ishandutta2007ishandutta2007/Awesome-Claude-Skills/skills/write-a-skill/skill.md

write-a-skill

Skill16 starsChanged 6 months agoMITView on GitHub

Output: "Creating pdf-extraction skill. Description: Extract text and tables from PDF files. Use when working with PDF files or when user mentions forms or document extraction. Structure: - skill.md: Core instructions. - scripts/parse.py: Python helper for PDF parsing."

122 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ubiquitous-language, prd-to-plan and 4 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.
  • kennethkeimSkill

    ubiquitous-language

    Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".

    Also in 20 projects that use this

  • HK-hubSkill

    prd-to-plan

    Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

    Also in 7 projects that use this

  • semtexfromuaSkill

    how-to

    Курс typing-уроків по існуючому проекту — «як написати його з нуля»: аналіз → план у .practicum/course.md → покрокова генерація уроків. Використовуй для команди /vibe-typing:how-to.

    Also in 3 projects that use this

  • GoogleSkill

    setup-matt-pocock-skills

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

    Also in 33 projects that use this

  • ShopifySkill

    triage-issue

    Triage a GitHub issue — classify priority (P0/P1/P2), search for duplicates, and apply labels.

    Also in 7 projects that use this

  • GoogleSkill

    improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    Also in 59 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 118 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create new Claude skills with proper structure, progressive disclosure, and bundled resources to expand an agent's capabilities.

    line 7
  2. Very specific:

    Concise instructions: Keep the main skill.md focused.

    line 11
  3. Distinctive:

    Deterministic Helpers: Add utility scripts for operations that are repetitive or need strict validation.

    line 12
  4. Distinctive:

    Third Person: Write descriptions in the third person for the agent's system prompt.

    line 13
  5. Distinctive:

    Gather: Ask about the domain, use cases, and needed scripts.

    line 16
  6. Very specific:

    Draft: Create the skill.md and any supporting READMEs or scripts.

    line 17

“Common” is measured: kept by at least 6 in 10 of the 118 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: Write a Skill

Role

You are a Prompt Engineer and Agent Workflow Expert.

Objective

Create new Claude skills with proper structure, progressive disclosure, and bundled resources to expand an agent's capabilities.

Constraints

  • Trigger-Focused: The skill description must clearly state when and why to use it ("Use when...").
  • Concise instructions: Keep the main skill.md focused. Use supplementary files for heavy documentation.
  • Deterministic Helpers: Add utility scripts for operations that are repetitive or need strict validation.
  • Third Person: Write descriptions in the third person for the agent's system prompt.

Process

  1. Gather: Ask about the domain, use cases, and needed scripts.
  2. Draft: Create the skill.md and any supporting READMEs or scripts.
  3. Review: Present the draft to the user for clarity and coverage check.
  4. Refine: Iterate based on feedback until the skill is "AI-ready."

Output Format

  • Skill Structure: A tree view of the new skill directory.
  • Skill.md Content: The core instructions and triggers.
  • Utility Scripts: (Optional) Code for helper scripts.

Examples

Example 1: New PDF Skill

Input: "I want a skill to help me extract data from PDFs."

Output: "Creating pdf-extraction skill. Description: Extract text and tables from PDF files. Use when working with PDF files or when user mentions forms or document extraction. Structure:

  • skill.md: Core instructions.
  • scripts/parse.py: Python helper for PDF parsing."

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.