菜单
Expert guidance for creating high-quality Claude Code skills following Anthropic's official best practices. Use when creating, improving, or auditing skill files.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/nathanvale/side-quest-marketplace-old --skill claude-code-skill-expert命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Web scraping, site crawling, search, structured data extraction, and AI-powered research with Firecrawl CLI. Use when you need full page content as markdown, JS-rendered pages, anti-bot bypass, crawling entire documentation sites, extracting structured data with schemas, or deep web research. Prefer WebFetch for quick questions about a known URL. Prefer WebSearch for finding links without full content.
Build production-grade MCP (Model Context Protocol) servers with observability, correlation ID tracing, and dual logging. Use when creating new MCP servers, adding tools to existing servers, implementing file logging, debugging MCP issues, wrapping CLI tools with spawnSyncCollect, or following Side Quest marketplace patterns. Covers @side-quest/core/mcp declarative API, @side-quest/core/spawn CLI wrapper patterns, Zod schemas, Bun runtime, and 9 gold standard patterns validated across Kit plugin (18 tools). Includes error handling, response format switching, MCP annotations, and graceful degradation.
Unified inbox processor - handles ALL content types (clippings, transcriptions, VTT files, attachments) with parallel subagents and single-table review. Routes to appropriate creator based on proposed_template.
基于 SOC 职业分类
正在显示 SKILL.md
| name | claude-code-skill-expert |
| description | Expert guidance for creating high-quality Claude Code skills following Anthropic's official best practices. Use when creating, improving, or auditing skill files. |
Guide for creating effective, well-structured Claude Code skills that follow Anthropic's official best practices.
Structure skills as a table of contents where Claude loads content on-demand:
Pattern: Keep SKILL.md under 500 lines. Move detailed content to separate reference files.
Example:
## Step 1: Analyze Code
Run the analyzer: `bun run analyzer.ts`
**Output**: See [output-templates.md#analysis](references/output-templates.md#analysis) for format
The most critical fields - Claude uses these to decide when to trigger the skill.
Good description:
description: Books
Bad description:
description: A helpful skill for booking things
Rules:
One-level-deep references from SKILL.md:
skill/
├── SKILL.md # Overview, workflow steps
└── references/
├── templates.md # Output formats
├── commands.md # CLI reference
└── errors.md # Error recovery
Don't do:
skill/
├── SKILL.md
└── references/
├── advanced/
│ └── deep-file.md # Too deep!
---
name: my-skill
description: What it does and when to use it
allowed-tools: Bash, Read, Write
model: claude-sonnet-4-5
---
# Skill Title
Brief introduction explaining purpose.
## Workflow Overview
[Optional: Visual diagram of steps]
## Step 1: First Action
**Action**: What to do
**Command/Tool**: Specific tool or bash command
**Output**: Template reference or inline format
**Wait for**: User response or validation
---
## Step 2: Second Action
[Continue pattern...]
---
## References
- [Templates](references/templates.md) - Exact output formats
- [Commands](references/commands.md) - CLI reference
- [Errors](references/errors.md) - Recovery patterns
CRITICAL: Create a separate references/output-templates.md file with exact copy-paste formats.
# Output Templates
**CRITICAL**: Use these exact templates. Copy the structure precisely.
---
## Template Name
**ALWAYS use this exact format**:
\`\`\`
[Exact format with placeholders]
\`\`\`
**Rules**:
- Specific formatting requirements
- What to show/hide
- How to handle edge cases
**Mapping from data**:
\`\`\`
field_name → [PLACEHOLDER]
nested.field → [OTHER_PLACEHOLDER]
\`\`\`
**Example**:
\`\`\`
[Concrete example with real data]
\`\`\`
## Step 2: Choose Path
**If** creating new content → Go to Step 3
**If** editing existing → Go to Step 5
## Step 4: Validate
Run validator → identify errors → fix → repeat until passing
**See**: [error-handling.md#validation](references/error-handling.md#validation)
## Step 1: Analyze Request
**Use**:
- `kit_grep` for literal text search
- `kit_semantic` for "find where we handle X"
- `kit_symbols` for function definitions
**See**: [tool-selection.md](references/tool-selection.md) for full decision tree
# My Skill
Keep SKILL.md as overview.
**Resources**:
- [Forms](references/forms.md) - Advanced form handling
- [API](references/api.md) - API details
- [Examples](references/examples.md) - Concrete examples
If certain contexts are rarely used together, keep paths separate:
references/
├── create-workflow.md # Only for creating new items
└── edit-workflow.md # Only for editing existing
Scripts don't load into context - only their output does.
Efficient:
bun run extract-fields.ts # Code not in context
Inefficient:
Parse the JSON manually and extract these 20 fields...
[20 lines of parsing instructions]
For files >100 lines:
# Long Reference File
## Contents
- [Section 1](#section-1)
- [Section 2](#section-2)
## Section 1
...
Likely causes:
Fix: Add trigger phrases to description: "Use when users ask about X, need to Y, or mention Z"
Likely causes:
Fix: Narrow description with specific scenarios
Likely causes:
Fix: Move details to reference files, use "See X" pattern
Likely causes:
Fix: Create output-templates.md with exact formats and examples
Before considering a skill complete:
processing-pdfs)See the-cinema-bandit plugin's ticket-booking skill for a production example:
skills/ticket-booking/
├── SKILL.md (127 lines) # Lean workflow
└── references/
├── output-templates.md # Strict formats
├── cli-commands.md # CLI reference
└── error-handling.md # Recovery patterns
Key features: