writing-skills

Automate Skill documentation creation and validation with test-driven checks.

968|43|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/GanyuanRan/Aegis --skill writing-skills-ganyuanran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/GanyuanRan/Aegis/tree/main/skills/writing-skills
Command: npx skills add https://github.com/GanyuanRan/Aegis --skill writing-skills-ganyuanran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This section guides teams to create clear, reusable Skill documents that are rigorously validated through a test-driven process, reducing ambiguity and drift when Skills are loaded by agents.

Core Features & Use Cases

  • Enforces YAML frontmatter with required fields (name, description) and structured sections
  • Guides RED-GREEN-REFACTOR testing of Skills using pressure scenarios and rationalization tracking
  • Supports progressive disclosure, references, and cross-skill reuse to keep metadata lean

Quick Start

Draft a minimal Skill with the required frontmatter and a concise body that includes one example scenario.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I validate Skill documentation before deployment?

You can validate Skill documentation by running automated readiness checks that enforce metadata rules, verify frontmatter correctness, and ensure structural consistency before deployment.

What is test-driven development for skill writing?

Test-driven development for skill writing is a process that uses RED-GREEN-REFACTOR testing with pressure scenarios to rigorously validate Skill documents and track rationalizations.

How do I automate YAML frontmatter validation for workflows?

Automating YAML frontmatter validation requires enforcing required fields like name and description, checking structure, and ensuring workflow coverage to maintain consistency across Skills.

Can I use progressive disclosure to keep Skill metadata lean?

Yes, you can use progressive disclosure alongside references and cross-skill reuse to keep Skill metadata lean while reducing ambiguity when agents load the Skills.

Why does my Skill documentation drift when loaded by agents?

Skill documentation drifts when loaded by agents due to ambiguity and lack of rigorous validation, which test-driven documentation processes and structured sections are designed to prevent.

When do I need test-driven skill documentation?

You need test-driven skill documentation when creating clear, reusable Skill documents to reduce ambiguity and drift, ensuring agents process workflows consistently and accurately.