writing-skills

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

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Syedyasir001/RVULibPass --skill writing-skills-syedyasir001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Syedyasir001/RVULibPass/tree/main/.agent/skills/library/writing-skills
Command: npx skills add https://github.com/Syedyasir001/RVULibPass --skill writing-skills-syedyasir001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphviz.

What problem does it solve? Writing documentation-style skills for AI agents often produces untested instructions that agents ignore or rationalize away under pressure. This Skill applies test-driven development to skill authoring so every skill is verified against real agent behavior before deployment. ## Core Features & Use Cases - TDD-based skill authoring: Run baseline pressure scenarios with subagents (RED), write the skill addressing observed failures (GREEN), then close rationalization loopholes (REFACTOR). - Discovery optimization guidance: Rules for writing name and description frontmatter, keyword coverage, token efficiency, and Claude Search Optimization so agents actually find the skill. - Testing methodology: Detailed guidance for pressure scenarios, rationalization tables, red-flag lists, and meta-testing, plus persuasion principles research for bulletproofing discipline-enforcing skills. - Use Case: You want to create a new skill that enforces a code-review rule. Use this Skill to first run a subagent scenario without the rule, capture the agent's excuses verbatim, write the skill countering those exact excuses, and re-test until the agent complies under time, sunk-cost, and authority pressure. ## Quick Start Ask the agent to help you create a new skill using test-driven development, starting with a baseline pressure scenario before writing any documentation.

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?▼

A SKILL.md needs YAML frontmatter with a name and description, followed by a markdown body with an overview, when-to-use triggers, core patterns, and examples. Keep the description focused on triggering conditions starting with "Use when" rather than summarizing the workflow.

How to test an agent skill before deploying it?▼

Run pressure scenarios with subagents without the skill to capture baseline failures, then write the skill addressing those specific rationalizations and re-test. Combine three or more pressures like time, sunk cost, and authority, and iterate until the agent complies under maximum pressure.

What makes a good skill description for agent discovery?▼

A good description starts with "Use when", describes only triggering conditions and symptoms in third person, and never summarizes the skill's workflow. Descriptions that summarize process steps cause agents to follow the description instead of reading the full skill body.

When should I not create a new skill?▼

Skip creating skills for one-off solutions, standard practices already well-documented, project-specific conventions that belong in project config files, and mechanical constraints that can be enforced with automated validation instead of documentation.

Why do agents ignore or bypass skill instructions?▼

Agents rationalize around rules under pressure using excuses like "spirit versus letter" or "being pragmatic". Bulletproof skills close each loophole with explicit negations, rationalization tables, red-flag lists, and foundational principles discovered through iterative pressure testing.