writing-skills

Create and edit Skill documentation using a RED-GREEN-REFACTOR workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents sloppy or incomplete Skills by enforcing test-driven development (TDD) when creating or editing skill documentation, so agents reliably comply under pressure.

Core Features & Use Cases

  • TDD for Documentation: Converts skill authorship into a RED-GREEN-REFACTOR cycle using pressure scenarios with subagents.
  • Baseline Failure Capture: Documents exactly how agents rationalize violations without the skill, so the skill targets real failure modes.
  • Loophole-Closing Bulletproofing: Adds explicit counters, “red flags,” and re-tests after new rationalizations emerge.
  • Claude Search Optimization (CSO): Ensures metadata (especially description) focuses on triggering conditions to improve discovery and correct loading.

Quick Start

Create a pressure scenario that tempts the agent to violate the rule, run it without the new skill to capture baseline rationalizations verbatim, then write the minimal skill and re-run the same scenario to verify compliance.

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 for documentation and skill authoring?

Test-driven development for documentation applies a RED-GREEN-REFACTOR cycle to skill authoring. You capture baseline agent failures verbatim, write minimal skill instructions to fix them, then refactor to close loopholes and ensure agent compliance under pressure.

Why does my AI agent rationalize violations and ignore prompt instructions under pressure?

Agents rationalize violations when skill instructions teach assumed interpretations rather than explicit behaviors. Capturing baseline failures verbatim without the new skill reveals real failure modes, allowing you to add explicit loophole counters and red flags to enforce compliance.

What is the best way to improve search optimization for AI agent skills?

Search optimization for agent skills requires encoding metadata with specific triggering conditions. Focusing the description on when to use the skill, without summarizing its workflow, improves discovery and ensures correct loading during high-pressure scenarios.

How do I bulletproof prompts against emerging rationalizations and edge cases?

Bulletproofing prompts involves adding explicit counters and red flags after baseline failure capture. You must re-test the agent with subagents using pressure scenarios whenever new rationalizations emerge to verify the updated documentation maintains strict compliance.

Can I update existing skill documentation using a test-driven workflow?

Updating existing skills uses the same test-driven development workflow as authoring new ones. You run pressure scenarios to capture verbatim failures, apply RED-GREEN-REFACTOR cycles, and update metadata to target real agent failure modes without summarizing workflow steps.