writing-skills

Write and verify Skills using RED-GREEN-REFACTOR test-driven cycles.

3|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/BubbleBuffer/superpawers --skill writing-skills-bubblebuffer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/BubbleBuffer/superpawers/tree/main/skills/writing-skills
Command: npx skills add https://github.com/BubbleBuffer/superpawers --skill writing-skills-bubblebuffer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps teams ensure Skills are written, tested, and verified with a disciplined, test-driven process before deployment, reducing drift and misalignment between Skill documentation and actual behavior.

Core Features & Use Cases

  • Provides a structured approach to Skill creation, editing, and verification using a RED-GREEN-REFACTOR lifecycle.
  • Documents baseline failures, captures rationalizations, and builds counters and red flags to prevent common evasions under pressure.
  • Serves as a reusable template for Skill documentation, enabling consistent quality across the Skill library.

Quick Start

Read the SKILL.md and apply the RED-GREEN-REFACTOR workflow to craft and validate a new Skill.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
What is test-driven development for skill creation and verification?

Test-driven development for skill creation is a strict RED-GREEN-REFACTOR lifecycle that ensures skill documentation matches actual behavior by documenting baseline failures and iterating until tests pass. It reduces drift and misalignment before deployment.

How do I document and verify a skill using a RED-GREEN-REFACTOR cycle?

To document and verify a skill, capture baseline failures and rationalizations, build a rationalization table with counters, then iterate the RED-GREEN-REFACTOR cycle to produce bulletproof skill documentation that passes verification before deployment.

Why does skill documentation drift from actual behavior under pressure?

Skill documentation drifts under pressure due to common evasions. Capturing rationalizations and building counters and red flags into the test-driven documentation process prevents these evasions and maintains strict alignment during skill creation and editing.

Does test-driven skill creation work for editing existing skills?

Yes, test-driven skill creation applies to editing existing skills and verifying skills before deployment across the library. The RED-GREEN-REFACTOR workflow serves as a reusable template for consistent quality during any skill modification.

What's the best way to prevent misalignment between skill documentation and behavior?

The best way to prevent misalignment is applying a disciplined test-driven process that requires documenting baseline failures, building a rationalization table, and iterating RED-GREEN-REFACTOR cycles to verify skills before deployment across the library.