Claude技能创建指南：技能开发模板与最佳实践 | skill-creator

skill-creator by 404kidwiz/claude-supercode-skills

79 周安装量

63 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/404kidwiz/claude-supercode-skills --skill skill-creator

AI/机器学习技术文档编程最佳实践

🇨🇳中文介绍

技能创建器

目的

一个元技能，用于指导创建高质量、高效的技能。提供模板、最佳实践和结构指南，用于构建能通过专业知识、工作流程或工具集成来增强 Claude 能力的技能。

使用时机

用户想要创建一个新技能
用户想要更新或改进现有技能
用户询问如何构建技能文档
需要为特定领域或工作流程设计技能
希望确保技能遵循最佳实践

核心技能结构

必需组件

每个技能必须包含以下元素：

Frontmatter

---
name: skill-name
description: One-line description when to use this skill
---

标题与目的

# Skill Name

## Purpose
Clear, concise statement of what this skill does

使用时机

## When to Use
- Specific trigger 1
- Specific trigger 2
- Context where this helps

核心能力

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

可选但推荐的组件

工作流程

## Workflow

1. Step 1: What to do first
2. Step 2: Next action
3. Step 3: Final deliverable

最佳实践

## Best Practices

- Do this
- Avoid that
- Remember this

示例

## Examples

### Example 1: Common Use Case
**Input**: User request
**Approach**: How to handle
**Output**: Expected result

反模式

## Anti-Patterns

❌ **Don't**: Bad practice
✅ **Do**: Good alternative

技能创建工作流程

步骤 1：定义范围

这个技能解决什么问题？
谁会使用它？
什么会触发它的使用？
预期的结果是什么？

步骤 2：识别核心知识

领域特定术语
关键概念和原则
该领域的常见模式
涉及的工具和技术

步骤 3：构建工作流程

进入条件
逐步流程
决策点
退出标准和交付物

步骤 4：添加实用元素

真实世界示例
需要避免的常见陷阱
该领域的最佳实践
质量标准

步骤 5：编写清晰的触发器

使“使用时机”具体化：

✅ "用户需要对 PostgreSQL 数据库进行 SQL 查询优化"
❌ "用户需要数据库帮助"
✅ "调试分布式系统中的生产环境故障"
❌ "修复错误"

名称不言自明
描述清楚地说明了何时使用
目的用 1-2 句话说明
没有未经解释的行话

所有必需部分都存在
工作流程是可操作的
示例涵盖常见情况
处理了边界情况

触发器是具体的
步骤足够详细以便遵循
工具/方法被明确命名
定义了成功标准

易于浏览和导航
格式一致
章节顺序合乎逻辑
在有用处提供交叉引用

技术领域技能模板

---
name: domain-expert
description: Use when user needs [specific technical task] in [technology/domain]
---

# Domain Expert

## Purpose

Expert in [domain] specializing in [specific areas]. Helps with [key problems solved].

## When to Use

- User needs [specific task 1]
- Working with [technology] and needs [help type]
- Troubleshooting [specific problem type]
- Designing [architectural element]

## Core Capabilities

### [Domain] Expertise
- [Technology 1] - [version/specifics]
- [Technology 2] - [what aspects]
- [Pattern/practice] - [when/how]

### Key Techniques
- **[Technique 1]**: [What it solves]
- **[Technique 2]**: [When to use]
- **[Technique 3]**: [How it helps]

## Workflow

1. **Understand Requirements**
   - Clarify [specific aspects]
   - Identify [constraints]

2. **Apply [Domain] Patterns**
   - Use [pattern 1] for [scenario]
   - Consider [trade-off]

3. **Implement Solution**
   - Follow [best practice]
   - Ensure [quality criteria]

4. **Validate**
   - Test [aspects]
   - Verify [requirements met]

## Best Practices

- **[Practice 1]**: [Reasoning]
- **[Practice 2]**: [Benefit]
- **[Practice 3]**: [Why important]

## Common Patterns

### [Pattern 1]
**When**: [Scenario]
**How**: [Implementation approach]
**Why**: [Benefits]

### [Pattern 2]
**When**: [Scenario]
**How**: [Implementation approach]
**Why**: [Benefits]

## Anti-Patterns

❌ **Don't**: [Bad practice]
   - Why it fails: [Reason]
   - Better approach: [Alternative]

❌ **Avoid**: [Common mistake]
   - Problem: [What goes wrong]
   - Instead: [Correct way]

## Examples

### Example 1: [Common Scenario]
**Context**: [Situation]
**Approach**: [Solution steps]
**Result**: [Outcome]

## Tools & Technologies

- **[Tool 1]**: [Version] - [Use for what]
- **[Tool 2]**: [Version] - [Use for what]
- **[Framework]**: [Version] - [Key features used]

流程/工作流技能模板

---
name: process-specialist
description: Use when user needs [specific process/workflow] for [outcome]
---

# Process Specialist

## Purpose

Guides [specific process] to achieve [specific outcome]. Ensures [quality aspects] through [methodology].

## When to Use

- Need to [execute process]
- Want to ensure [quality outcome]
- Working on [scenario requiring this process]

## Core Process

### Phase 1: [Name]
**Goal**: [What to achieve]

Steps:
1. [Action 1]: [Details]
2. [Action 2]: [Details]
3. [Action 3]: [Details]

**Outputs**: [What you have after this phase]

### Phase 2: [Name]
**Goal**: [What to achieve]

Steps:
1. [Action 1]: [Details]
2. [Action 2]: [Details]

**Outputs**: [What you have after this phase]

### Phase 3: [Name]
**Goal**: [What to achieve]

Steps:
1. [Action 1]: [Details]
2. [Action 2]: [Details]

**Deliverable**: [Final output]

## Decision Points

### When to [Decision]
- If [condition], then [choice A]
- If [condition], then [choice B]

## Quality Gates

After each phase, verify:
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

## Best Practices

- **[Practice]**: [Why it matters]
- **[Practice]**: [Impact on quality]

## Common Pitfalls

- **Pitfall**: [What people do wrong]
  - **Impact**: [What happens]
  - **Solution**: [How to avoid]

❌ "在处理数据库时使用" ✅ "在需要对 PostgreSQL 14+ 生产数据库进行 SQL 查询优化时使用"

❌ "考虑安全性" ✅ "运行 OWASP ZAP 扫描并审查所有 HIGH 严重性发现"

使用一致的标题级别：

## 用于主要章节
### 用于子章节
#### 用于详细分解

使用视觉指示器

✅ 表示良好实践
❌ 表示反模式
🔍 表示调查步骤
⚠️ 表示警告
💡 表示提示

不要只列出要做什么——解释原因：

## Instead of:
- Use connection pooling

## Write:
- **Use connection pooling** (pg-pool for PostgreSQL)
  - Reduces connection overhead by 80%
  - Critical for applications with >100 concurrent users
  - Configure pool size = (core count × 2) + effective_spindle_count

核心技术发布新版本
该领域出现更好的实践
用户反馈揭示不足
创建了相关技能（交叉引用）

考虑添加到 frontmatter：

---
name: skill-name
description: One-line description
---

链接到相关技能：

## Related Skills
- Use [[debugger-skill]] when issues arise
- Combine with [[performance-engineer-skill]] for optimization
- Precede with [[architect-reviewer-skill]] for design validation

复杂的工作流程可以串联技能：

## Workflow
1. Use [[requirement-analyst]] to gather needs
2. Apply this skill for implementation
3. Use [[code-reviewer]] for quality assurance
4. Use [[deployment-engineer]] to ship

示例 1：创建 Python 专家技能

上下文：需要为高级 Python 开发创建一个技能

定义范围：专注于 FastAPI 和类型安全的 Python 3.11+
识别触发器："modern Python"、"type hints"、"FastAPI"
构建核心能力：
- Python 3.11+ 特性（match 语句、类型改进）
- FastAPI 框架模式
- 类型注解最佳实践
添加工作流程：设计 API → 类型模型 → 实现路由 → 测试
包含示例：带有完整类型注解的 FastAPI 路由

结果：一个专注于现代 Python 开发的、可操作的技能

示例 2：创建 Git 工作流技能

上下文：需要将团队的 git 分支策略规范化

定义范围：用于功能开发的 Git 工作流
识别触发器："create branch"、"make PR"、"git workflow"
构建为阶段：
- 分支创建
- 开发周期
- PR 流程
- 合并策略
添加决策点：何时 rebase 与 merge
包含示例：标准功能开发流程

结果：用于一致使用 git 的清晰程序指南

在最终确定技能之前，检查：

Frontmatter 完整（名称、描述）
标题和目的清晰
"使用时机"部分有具体的触发器
核心能力定义明确

信息准确且最新
示例真实且有用
最佳实践有理由支持
反模式展示了替代方案

可以快速浏览并找到信息
章节逻辑流畅
格式一致
交叉引用正确

没有拼写/语法错误
技术术语有定义
代码示例（如果有）正确
满足上述所有质量标准

元信息：关于此技能

此技能本身展示了它所教授的原则：

清晰的 frontmatter 和结构
具体的"使用时机"触发器
可操作的工作流程
具体的示例
质量标准

创建技能时，请将此既作为指南又作为模板。

2026 年 1 月 24 日

🇺🇸English

Skill Creator

Purpose

A meta-skill that guides the creation of high-quality, effective skills. Provides templates, best practices, and structural guidelines for building skills that enhance Claude's capabilities with specialized knowledge, workflows, or tool integrations.

When to Use

User wants to create a new skill
User wants to update or improve an existing skill
User asks how to structure skill documentation
Need to design a skill for a specific domain or workflow
Want to ensure skill follows best practices

Core Skill Structure

Required Components

Every skill must have these elements:

Frontmatter

---
name: skill-name
description: One-line description when to use this skill
---

Title & Purpose

# Skill Name

## Purpose
Clear, concise statement of what this skill does

When to Use

## When to Use
- Specific trigger 1
- Specific trigger 2
- Context where this helps

Core Capabilities

## Core Capabilities

### Domain Expertise
- Key knowledge area 1
- Key knowledge area 2

### Tools & Methods
- Specific techniques
- Frameworks used

Optional but Recommended Components

Workflow

## Workflow

1. Step 1: What to do first
2. Step 2: Next action
3. Step 3: Final deliverable

Best Practices

## Best Practices

- Do this
- Avoid that
- Remember this

Examples

## Examples

### Example 1: Common Use Case
**Input**: User request
**Approach**: How to handle
**Output**: Expected result

Anti-Patterns

## Anti-Patterns

❌ **Don't**: Bad practice
✅ **Do**: Good alternative

Skill Creation Workflow

Step 1: Define Scope

Ask yourself:

What problem does this skill solve?
Who will use it?
What triggers its use?
What's the expected outcome?

Step 2: Identify Core Knowledge

Document:

Domain-specific terminology
Key concepts and principles
Common patterns in this domain
Tools and technologies involved

Step 3: Structure the Workflow

Map out:

Entry conditions
Step-by-step process
Decision points
Exit criteria and deliverables

Step 4: Add Practical Elements

Include:

Real-world examples
Common pitfalls to avoid
Best practices from the field
Quality criteria

Step 5: Write Clear Triggers

Make "When to Use" specific:

✅ "User needs SQL query optimization for PostgreSQL databases"
❌ "User needs database help"
✅ "Debugging production outages in distributed systems"
❌ "Fixing bugs"

Skill Quality Criteria

Clarity

Name is self-explanatory
Description clearly states when to use
Purpose is stated in 1-2 sentences
No jargon without explanation

Completeness

All required sections present
Workflow is actionable
Examples cover common cases
Edge cases addressed

Specificity

Triggers are concrete
Steps are detailed enough to follow
Tools/methods are named explicitly
Success criteria defined

Usability

Easy to scan and navigate
Consistent formatting
Logical section ordering
Cross-references where helpful

Skill Templates

Technical Domain Skill Template

---
name: domain-expert
description: Use when user needs [specific technical task] in [technology/domain]
---

# Domain Expert

## Purpose

Expert in [domain] specializing in [specific areas]. Helps with [key problems solved].

## When to Use

- User needs [specific task 1]
- Working with [technology] and needs [help type]
- Troubleshooting [specific problem type]
- Designing [architectural element]

## Core Capabilities

### [Domain] Expertise
- [Technology 1] - [version/specifics]
- [Technology 2] - [what aspects]
- [Pattern/practice] - [when/how]

### Key Techniques
- **[Technique 1]**: [What it solves]
- **[Technique 2]**: [When to use]
- **[Technique 3]**: [How it helps]

## Workflow

1. **Understand Requirements**
   - Clarify [specific aspects]
   - Identify [constraints]

2. **Apply [Domain] Patterns**
   - Use [pattern 1] for [scenario]
   - Consider [trade-off]

3. **Implement Solution**
   - Follow [best practice]
   - Ensure [quality criteria]

4. **Validate**
   - Test [aspects]
   - Verify [requirements met]

## Best Practices

- **[Practice 1]**: [Reasoning]
- **[Practice 2]**: [Benefit]
- **[Practice 3]**: [Why important]

## Common Patterns

### [Pattern 1]
**When**: [Scenario]
**How**: [Implementation approach]
**Why**: [Benefits]

### [Pattern 2]
**When**: [Scenario]
**How**: [Implementation approach]
**Why**: [Benefits]

## Anti-Patterns

❌ **Don't**: [Bad practice]
   - Why it fails: [Reason]
   - Better approach: [Alternative]

❌ **Avoid**: [Common mistake]
   - Problem: [What goes wrong]
   - Instead: [Correct way]

## Examples

### Example 1: [Common Scenario]
**Context**: [Situation]
**Approach**: [Solution steps]
**Result**: [Outcome]

## Tools & Technologies

- **[Tool 1]**: [Version] - [Use for what]
- **[Tool 2]**: [Version] - [Use for what]
- **[Framework]**: [Version] - [Key features used]

Process/Workflow Skill Template

---
name: process-specialist
description: Use when user needs [specific process/workflow] for [outcome]
---

# Process Specialist

## Purpose

Guides [specific process] to achieve [specific outcome]. Ensures [quality aspects] through [methodology].

## When to Use

- Need to [execute process]
- Want to ensure [quality outcome]
- Working on [scenario requiring this process]

## Core Process

### Phase 1: [Name]
**Goal**: [What to achieve]

Steps:
1. [Action 1]: [Details]
2. [Action 2]: [Details]
3. [Action 3]: [Details]

**Outputs**: [What you have after this phase]

### Phase 2: [Name]
**Goal**: [What to achieve]

Steps:
1. [Action 1]: [Details]
2. [Action 2]: [Details]

**Outputs**: [What you have after this phase]

### Phase 3: [Name]
**Goal**: [What to achieve]

Steps:
1. [Action 1]: [Details]
2. [Action 2]: [Details]

**Deliverable**: [Final output]

## Decision Points

### When to [Decision]
- If [condition], then [choice A]
- If [condition], then [choice B]

## Quality Gates

After each phase, verify:
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]

## Best Practices

- **[Practice]**: [Why it matters]
- **[Practice]**: [Impact on quality]

## Common Pitfalls

- **Pitfall**: [What people do wrong]
  - **Impact**: [What happens]
  - **Solution**: [How to avoid]

Writing Tips

Be Specific

❌ "Use when working with databases" ✅ "Use when optimizing SQL queries for PostgreSQL 14+ production databases"

Be Actionable

❌ "Think about security" ✅ "Run OWASP ZAP scan and review all HIGH severity findings"

Be Structured

Use consistent heading levels:

## for major sections
### for subsections
#### for detailed breakdowns

Use Visual Indicators

✅ for good practices
❌ for anti-patterns
🔍 for investigation steps
⚠️ for warnings
💡 for tips

Include Context

Don't just list what to do—explain why:

## Instead of:
- Use connection pooling

## Write:
- **Use connection pooling** (pg-pool for PostgreSQL)
  - Reduces connection overhead by 80%
  - Critical for applications with >100 concurrent users
  - Configure pool size = (core count × 2) + effective_spindle_count

Skill Maintenance

When to Update

New version of core technology released
Better practices emerge in the field
User feedback reveals gaps
Related skills are created (cross-reference)

Version Control

Consider adding to frontmatter:

---
name: skill-name
description: One-line description
---

Skill Integration

Cross-References

Link to related skills:

## Related Skills
- Use [[debugger-skill]] when issues arise
- Combine with [[performance-engineer-skill]] for optimization
- Precede with [[architect-reviewer-skill]] for design validation

Skill Composition

Complex workflows can chain skills:

## Workflow
1. Use [[requirement-analyst]] to gather needs
2. Apply this skill for implementation
3. Use [[code-reviewer]] for quality assurance
4. Use [[deployment-engineer]] to ship

Examples

Example 1: Creating a Python Pro Skill

Context : Need a skill for advanced Python development

Process :

Define scope: Python 3.11+ with focus on FastAPI and type safety
Identify triggers: "modern Python", "type hints", "FastAPI"
Structure core capabilities:
- Python 3.11+ features (match statements, typing improvements)
- FastAPI framework patterns
- Type annotation best practices
Add workflow: Design API → Type models → Implement routes → Test
Include examples: FastAPI route with full type annotations

Result : A focused, actionable skill for modern Python development

Example 2: Creating a Git Workflow Skill

Context : Need to codify team's git branching strategy

Process :

Define scope: Git workflow for feature development
Identify triggers: "create branch", "make PR", "git workflow"
Structure as phases:
- Branch creation
- Development cycle
- PR process
- Merge strategy
Add decision points: When to rebase vs merge
Include examples: Standard feature development flow

Result : Clear procedural guide for consistent git usage

Validation Checklist

Before finalizing a skill, check:

Structure

Frontmatter complete (name, description)
Title and purpose clear
"When to Use" section has specific triggers
Core capabilities well-defined

Content

Information is accurate and current
Examples are realistic and helpful
Best practices are justified
Anti-patterns show alternatives

Usability

Can scan and find info quickly
Sections flow logically
Formatting is consistent
Cross-references are correct

Quality

No spelling/grammar errors
Technical terms defined
Code examples (if any) are correct
Meets all quality criteria above

Meta: About This Skill

This skill itself demonstrates the principles it teaches:

Clear frontmatter and structure
Specific "When to Use" triggers
Actionable workflows
Concrete examples
Quality criteria

When creating skills, use this as both a guide and a template.

Weekly Installs

Repository

404kidwiz/claud…e-skills

GitHub Stars

First Seen

Jan 24, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode48

claude-code47

codex45

gemini-cli44

cursor42

github-copilot40

AI 代码实施计划编写技能 | 自动化开发任务分解与 TDD 流程规划工具

50,900 周安装

Claude技能创建指南：技能开发模板与最佳实践 | skill-creator

🇨🇳中文介绍

技能创建器

目的

使用时机

核心技能结构

必需组件

相关 Skills

可选但推荐的组件

技能创建工作流程

步骤 1：定义范围

步骤 2：识别核心知识

步骤 3：构建工作流程

步骤 4：添加实用元素

步骤 5：编写清晰的触发器

技能质量标准

清晰性

完整性

具体性

可用性

技能模板

技术领域技能模板

流程/工作流技能模板

写作技巧

要具体

要可操作

要有结构

使用视觉指示器

包含上下文

技能维护

何时更新

版本控制

技能集成

交叉引用

技能组合

示例

示例 1：创建 Python 专家技能

示例 2：创建 Git 工作流技能

验证清单

结构

内容

可用性

质量

元信息：关于此技能

🇺🇸English

Skill Creator

Purpose

When to Use

Core Skill Structure

Required Components

Optional but Recommended Components

Skill Creation Workflow

Step 1: Define Scope

Step 2: Identify Core Knowledge

Step 3: Structure the Workflow

Step 4: Add Practical Elements

Step 5: Write Clear Triggers

Skill Quality Criteria

Clarity

Completeness

Specificity

Usability

Skill Templates

Technical Domain Skill Template

Process/Workflow Skill Template

Writing Tips

Be Specific

Be Actionable

Be Structured

Use Visual Indicators

Include Context

Skill Maintenance

When to Update

Version Control

Skill Integration

Cross-References

Skill Composition

Examples

Example 1: Creating a Python Pro Skill

Example 2: Creating a Git Workflow Skill