writing-skills

Automate Skill documentation creation and testing with the RED-GREEN-REFACTOR workflow.

1|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/sswapnil2/ai-config-fintech --skill writing-skills-sswapnil2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/sswapnil2/ai-config-fintech/tree/main/skills/superpowers/writing-skills
Command: npx skills add https://github.com/sswapnil2/ai-config-fintech --skill writing-skills-sswapnil2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skills documentation written with a test-driven approach to capture reusable patterns, prevent drift, and guide future agent behavior.

Core Features & Use Cases

  • TDD-led skill authoring workflow (RED-GREEN-REFACTOR) for documentation
  • Clear frontmatter guidance (name + description) and structured content
  • Progressive disclosure patterns with references and inline guidance

Quick Start

Draft a new SKILL.md with proper frontmatter and then run the RED-GREEN-REFACTOR cycle to validate the skill.

Frequently Asked Questions about writing-skills

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

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

Test-driven development for skill documentation works by applying a RED-GREEN-REFACTOR workflow to author and validate SKILL.md files, enforcing frontmatter requirements and progressive disclosure to ensure deployment readiness.

What is the RED-GREEN-REFACTOR workflow for authoring skills?

The RED-GREEN-REFACTOR workflow is a test-driven development process for authoring skills that validates frontmatter, enforces progressive disclosure patterns, and runs deployment checks to ensure documentation meets structural requirements.

How do I validate frontmatter requirements for skill documentation?

To validate frontmatter requirements for skill documentation, draft your SKILL.md with the required name and description fields, then run the test-driven development workflow to enforce these structural checks automatically.

How do I prevent content drift in reusable skill documentation?

Prevent content drift in reusable skill documentation by using a test-driven development approach that captures reusable patterns, enforces progressive disclosure, and runs deployment checks to maintain consistency across edits.

What are the frontmatter requirements for deploying a new skill?

The frontmatter requirements for deploying a new skill mandate that the SKILL.md file includes both a name and a description, which are validated during the test-driven development cycle before deployment checks pass.

Does the skill writing process support progressive disclosure patterns?

Yes, the skill writing process supports progressive disclosure patterns by structuring content with references and inline guidance, which are validated through the test-driven development workflow to ensure proper documentation layering.