writing-skills

Create and maintain Skills documentation with test-driven development workflows.

7.6k|721|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/jnMetaCode/superpowers-zh --skill writing-skills-jnmetacode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/jnMetaCode/superpowers-zh/tree/main/skills/writing-skills
Command: npx skills add https://github.com/jnMetaCode/superpowers-zh --skill writing-skills-jnmetacode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills provide a standardized, test-driven framework for creating, editing, and validating Skills documentation to ensure clarity, consistency, and verifiable quality across teams.

Core Features & Use Cases

  • Frontmatter discipline: enforces YAML frontmatter with name and description and constrains length per specification.
  • Progressive disclosure: loads references, scripts, and background guides only when needed to minimize context load.
  • TDD-aligned workflow: prescribes red-green-refactor cycles for skill creation and maintenance, with test scaffolds and evaluation checklists.
  • Cross-skill reuse: promotes linking to existing skills to reduce duplication and improve discoverability.
  • Organization guidelines: supports self-contained SKILL.md with optional directories for scripts, references, and assets.

Quick Start

Create SKILL.md with a name and concise frontmatter, then describe the skill using the sections and progressive-disclosure approach.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write AI agent documentation using a test-driven development workflow?

AI agent documentation uses a test-driven development workflow by applying red-green-refactor cycles to skill creation, ensuring clear and verifiable guidance through test scaffolds and structured SKILL.md layouts.

What is progressive disclosure in skill documentation and when should I use it?

Progressive disclosure in skill documentation loads references, scripts, and background guides only when needed to minimize context load. Use it when organizing self-contained SKILL.md files with optional asset directories.

How do I validate frontmatter requirements before deploying a SKILL.md file?

To validate frontmatter requirements before deployment, check that your SKILL.md enforces YAML frontmatter with a name and description, constraining length per specification to ensure readiness across AI agents.

Can I use this test-driven framework to edit existing skills or is it only for creating new ones?

You can use this test-driven framework to edit existing skills, create new ones, and validate readiness before deployment. It applies red-green-refactor cycles to both skill creation and maintenance.

What is the best way to organize skill documentation to improve cross-skill reuse and discoverability?

The best way to organize skill documentation for cross-skill reuse is linking to existing skills to reduce duplication, using a self-contained SKILL.md with optional directories for scripts, references, and assets.

Do I need external dependencies to maintain skill documentation with this framework?

You do not need external dependencies to maintain skill documentation with this framework. It operates independently with no required dependencies, enforcing frontmatter discipline and progressive disclosure natively.