writing-skills

Create and validate skills using a TDD-inspired red-green-refactor process.

2|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/passionseed/ps_app --skill writing-skills-passionseed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/passionseed/ps_app/tree/main/.agent/skills/writing-skills
Command: npx skills add https://github.com/passionseed/ps_app --skill writing-skills-passionseed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills provide a structured, test-driven approach to documenting proven techniques, patterns, or tools so that others can reliably reuse them and avoid regressions in future sessions.

Core Features & Use Cases

  • Applies a RED-GREEN-REFACTOR discipline to skill documentation to prevent drift
  • Establishes baseline testing, rationalization tracking, and red-flag mechanisms
  • Enables progressive disclosure with concise frontmatter and lightweight inline content for fast discovery

Quick Start

Begin by drafting a minimal SKILL.md that passes a failing baseline scenario and then expand iteratively.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write skills documentation using a TDD-inspired process?

To write skills using a TDD-inspired process, draft a minimal SKILL.md that passes a failing baseline scenario, then expand iteratively through red-green-refactor cycles to ensure tested, regression-free documentation patterns.

What is progressive disclosure in skill authoring?

Progressive disclosure in skill authoring is a documentation design pattern that uses concise frontmatter and lightweight inline content to enable fast discovery while preventing content drift across projects.

How do I prevent documentation drift when authoring skills?

You prevent documentation drift when authoring skills by applying rationalization tracking, baseline testing, and red-flag mechanisms within a structured red-green-refactor discipline to validate reusable patterns.

What is the best way to structure a SKILL.md file for reuse?

The best way to structure a SKILL.md file for reuse is to enforce frontmatter with name and description, maintain a compact content body, and optionally include scripts, references, and assets for progressive disclosure.

Does writing skills require any external dependencies or components?

Writing skills does not require any external dependencies or components, allowing skill authors to immediately establish baseline testing and rationalization tracking without environment setup barriers.