skill-authoring
Creates and structures SKILL.md files for AI coding agents, including YAML frontmatter, trigger phrases, directive instructions, decision trees, code examples, and verification checklists. Use when the user asks to write a new skill, create a skill file, author agent capabilities, generate skill documentation, or define a skill template for Claude Code agents.
Best use case
skill-authoring is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Creates and structures SKILL.md files for AI coding agents, including YAML frontmatter, trigger phrases, directive instructions, decision trees, code examples, and verification checklists. Use when the user asks to write a new skill, create a skill file, author agent capabilities, generate skill documentation, or define a skill template for Claude Code agents.
Teams using skill-authoring should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/skill-authoring/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How skill-authoring Compares
| Feature / Agent | skill-authoring | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Creates and structures SKILL.md files for AI coding agents, including YAML frontmatter, trigger phrases, directive instructions, decision trees, code examples, and verification checklists. Use when the user asks to write a new skill, create a skill file, author agent capabilities, generate skill documentation, or define a skill template for Claude Code agents.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# Skill Authoring Guide You are authoring a SKILL.md for an AI coding agent. A well-written skill provides clear, actionable guidance that agents can follow consistently. ## Core Principle **A skill's description triggers it; the body teaches it.** The description tells the agent WHEN to use the skill. The content tells the agent HOW to execute it. ## Skill Anatomy ### SKILL.md Structure ```markdown --- name: [lowercase-hyphenated-name] description: [Concrete actions + "Use when..." clause] version: [Semantic version] triggers: - [keyword 1] - [keyword 2] tags: - [tag 1] --- # [Skill Title] [Introduction paragraph explaining purpose] ## Core Principle **[Single most important rule in bold]** ## [Main Content Sections] ## [Decision Points] ## [Verification Checklist] ``` ### Frontmatter Fields | Field | Required | Constraints | |-------|----------|-------------| | name | Yes | Lowercase alphanumeric + hyphens, 1–64 chars | | description | Yes | Must include "Use when..." clause; 1–1024 chars | | version | Yes | Semantic version (e.g. `1.0.0`) | | triggers | Recommended | Natural-language phrases that activate the skill | | tags | Recommended | Categorization tags | ## Writing Effective Triggers Triggers should be phrases users naturally type. **Good triggers:** - "write tests first" - "tdd" - "test driven development" **Bad triggers:** - "testing methodology" (too vague) - "red-green-refactor-cycle-for-test-driven-development" (too specific) - "skill-123" (not natural language) ### Trigger Guidelines 1. **Natural language** — How would a human ask for this? 2. **Multiple variations** — Different ways to say the same thing 3. **Specific enough** — Don't trigger on too many queries 4. **Common terms** — Use terms people actually use ## Writing Skill Content ### Voice and Tone Use **second person, present tense, active voice**: - ✅ "Write the test first" - ✅ "You are implementing TDD" - ❌ "The developer should..." (passive) - ❌ "It is recommended that..." (wordy) ### Structure Guidelines 1. **Start with context** — What is the agent doing and why 2. **State the core principle** — Most important rule upfront 3. **Provide process** — Step-by-step guidance 4. **Include examples** — Concrete illustrations 5. **Add a checklist** — Verification criteria 6. **End with integration** — How this connects to other skills ### Directive Language | Strength | Examples | |----------|----------| | Strong (critical rules) | "You MUST…", "ALWAYS…", "NEVER…", "Do NOT…" | | Soft (recommendations) | "Prefer…", "Consider…", "When possible…" | ## Content Patterns ### Decision Trees ```markdown ## Decision: [What to Decide] If [condition A]: → [Action for A] If [condition B]: → [Action for B] If uncertain: → [Default action] ``` ### Process Steps ```markdown ### Step 1: [Action] [Detailed explanation] **Verification:** [How to know step is complete] ### Step 2: [Action] ... ``` ### Code Examples ```typescript // BAD const result = doTheThing(badInput); // GOOD const validated = validate(input); const result = doTheThing(validated); ``` ## Anti-Patterns to Avoid | Anti-pattern | Problem | Fix | |--------------|---------|-----| | The Encyclopedia | Too much info, agent gets lost | Focus on actionable guidance only | | The Vague Guide | "Consider best practices" | Be specific: "Use Arrange-Act-Assert" | | The Constraint-Free Skill | No clear rules, agent improvises | Include explicit constraints | | The Monologue | Wall of text | Use headers, lists, tables, code blocks | | The Outdated Skill | References deprecated patterns | Version skills and review periodically | ## Skill Testing Before publishing, verify: 1. **Trigger test** — Does it activate on expected phrases? 2. **Completeness test** — Can the agent follow it without external info? 3. **Clarity test** — Is every instruction unambiguous? 4. **Contradiction test** — No conflicting guidance? 5. **Edge case test** — Handles unusual situations? ## Pack Organization Group related skills under a named pack directory. See `PACKS.md` for full pack manifest format and filesystem conventions. ``` packs/ ├── testing/ │ ├── pack.json │ ├── red-green-refactor/ │ │ └── SKILL.md │ └── test-patterns/ │ └── SKILL.md ``` ## Skill Maintenance See `MAINTENANCE.md` for detailed versioning policy. Quick reference: **Version increments:** - **Patch (1.0.x):** Typos, clarifications, minor fixes - **Minor (1.x.0):** New sections, examples, capabilities - **Major (x.0.0):** Breaking changes, fundamental rewrites **Deprecation frontmatter:** ```yaml deprecated: true deprecatedReason: "Superseded by skill-v2" deprecatedSince: "2024-01-15" ``` Add a visible notice at the top of the body: `> **DEPRECATED:** Use [skill-v2] instead.` ## Publication Checklist Before publishing, confirm: - [ ] Frontmatter is complete and valid (name, description, version) - [ ] Description includes concrete actions and a "Use when…" clause - [ ] Triggers are natural-language phrases, specific but not over-fitted - [ ] Core principle is clear and prominent - [ ] Content uses headers, lists, or tables — no walls of text - [ ] Code examples demonstrate correct vs. incorrect usage - [ ] Verification criteria are included - [ ] Related skills are linked where applicable - [ ] No spelling/grammar errors - [ ] Tested with target agents against all trigger phrases
Related Skills
find-skills
Discovers, searches, and installs skills from multiple AI agent skill marketplaces (400K+ skills) using the SkillKit CLI. Supports browsing official partner collections (Anthropic, Vercel, Supabase, Stripe, and more) and community repositories, searching by domain or technology, and installing specific skills from GitHub. Use when the user wants to find, browse, or install new agent skills, plugins, extensions, or add-ons; asks 'is there a skill for X' or 'find a skill for X'; wants to explore a skill store or marketplace; needs to extend agent capabilities in areas like React, testing, DevOps, security, or APIs; or says 'browse skills', 'search skill marketplace', 'install a skill', or 'what skills are available'.
test-patterns
Applies proven testing patterns — Arrange-Act-Assert (AAA), Given-When-Then, Test Data Builders, Object Mother, parameterized tests, fixtures, spies, and test doubles — to help write maintainable, reliable, and readable test suites. Use when the user asks about writing unit tests, integration tests, or end-to-end tests; structuring test cases or test suites; applying TDD or BDD practices; working with mocks, stubs, spies, or fakes; improving test coverage or reducing flakiness; or needs guidance on test organization, naming conventions, or assertions in frameworks like Jest, Vitest, pytest, or similar.
red-green-refactor
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like 'make the test pass', 'test coverage', or 'unit tests before implementation'.
testing-anti-patterns
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.
verification-gates
Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations.
task-decomposition
Breaks down complex software, writing, or research tasks into small, atomic, independently completable units with dependency graphs and milestone breakdowns. Use when the user asks to plan a project, decompose a feature, create subtasks, split up work, or needs help organizing a large piece of work into a step-by-step plan. Triggered by phrases like "break down", "decompose", "where do I start", "too big", "split into tasks", "work breakdown", or "task list".
design-first
Guides the creation of technical design documents before writing code, producing architecture diagrams, data models, API interface definitions, implementation plans, and multi-option trade-off analyses. Use when the user asks to plan a feature, architect a system, design an API, explore implementation approaches, or requests a technical design or spec before coding — especially for complex features involving multiple components, ambiguous requirements, or significant architectural changes.
trace-and-isolate
Applies systematic tracing and isolation techniques to pinpoint exactly where a bug originates in code. Use when a bug is hard to locate, code is not working as expected, an error or crash appears with unclear cause, a regression was introduced between recent commits, or you need to narrow down which component, function, or line is faulty. Covers binary search debugging, git bisect for regressions, strategic logging with [TRACE] patterns, data and control flow tracing, component isolation, minimal reproduction cases, conditional breakpoints, and watch expressions across TypeScript, SQL, and bash.
root-cause-analysis
Performs systematic root cause analysis to identify the true source of bugs, errors, and unexpected behavior through structured investigation phases — not just treating symptoms. Use when a user reports a bug, crash, error, or broken behavior and needs to debug, troubleshoot, or investigate why something is not working; especially for complex or intermittent issues across multiple components. Applies the Five Whys method, hypothesis-driven testing, stack trace analysis, git blame/log evidence gathering, and causal chain documentation to isolate and confirm root causes before applying any fix.
hypothesis-testing
Applies the scientific method to debugging by helping users form specific, testable hypotheses, design targeted experiments, and systematically confirm or reject theories to find root causes. Use when a user says their code isn't working, they're getting an error, something broke, they want to troubleshoot a bug, or they're trying to figure out what's causing an issue. Concrete actions include isolating failing components, forming and testing hypotheses, analyzing error messages, tracing execution paths, and interpreting test results to narrow down root causes.
structured-code-review
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR feedback, pull request review, or wants their code checked for bugs, style issues, or vulnerabilities — triggered by phrases like "review my code", "check this PR", "review my changes", "pull request review", or "code feedback".
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist; when serial troubleshooting is too slow; or when multiple investigators can divide root-cause analysis work. Provides structured phases for problem decomposition, thread assignment, sync points with Continue/Pivot/Converge decisions, and final report synthesis.