writing-skills

Standardize Skill creation and validation with red-green-refactor documentation workflows.

4|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/atxinsky/skills --skill writing-skills-atxinsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/atxinsky/skills/tree/main/writing-skills
Command: npx skills add https://github.com/atxinsky/skills --skill writing-skills-atxinsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes the creation of Skills documentation by applying a test-driven approach to process documentation, reducing ambiguity and increasing discoverability and reliability.

Core Features & Use Cases

  • Guided Skill creation: defines the required frontmatter (name, description) and the recommended SKILL.md structure, enabling consistent Skill units.
  • Documentation-as-code discipline: emphasizes RED-GREEN-REFACTOR style validation for Skills before deployment.
  • Discovery & maintenance: improves searchability with explicit keywords and cross-references, and supports lightweight references for large Skills.

Quick Start

Create a new Skill directory under skills/, add SKILL.md at the root with YAML frontmatter containing name and description, and provide a concise Markdown body with sections like Overview, When to Use, Core Patterns, and Quick Start. Keep content focused and concise to ensure fast loading and reliable discovery.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I enforce TDD for skill documentation to reduce rationalization?

Apply a red-green-refactor workflow to skill documentation by defining explicit tests and rationalization tables before finalizing content. This ensures consistency and reduces ambiguity by validating behavior upfront during creation or editing.

What is the standard structure for process documentation to ensure reliability?

Standard process documentation requires YAML frontmatter with name and description, followed by a concise Markdown body featuring Overview, When to Use, Core Patterns, and Quick Start sections to guarantee consistent, discoverable skill units.

How do I validate skills before deployment to maintain quality assurance?

Validate skills before deployment by applying a documentation-as-code discipline using red-green-refactor cycles. This verifies the skill meets explicit specifications and maintains required frontmatter without rationalizing gaps.

Does test-driven documentation work for editing existing skills?

Test-driven documentation applies when creating new skills, editing existing ones, or verifying skills before deployment. It enforces standardized validation to ensure all modifications maintain structural consistency and reduce rationalization.

What's the best way to improve skill discoverability and searchability?

Improve skill discoverability by providing explicit keywords and cross-references within the documentation. Keeping content compact and testable also supports lightweight references for large skills, ensuring fast loading and reliable discovery.