writing-skills

Apply test-driven development to validate skill documentation before deployment.

6|Updated Aug 19, 2025
One-click install
npx skills add https://github.com/lv416e/dotfiles --skill writing-skills-lv416e
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/lv416e/dotfiles/tree/main/dot_claude/skills/writing-skills
Command: npx skills add https://github.com/lv416e/dotfiles --skill writing-skills-lv416e

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating effective AI skills that reliably guide agents, especially under pressure, requires a robust development methodology. This skill applies Test-Driven Development (TDD) principles to process documentation, ensuring skills are bulletproof against rationalization.

Core Features & Use Cases

  • TDD for Documentation: Adapts the Red-Green-Refactor cycle to skill creation, testing with subagents before writing.
  • Bulletproofing Techniques: Incorporates persuasion principles (authority, commitment, social proof) and explicit anti-rationalization strategies.
  • Skill Structure & Optimization: Guides on effective SKILL.md structure, description writing, keyword optimization, and token efficiency.
  • Comprehensive Testing: Provides methodologies for testing discipline-enforcing, technique, pattern, and reference skills.

Quick Start

I want to create a new skill that enforces a strict code style. Use the writing-skills skill to guide me through the TDD-based creation process.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply test-driven development to skill documentation?

Test-driven development for skills follows the RED-GREEN-REFACTOR cycle: write tests with subagents first to observe baseline failure, then document the skill to pass those tests, then refactor for clarity. This ensures documentation guides agents reliably under pressure before deployment.

What's the best way to bulletproof AI skills against rationalization?

Bulletproofing applies persuasion principles—authority, commitment, social proof—and explicit anti-rationalization strategies to skill design. Pressure scenarios with subagents reveal loopholes in reasoning and process enforcement, closing them through iterative refinement.

How do I structure and optimize skill documentation for agent deployment?

Effective skill documentation requires clear structure in the SKILL.md format, keyword optimization for discoverability, token-efficient descriptions, and discipline-enforcing patterns. TDD validation ensures the documentation guides agents through complex workflows without deviation.

Can I use TDD methodology to test existing skills?

Yes. TDD applies to creating new skills and editing existing ones. Test methodology varies by skill type—discipline-enforcing, technique, pattern, and reference skills each require specific validation approaches to verify functionality in agent ecosystems.

What should I test before deploying a new skill to agents?

Before deployment, test skill documentation against baseline failure scenarios with subagents, verify compliance through the RED-GREEN-REFACTOR cycle, and validate that the skill enforces intended behavior under pressure conditions without allowing agent rationalization.

Why does test-first documentation matter for AI skill creation?

Test-first documentation catches design flaws before agents encounter them in production. Writing tests before documentation forces explicit reasoning about edge cases, failure modes, and persuasion vulnerabilities, resulting in skills that guide agent behavior reliably.