superpowers-writing-skills

Structure Skill documentation with frontmatter and progressive-disclosure patterns.

2|1|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/aldoborrero/agent-kit --skill superpowers-writing-skills-aldoborrero
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpowers-writing-skills
Source: https://github.com/aldoborrero/agent-kit/tree/main/skills/superpowers/writing-skills
Command: npx skills add https://github.com/aldoborrero/agent-kit --skill superpowers-writing-skills-aldoborrero

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps creators craft high-quality Skill documentation that is easy for Claude to discover and apply, reducing misinterpretation and deployment risk.

Core Features & Use Cases

  • Structured frontmatter and body: ensures essential metadata exists and the skill can be loaded in the correct context.
  • Progressive disclosure patterns: organizes content so Claude loads only what is needed, when needed.
  • Evaluation-driven development: integrates RED-GREEN-REFACTOR style testing for skills, including rationalization tracking.
  • Real-world applicability: supports both discipline-enforcing and reference-style skills across Claude Code and pi-coding-agent ecosystems.

Quick Start

Draft a minimal Skill that captures the RED-GREEN-REFACTOR workflow and outline a baseline testing plan.

Frequently Asked Questions about superpowers-writing-skills

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

FAQPage Schema
How do I write agent skills documentation that Claude can discover and apply correctly?

To write agent skills documentation that Claude can discover and apply correctly, structure the frontmatter with essential metadata and organize the body using progressive-disclosure patterns so the agent loads only what is needed, when needed.

What is progressive disclosure in skill writing and why does it matter?

Progressive disclosure in skill writing is a content organization pattern that structures documentation so Claude loads only what is needed, when needed, reducing misinterpretation and deployment risk across discipline-enforcing and reference-style skills.

Can I use test-driven development to evaluate and refine skill documentation?

Yes, you can use test-driven development to evaluate and refine skill documentation by implementing RED-GREEN-REFACTOR workflows with subagents, tracking rationalizations, and iteratively refining the skill body based on evaluative tests.

Does this skill writing approach work for both discipline-enforcing and reference-style skills?

Yes, this skill writing approach works for both discipline-enforcing and reference-style skills across Claude Code and pi-coding-agent ecosystems, ensuring structured frontmatter and body formats that support correct loading in the appropriate context.

What's the best way to structure frontmatter and body content for a new agent skill?

The best way to structure frontmatter and body content for a new agent skill is to include essential metadata like name and description in the frontmatter, then apply progressive-disclosure patterns in the body with RED-GREEN-REFACTOR workflows and evaluative tests.

Why does my agent skill fail to load or get misinterpreted by Claude?

Agent skills fail to load or get misinterpreted by Claude when frontmatter lacks essential metadata like name and description, or when the body does not follow progressive-disclosure patterns, increasing misinterpretation and deployment risk.