writing-skills

Author, validate, and deploy process-skills using test-driven documentation.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill writing-skills-alo-exp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/writing-skills
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill writing-skills-alo-exp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing skills documentation often lacks a formal validation loop. This skill provides a test-driven framework to create, verify, and deploy process documentation for skills, ensuring clarity, consistency, and repeatability across teams.

Core Features & Use Cases

  • Test-driven skills: Apply RED-GREEN-REFACTOR to skill documentation and ensure failing baseline tests are corrected by SKILL.md updates.
  • Structured workflow: Enforces frontmatter validation, description sections, and deployment checklist.
  • Quality discipline: Provides red flags, rationalization tables, and safe deployment controls to reduce risk when adding new skills.

Quick Start

Describe a pressure scenario and run it without the skill to observe baseline failures, then implement the skill following the RED-GREEN-REFACTOR cycle and verify with testing.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use test-driven development to write Claude skills documentation?

Test-driven skills documentation applies a RED-GREEN-REFACTOR cycle to skill authorship. You observe baseline failures by running pressure scenarios without the skill, then update the SKILL.md to correct those failures and verify consistency.

What is the RED-GREEN-REFACTOR cycle for process documentation?

The RED-GREEN-REFACTOR cycle for process documentation involves writing failing baseline tests for pressure scenarios, updating the skill documentation to make them pass, and refactoring the content to ensure clarity, consistency, and repeatability.

How do I validate Claude skill frontmatter and descriptions before deployment?

You validate Claude skill frontmatter and descriptions by enforcing a structured workflow that checks for required name and description fields, verifies three-section description formats, and runs safe deployment controls to reduce risk.

Do I need any external dependencies to apply TDD-guided skill authorship?

No external dependencies are required to apply TDD-guided skill authorship. The framework operates independently to enforce frontmatter validation, description sections, and deployment checklists for creating and editing process-skills.

What are the limitations of using TDD for skill documentation?

Using TDD for skill documentation requires defining explicit pressure scenarios upfront, meaning ambiguous or highly exploratory processes may be difficult to baseline test until concrete failure conditions are established.

Can writing-skills enforce deployment safety checks for new Claude skills?

Yes, writing-skills enforces deployment safety checks for new Claude skills by providing red flags, rationalization tables, and safe deployment controls to reduce risk when adding or editing process documentation.