writing-skills

Create and validate Claude Skills through RED-GREEN-REFACTOR testing cycles.

1|Updated Nov 22, 2025
One-click install
npx skills add https://github.com/gmliao/swift-state-tree --skill writing-skills-gmliao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/gmliao/swift-state-tree/tree/main/.agent/skills/Superpowers/writing-skills
Command: npx skills add https://github.com/gmliao/swift-state-tree --skill writing-skills-gmliao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, test-driven approach to creating and refining Skills, ensuring they are validated under pressure before deployment.

Core Features & Use Cases

  • RED-GREEN-REFACTOR discipline: Apply a rigorous testing loop to skill documentation, capturing baseline failures and explicit rationalizations.
  • Baseline testing patterns: Learn to observe agent behavior without a Skill to identify concrete failure modes.
  • Iterative refinement: Systematically close loopholes by updating counters and red flags, then re-test to ensure compliance.
  • Deployment readiness: Ensure Skills are deployable only after repeatable green outcomes.

Quick Start

Create a new Skill by drafting SKILL.md with frontmatter, write RED baseline scenarios to capture failures, implement GREEN content to address those failures, then REFACTOR to close new loopholes. Document rationalizations verbatim and re-run tests to verify compliance under pressure.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How to use test-driven development for writing agent skills?

Test-driven skill authoring applies RED-GREEN-REFACTOR cycles to documentation by capturing baseline agent failures, writing content to address them, then refining to close loopholes. This ensures validated, repeatable compliance before deployment.

What is the RED-GREEN-REFACTOR process for skill documentation?

RED-GREEN-REFACTOR for skill documentation involves drafting YAML frontmatter, writing RED scenarios to capture baseline failures, implementing GREEN content to fix them, and refactoring to close new loopholes and prevent rationalizations.

Why do agent skills fail under pressure without baseline testing?

Agent skills fail under pressure when baseline testing patterns are skipped, leaving loopholes for rationalizations. Observing agent behavior without a skill first identifies concrete failure modes to systematically close during iterative refinement.

How do I validate Claude Skills before deployment?

Validate Claude Skills before deployment by enforcing iterative RED-GREEN-REFACTOR test cycles. Skills reach deployment readiness only after achieving repeatable green outcomes that confirm compliance under pressure and prevent rationalizations.

Can I apply TDD methodology to edit existing skill documentation?

Yes, TDD methodology applies to authoring, editing, and pre-deployment validation of skills. You update counters and red flags in existing structured sections, then re-run tests to verify compliance and close newly identified loopholes.

What are the limitations of using TDD for skill authoring?

TDD for skill authoring requires drafting structured YAML frontmatter and documenting rationalizations verbatim. It is unsuitable if you cannot observe baseline agent failures or lack resources for iterative refinement to achieve repeatable green outcomes.