AgentSkillsCN

write-skill

掌握一种元技能，能够以正确格式与 [BRACKET] 区段，快速创建全新技能。

SKILL.md
--- frontmatter
name: write-skill
description: "Meta-skill for creating new skills in the proper format with [BRACKET] sections and correct structure."
last_updated: 2026-01-10
tools_required: [Write, Read]
agent_type: main_agent

Write Skill

Meta-skill for creating new skills with proper structure.

[GOAL]

Create well-structured skills that follow the [BRACKET] pattern and are easy for AI to parse and execute.

[CONTEXT]

Skills are executable instructions in markdown. They should be:

  • •Specific enough to execute without ambiguity
  • •Organized with clear sections
  • •Referenced not duplicated

[PROCESS]

1. Choose Location and Name

code
skills/
├── thinking/          # brainstorming, decision-making, critique
├── documentation/     # writing docs, planning
├── meetings/          # prep, follow-up
├── research/          # web research, investigation
├── memory/            # memory management
├── system/            # file organization, setup
└── coding/            # git, refactoring, testing

Name: lowercase-hyphen format (e.g., meeting-prep, write-planning-doc)

2. Create Folder Structure

code
skill-name/
├── SKILL.md          # Required: instructions
├── scripts/          # Optional: automation code
├── references/       # Optional: supporting docs
└── assets/           # Optional: templates

3. Write SKILL.md

markdown
---
name: skill-name
description: "One-line description"
last_updated: YYYY-MM-DD
tools_required: [Tool1, Tool2]
agent_type: main_agent | subagent | either
---

# Skill Title

Brief intro (1-2 sentences).

## See Also

- [[related-skill]] - Brief context
- [[another-skill]]

## [PERSONA]

Specific expert role (not generic like "helpful assistant").

## [GOAL]

One clear sentence describing what this accomplishes.

## [CONTEXT]

Why this skill exists (2-4 sentences).

## [PROCESS]

- Hyphenated, verb-first steps
- Reference specific files/paths
- Mention relevant tools if needed
- Specific enough to execute without ambiguity

## [IMPORTANT]

- Non-negotiable requirements (bullets)
- Common mistakes to avoid
- Tool-specific gotchas

4. Validation Checklist

  • •✅ References other docs instead of duplicating
  • •✅ Tool/MCP references included where relevant
  • •✅ Direct, practical tone - no fluff
  • •✅ Could someone execute this identically to intent?
  • •✅ Proper frontmatter (name matches folder)
  • •✅ [PERSONA] and [GOAL] present
  • •✅ [PROCESS] with verb-first steps
  • •✅ [IMPORTANT] for gotchas

[IMPORTANT]

  • •[PROCESS] steps start with verbs: Search, Read, Create, Update, Verify
  • •Be specific: Name files, paths, tools explicitly
  • •Link, don't duplicate: Reference single source of truth
  • •Keep [IMPORTANT] concise: Bullets only, non-negotiables
  • •Skills ARE the documentation (not separate docs + code)