writing-skills

Adapt test-driven development to agent skill documentation with YAML frontmatter.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of untested, brittle skill documentation that agents may misapply or partially follow under pressure, causing inconsistent behavior after deployment.

Core Features & Use Cases

  • Test-driven skill authoring: Converts documentation changes into discipline-enforcing checks by using pressure scenarios and subagents to establish baseline failures and verified compliance.
  • Rationalization-proof structure: Guides writers to document the exact “why” agents do wrong, then close loopholes with explicit counters and red-flag stop conditions.
  • Discovery-ready metadata discipline: Enforces concise, trigger-focused frontmatter so skills are found correctly and not skipped due to workflow-summary descriptions.

Quick Start

Use the writing-skills skill when creating or updating a skill document and you have not yet run a baseline scenario to confirm how agents fail without the skill.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write agent skill documentation that prevents loopholes and misapplication?

Test-driven skill documentation adapts TDD by establishing failing baseline scenarios and verifying compliance after edits. This red-green-refactor cycle closes rationalization loopholes to prevent agents from misapplying instructions during deployment.

What is test-driven development for agent skill authoring?

Test-driven skill authoring converts documentation changes into discipline-enforcing checks. It uses pressure scenarios and subagents to establish baseline failures, then verifies compliance after edits to prevent brittle, untested skill documentation from causing inconsistent agent behavior.

How do I format YAML frontmatter for skill discovery in agent directories?

Skill discovery requires YAML frontmatter with a name field and a trigger-only description. Enforcing concise, trigger-focused metadata prevents skills from being skipped in agent directories due to workflow-summary descriptions.

Why do agents partially follow skill documentation under pressure?

Agents partially follow documentation under pressure due to rationalization loopholes. Untested, brittle skill documentation lacks explicit counters and red-flag stop conditions, causing inconsistent behavior when deployed.

When should I run a baseline scenario during skill creation?

Run a baseline scenario when creating or updating a skill document before making any edits. This confirms how agents fail without the skill, establishing a failing baseline that verifies compliance after subsequent documentation changes.

Does skill documentation require third-person rule wording for agent compliance?

Skill documentation requires third-person rule wording to ensure agent compliance. This structural discipline enforces consistent instruction following by guiding writers to document exact failure reasons and close loopholes with explicit counters.