writing-skills

Create and test agent skills using test-driven development methodology.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/SESELOVSKYDarian/Vase --skill writing-skills-seselovskydarian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/SESELOVSKYDarian/Vase/tree/main/.agents/skills/writing-skills
Command: npx skills add https://github.com/SESELOVSKYDarian/Vase --skill writing-skills-seselovskydarian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Writing effective agent skills without testing leads to documentation that agents ignore, misinterpret, or rationalize away under pressure, resulting in unreliable skill behavior in production. ## Core Features & Use Cases - TDD-Based Skill Authoring: Applies the RED-GREEN-REFACTOR cycle to skill creation, requiring baseline failure tests before writing any skill content. - Pressure Scenario Testing: Provides a methodology for testing skills with subagents under combined pressures like time constraints, sunk cost, and authority. - Rationalization Bulletproofing: Includes patterns for closing loopholes, building rationalization tables, and creating red flag lists that prevent agents from bypassing rules. - Use Case: When creating a new discipline-enforcing skill like TDD or verification-before-completion, use this skill to run baseline scenarios, document agent failures verbatim, write minimal counter-instructions, and iterate until agents comply under maximum pressure. ## Quick Start Ask the agent to create a new skill following the writing-skills methodology, starting with baseline pressure scenario testing before writing any content.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I create a new agent skill with SKILL.md?

Create a directory containing a SKILL.md file with YAML frontmatter defining name and description fields, followed by markdown body instructions. The description should start with "Use when..." and describe triggering conditions only, never summarizing the workflow.

How to test agent skills before deployment?

Run pressure scenarios with subagents without the skill first to document baseline failures verbatim, then write the skill addressing those failures, and re-test to verify compliance. Combine three or more pressures like time constraints, sunk cost, and authority for realistic testing.

What makes a good skill description for discovery?

Write descriptions in third person starting with "Use when..." that describe only triggering conditions and symptoms, never the workflow. Include concrete keywords like error messages, symptoms, and tool names that agents would search for.

Why do agents ignore or bypass skill instructions?

Agents rationalize away rules under pressure using excuses like "spirit versus letter" or "being pragmatic." Counter this with explicit negations of specific loopholes, rationalization tables, red flag lists, and foundational principles stated early in the skill.

When should I not create a new skill?

Skip skill creation for one-off solutions, project-specific conventions that belong in CLAUDE.md, well-documented standard practices, and mechanical constraints that can be enforced with automated validation instead of documentation.