writing-skills

Create and validate agent skills using test-driven development with subagent pressure scenarios.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/bill80362/laravel-thread-admin --skill writing-skills-bill80362
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/bill80362/laravel-thread-admin/tree/main/.github/superpowers/writing-skills
Command: npx skills add https://github.com/bill80362/laravel-thread-admin --skill writing-skills-bill80362

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphviz, and includes references (resource) components.

What problem does it solve? Writing documentation-style skills for AI agents often produces instructions that agents ignore or rationalize away under pressure. This Skill applies test-driven development to skill authoring: you run baseline pressure scenarios without the skill, observe exact failure rationalizations, write the minimal skill to address them, and iterate until compliance holds. ## Core Features & Use Cases - TDD-based skill authoring: Red-green-refactor cycle adapted to documentation, with baseline testing, minimal skill writing, and loophole closing. - Skill Discovery Optimization (SDO): Guidance on writing trigger-focused descriptions, keyword coverage, naming conventions, and token-efficient structure. - Pressure testing methodology: Reference docs cover multi-pressure subagent scenarios, rationalization tables, red-line lists, and persuasion principles grounded in published research. - Use Case: When creating a new discipline-enforcement skill (e.g., mandatory TDD), run a scenario combining time pressure, sunk cost, and fatigue without the skill, record the agent's excuses verbatim, then write targeted rebuttals and re-test until the agent complies. ## Quick Start Ask the agent to help you create a new skill by first running a baseline pressure scenario without it, then drafting the SKILL.md and iterating until the agent complies under pressure.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write a SKILL.md file for an AI agent?

Start with YAML frontmatter containing name and description fields, then write a concise body with overview, when-to-use triggers, core patterns, and common mistakes. Keep the description focused on trigger conditions starting with "Use when" rather than summarizing the workflow.

How to test whether an agent skill actually works?

Run pressure scenarios with subagents before writing the skill to capture baseline failures verbatim, then re-run the same scenarios with the skill loaded. Combine three or more pressures like time constraints, sunk cost, and authority to verify compliance holds under stress.

What makes a good skill description for discovery?

Write in third person starting with "Use when" followed by concrete trigger conditions, symptoms, and scenarios. Never summarize the skill's workflow in the description, since agents may follow the description shortcut instead of reading the full skill body.

When should I not create a new skill?

Skip creating skills for one-off solutions, well-documented standard practices, project-specific conventions that belong in CLAUDE.md, or mechanical constraints that can be enforced with validation scripts instead of documentation.

Why do agents ignore skill instructions under pressure?

Agents generate rationalizations like "this case is different" or "the spirit matters more than the letter" when facing time pressure or sunk costs. Counter this with explicit loophole closures, rationalization tables, red-line lists, and foundational principles stated upfront.