/skill-authoring

name: skill-authoring
description: 'Guide creating Claude Code skills with TDD and persuasion principles. Use for new skill development.'
alwaysApply: false
category: skill-development
tags:
- authoring
- tdd
- skills
- writing
- best-practices
- validation
modules:
- modules/tdd-methodology.md
- modules/persuasion-principles.md
- modules/description-writing.md
- modules/progressive-disclosure.md
- modules/graphviz-conventions.md
- modules/deployment-checklist.md
- modules/advanced-patterns.md
- modules/authentication.md
- modules/error-handling.md
- modules/examples.md
- modules/testing-with-subagents.md
- modules/troubleshooting.md
- modules/validation.md
dependencies:
- modular-skills
- abstract:skill-graph-audit
estimated_tokens: 1500
model_hint: standard

Skill Authoring Guide

When NOT To Use

• Scoring a skill that already exists (use `abstract:skills-eval`)
• Authoring a hook (use `abstract:hook-authoring`)
• Verifying the skill fires (use `abstract:subagent-testing`)

Overview

Writing effective Claude Code skills requires Test-Driven Development (TDD) and persuasion principles from compliance research. We treat skill writing as process documentation that needs empirical validation rather than just theoretical instruction. Skills are behavioral interventions designed to change model behavior in measurable ways.

By using TDD, we ensure skills address actual failure modes identified through testing. Optimized descriptions improve discovery, while a modular structure supports progressive disclosure to manage token usage. It states intent, constraints and exit criteria, and leaves the path between them to the session doing the work. `modules/persuasion-principles.md` carries the strength budget that decides which of the three each statement is.

The Iron Law

**NO SKILL WITHOUT A FAILING TEST FIRST**

Every skill must begin with documented evidence of Claude failing without it. This validates that you are solving a real problem. No implementation should proceed without a failing test, and no completion claim should be accepted without evidence. Detailed enforcement patterns for adversarial verification and coverage gates are available in `imbue:proof-of-work`.

Skill Types

We categorize skills into three types: **Technique** skills for specific methods, **Pattern** skills for recurring solutions, and **Reference** skills for quick lookups and checklists. This helps organize interventions into the most effective format for the task.

Quick Start

Skill Analysis

\`\`\`bash

Analyze skill complexity

python scripts/skill_analyzer.py

Estimate tokens

python scripts/token_estimator.py \`\`\`

Validation

\`\`\`bash

Validate skill structure

python scripts/abstract_validator.py --check \`\`\`

**Verification**: Run analysis and review token estimates before proceeding.

Description Optimization

Skill descriptions must be optimized for semantic search and explicit triggering. Follow the formula `[What it does] + [When to use it] + [Key triggers]`. Use a third-person voice (e.g., "Guides...", "Provides...") and include specific, concrete use cases. Avoid marketing language or vague phrases like "helps with coding."

Skill Character Budget (Claude Code 2.1.32+)

Skill description character budgets now **scale with context window** at 2% of available context. This means:

| Context Window | Description Budget | |---------------|-------------------| | 200K (Sonnet/Haiku) | ~4,000 characters | | 1M (Opus 4.6 GA) | ~20,000 characters |

Previously constrained skills can use more descriptive text on larger windows. However, keep descriptions concise regardless: longer is not better. The scaling primarily prevents truncation for skills with legitimately complex trigger conditions, not as an invitation to add verbose content.

Plugin Name Auto-Display (Claude Code 2.1.33+)

Plugin names are now automatically shown alongside skill descriptions in the `/skills` menu. Do not repeat the plugin name in skill descriptions: it is redundant and wastes character budget. Focus descriptions on what the skill does and when to use it.

The TDD Cycle for Skills

RED Phase: Document Baseline Failures

Establish empirical evidence that an intervention is needed. Create at least three pressure scenarios that combine time pressure and ambiguity. Run these in a fresh instance without the skill active and document the exact failures, such as skipped error handling or missing validation.

GREEN Phase: Minimal Skill Implementation

Create the smallest intervention that addresses the documented failures. Write the `SKILL.md` with required frontmatter and content that directly counters the baseline failures. Include one example of correct behavior and verify that the same pressure scenarios now show measurable improvement.

REFACTOR Phase: Sharpen the Triggers

Eliminate the ability for Claude to explain away requirements. Run pressure scenarios with the skill active to identify common rationalizations, such as claiming a task is "too simple" for the full process. Add explicit counters, such as exception tables and red flag lists, until rationalizations stop.

Deciding Whether a Skill Applies

Skills must explicitly counter patterns where Claude attempts to bypass requirements. Common excuses include claiming a task is "too simple" or that a "spirit vs letter of the law" approach is sufficient. Skills should include red flag lists for self-checking, such as "Stop if you think: this is too simple for the full process." When exceptions are necessary, document them explicitly to prevent unauthorized shortcuts.

Module References

For detailed implementation guidance:

**Core authoring cycle:**

• **TDD Methodology**: See `modules/tdd-methodology.md` for RED-GREEN-REFACTOR cycle details
• **Instruction Strength**: See `modules/persuasion-principles.md` for how hard to push, and what earns an invariant
• **Description Writing**: See `modules/description-writing.m