writing-skills

Creates and validates skill documentation using RED-GREEN-REFACTOR with subagent testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills provide a test-driven approach to process documentation, ensuring that skill creation, validation, and deployment follow a repeatable, verifiable cycle that minimizes regressions and rationalizations.

Core Features & Use Cases

  • Discipline-enforcing guidance for drafting SKILL.md with frontmatter constraints (name and description) and structured content
  • Techniques for red-green-refactor cycles, pressure scenarios, and rationalization tracking
  • Patterns for progressive disclosure, red flags, and deployment checks to improve reliability and discoverability
  • Guidelines for documenting references, tests, and cross-skill references to build reusable knowledge
  • Clear criteria for evaluating skill bulletproofing and meta-testing across agent interactions

Quick Start

Start by documenting a baseline RED test scenario for a new skill, then implement a minimal GREEN skill and verify with REFACTOR to ensure resilience.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use TDD to write bulletproof process documentation?

Test-driven documentation uses a RED-GREEN-REFACTOR cycle to validate process patterns, starting with a failing baseline test scenario, implementing minimal documentation, and refactoring to ensure resilience and prevent regressions.

What is the best way to structure skill documentation for safe deployment?

Structuring skill documentation requires specifying frontmatter constraints, applying progressive-disclosure guidelines, and documenting deployment checks, red flags, and safety considerations to optimize discovery, reuse, and safe integration.

How do I prevent rationalizations when creating process documentation?

Preventing rationalizations in process documentation involves applying discipline-enforcing techniques like pressure scenarios and rationalization tracking within a red-green-refactor cycle to ensure test-driven evidence guides improvement.

Can I validate process patterns using subagent testing before deployment?

Yes, validating process patterns with subagent testing applies red-green-refactor cycles and meta-testing across agent interactions to evaluate skill bulletproofing and ensure safe integration without regressions.

Does test-driven skill creation work for documenting cross-skill references?

Test-driven skill creation supports documenting references, tests, and cross-skill references by encoding guidelines for building reusable knowledge while ensuring progressive disclosure and frontmatter constraints are met.