AgentSkillsCN

skill-creator

打造高效技能的指南。当用户希望创建一项新技能（或更新现有技能），并通过专业知识、工作流程或工具集成来拓展Claude的能力时，应使用此技能。

SKILL.md
--- frontmatter
name: skill-creator
description: 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.
license: Complete terms in LICENSE.txt

Skill Creator

This skill provides guidance for creating effective skills.

About Skills

Skills are modular, self-contained packages that extend Claude's capabilities by providing specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific domains or tasks—they transform Claude from a general-purpose agent into a specialized agent equipped with procedural knowledge that no model can fully possess.

What Skills Provide

  1. •Specialized workflows - Multi-step procedures for specific domains
  2. •Tool integrations - Instructions for working with specific file formats or APIs
  3. •Domain expertise - Company-specific knowledge, schemas, business logic
  4. •Bundled resources - Scripts, references, and assets for complex and repetitive tasks

Core Principles

Concise is Key

The context window is a public good. Skills share the context window with everything else Claude needs: system prompt, conversation history, other Skills' metadata, and the actual user request.

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?"

Prefer concise examples over verbose explanations.

Set Appropriate Degrees of Freedom

Match the level of specificity to the task's fragility and variability:

High freedom (text-based instructions): Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach.

Medium freedom (pseudocode or scripts with parameters): Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior.

Low freedom (specific scripts, few parameters): Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed.

Anatomy of a Skill

Every skill consists of a required SKILL.md file and optional bundled resources:

code
skill-name/
├── SKILL.md (required)
│   ├── YAML frontmatter metadata (required)
│   │   ├── name: (required)
│   │   └── description: (required)
│   └── Markdown instructions (required)
└── Bundled Resources (optional)
    ├── scripts/          - Executable code (Python/Bash/etc.)
    ├── references/       - Documentation loaded as needed into context
    └── assets/           - Files used in output (templates, icons, fonts, etc.)

SKILL.md (required)

Every SKILL.md consists of:

  • •Frontmatter (YAML): Contains name and description fields. These are the only fields that Claude reads to determine when the skill gets used.
  • •Body (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers.

Bundled Resources (optional)

Scripts (scripts/)

Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.

References (references/)

Documentation and reference material intended to be loaded as needed into context.

Assets (assets/)

Files not intended to be loaded into context, but rather used within the output Claude produces.

What to Not Include in a Skill

Do NOT create extraneous documentation or auxiliary files:

  • •README.md, INSTALLATION_GUIDE.md, QUICK_REFERENCE.md, CHANGELOG.md, etc.

Progressive Disclosure Design Principle

Skills use a three-level loading system:

  1. •Metadata (name + description) - Always in context (~100 words)
  2. •SKILL.md body - When skill triggers (<5k words)
  3. •Bundled resources - As needed by Claude

Keep SKILL.md body under 500 lines. Split content into separate files when approaching this limit.

Skill Creation Process

  1. •Understand the skill with concrete examples
  2. •Plan reusable skill contents (scripts, references, assets)
  3. •Initialize the skill (run init_skill.py)
  4. •Edit the skill (implement resources and write SKILL.md)
  5. •Package the skill (run package_skill.py)
  6. •Iterate based on real usage

Step 1: Understanding the Skill with Concrete Examples

Clearly understand concrete examples of how the skill will be used. Ask questions like:

  • •"What functionality should this skill support?"
  • •"Can you give examples of how this skill would be used?"
  • •"What would a user say that should trigger this skill?"

Step 2: Planning the Reusable Skill Contents

Analyze each example to identify what scripts, references, and assets would be helpful.

Step 3: Initializing the Skill

Run the init_skill.py script to generate a template:

bash
scripts/init_skill.py <skill-name> --path <output-directory>

Step 4: Edit the Skill

Learn Proven Design Patterns

  • •Multi-step processes: See references/workflows.md
  • •Specific output formats or quality standards: See references/output-patterns.md

Update SKILL.md

Frontmatter:

  • •name: The skill name
  • •description: Primary triggering mechanism. Include both what the Skill does and specific triggers/contexts.

Step 5: Packaging a Skill

bash
scripts/package_skill.py <path/to/skill-folder>

The script validates and packages into a distributable .skill file.

Step 6: Iterate

  1. •Use the skill on real tasks
  2. •Notice struggles or inefficiencies
  3. •Identify improvements needed
  4. •Implement changes and test again