writing-skills

Enforce test-driven documentation for SKILL.md files before deployment.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authoring skill documentation without enforced testing causes agents to skip critical validation and propagate rationalizations, so writing-skills brings the pre-deployment discipline needed for every new or edited SKILL.md. It frames the pain of shipping untested guidance by forcing authors to watch agents fail baseline scenarios before they write any documentation.

Core Features & Use Cases

  • TDD Mapping: A complete RED-GREEN-REFACTOR mapping clarifies pressure scenarios, documentation writing, and loophole closure so no skill ships before it is proven.
  • Rationalization Defenses: Pressure scenarios, rationalization tables, red-flag checklists, and description rewrites capture excuses and close every loophole an agent might exploit.
  • Discovery Discipline: Naming conventions, description guidelines, keyword coverage, and cross-reference rules keep new or edited skills consistent, searchable, and compliant before deployment; use this when validating a discipline-enforcing skill such as a security or verification directive.

Quick Start

Command the agent to run the writing-skills workflow before authoring or editing any other skill.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I test agent skill documentation before deployment?

Test agent skill documentation by capturing failing baseline scenarios where agents fail before you write any docs, enforcing a test-driven approach that prevents unchecked deployments and unvalidated guidance.

What is TDD for skill writing and how does it work?

TDD for skill writing applies a RED-GREEN-REFACTOR mapping to documentation, clarifying pressure scenarios, documenting loopholes, and closing rationalization gaps so no skill ships before it is proven.

How do I stop agents from rationalizing and skipping validation rules?

Stop agent rationalization by building pressure scenarios, rationalization tables, and red-flag checklists that capture excuses and close every loophole an agent might exploit during deployments.

How do I enforce naming conventions and keyword coverage for agent skills?

Enforce naming conventions and keyword coverage by applying discovery discipline rules that keep new or edited skills consistent, searchable, and compliant before deployment.

Do I need to capture failing baselines before writing CLAUDE-style SKILL.md files?

Yes, capturing failing baselines is required before writing CLAUDE-style SKILL.md files, forcing authors to watch agents fail baseline scenarios and resist rationalizations under pressure.

When should I use a test-driven documentation workflow for agent skills?

Use a test-driven documentation workflow whenever you create or edit discipline-enforcing skills such as security or verification directives, ensuring agents cannot skip critical validation checks.