Creating Skills

Automate skill documentation and validation through test-driven development cycles.

41|27|Updated Oct 6, 2025

Search Tags:#testing #tdd #documentation #subagents #quality-assurance #skill-development #process-documentation

Ready to run

npx skills add https://github.com/obra/clank --skill creating-skills-obra

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Creating Skills
Source: https://github.com/obra/clank/tree/main/skills/meta/creating-skills
Command: npx skills add https://github.com/obra/clank --skill creating-skills-obra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates poorly documented processes by applying Test-Driven Development principles to skill creation, ensuring every technique is verified before deployment.

Core Features & Use Cases

RED-GREEN-REFACTOR Cycle: Systematically test, document, and refine skills using subagent validation.
Rationalization Prevention: Build skills that resist common excuses and workarounds under pressure.
Use Case: When you discover a debugging technique that consistently works, use this Skill to document it in a way that's proven effective through testing.

Quick Start

Create a pressure scenario and test it with a subagent before writing any documentation to establish baseline behavior.

Frequently Asked Questions about Creating Skills

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I document a debugging technique so it's reliable and tested?▼

Test-driven development for skill creation validates techniques through subagent pressure tests before writing documentation. Apply RED-GREEN-REFACTOR cycles to establish baseline behavior, then structure your findings in a SKILL.md template to ensure the documented process resists common workarounds and remains effective under real conditions.

What's the best way to prevent poorly documented processes in my workflow?▼

Implement test-driven documentation by creating pressure scenarios with subagents first, then writing documentation only after baseline behavior is verified. This approach eliminates excuses and loopholes by proving your process works before deployment.

How do I ensure my process documentation passes quality validation?▼

Use RED-GREEN-REFACTOR cycles to validate skills systematically: create test scenarios, verify behavior with subagents, then refactor documentation into a compliant SKILL.md structure. This workflow confirms your documentation meets search optimization and integration requirements before release.

Can I use test-driven development to create reusable skills across different domains?▼

Yes. TDD for skill creation applies across domains by establishing pressure-test baselines and structured templates. The RED-GREEN-REFACTOR cycle and SKILL.md compliance framework ensure your documented techniques remain effective and self-contained regardless of the domain.

What happens if I skip testing during process documentation?▼

Untested documentation often contains hidden assumptions, workarounds, and loopholes that fail under pressure. TDD catches these gaps early by validating behavior against baseline scenarios before deployment, ensuring your final documentation is bulletproof.