skill-creator

Files (10)

• LICENSE.txt
• README.md
• SKILL.md
• output-patterns.md · references/
• workflows.md · references/
• init_skill.py · scripts/
• package_skill.py · scripts/
• quick_validate.py · scripts/
• skill-authoring-contract.test.sh · scripts/tests/
• skill-creator-flow.svg

SKILL.md (first lines)

<!-- Modified from the original work at https://github.com/anthropics/skills/tree/main/skills/skill-creator (Apache-2.0, copyright Anthropic, PBC). See THIRD_PARTY_NOTICES.md. -->
<!-- 本檔在契約測試底下：bash ~/.claude/skills/skill-creator/scripts/tests/skill-authoring-contract.test.sh；python3 ~/.claude/commands/tests/test_skill_verify_one_shot_callers.py -->

# Skill Creator

> **出處注記（2026-06-12）**：本檔底本 = 官方 anthropics/skills `0f77e501`（2025-11-17 版，byte 級確認）。官方 2026-02-06 [#350](https://github.com/anthropics/skills/pull/350) 整支重寫為 eval-loop 路線（人造 test case + benchmark + viewer 人審），**刻意不跟**——本地驗證鏈（skill-creator 內建 RED → GREEN → REFACTOR + fresh GREEN subagent 實跑 + B 線生產資料漂移抽查）更便宜且已實證。不要「同步上游」覆蓋本檔；上游動態由 skill-upstream-check weekly 巡邏。

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.

Think of Claude as exploring a path: a narrow bridge with cliffs needs specific guardrails (low freedom), while an open field allows many routes (high freedom).

### Anatomy of a Skill

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

```
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 intended to be loaded into context as needed
    └── 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, thus it is very important to be clear and comprehensive in describing what the skill is, and when it should be used.
- **Body** (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers (if at all).

### Separate invocation capability from trigger condition

When authoring a skill, document these as separate fields:

- **Invocation capability**: State whether the model can call the skill, which explicit user entry points exist, and which parent `Skill(...)` edges are active. Preserve Skill-to-Skill wiring by default.
- **Trigger condition**: State the observable authoring guidance for when to choose the skill. For a pipeline-gated child, keep it model-callable; describe the trigger condition as authoring guidance, not a runtime hard gate.

Do not turn a trigger condition into a hard flag that suppresses an active parent edge. Keep `disable-model-invocation` omitted by default；預設不使用它，因為 it removes a model-callable path and can silently break a parent→child edge. 使用 `disable-model-invocation` 前，先記錄 user-only 理由，再完成 inbound wiring inventory.

### Frontmatter field classes

Keep frontmatter claims in three separate classes:

- **runtime required**: Fields the Claude runtime actually consumes.
- **local validator accepted**: Fields accepted by the local validator, such as `quick_validate.py`; acceptance only describes this repository's parser.
- **local convention**: Fields or metadata used by local tooling or authoring convention, with no implied runtime behavior.

The validator `ALLOWED_PROPERTIES` is an allowlist for local validation, not evidence of platform support. Verify platform behavior from the platform contract or a real invocation before documenting it.

### Inbound wiring inventory

Before changing invocation behavior, scan skills, commands, workflows, registry entries, and frontmatter for inbound edges. Also scan `Skill(...)` calls, slash-command references, and prose references. Record every edge as `path:line`. A dynamic or planned edge without a registry entry is `unverified`, not an available trigger.

### Context pointers

Write every pointer in this form: `如果 X，就在 Y 前讀 Z`.

- `X` must be an observable（可觀察）condition.
- `Y` must name the execution timepoint（時點）.
- `Z` must name a concrete location to read.

A pointer is incomplete when it omits any slot.

#### Bundled Resources (optional)

##### Scripts (`scripts/`)

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

- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed
- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks
- **Benefits**: Token efficient, deterministic, may be executed without loading into context
- **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments

##### References (`references/`)

Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.

- **When to include**: For documentation that Claude should reference while working
- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications
- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides

From GGGODLIN/gggodlin-cc-harness, MIT.

More from GGGODLIN/gggodlin-cc-harness