writing-skills

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill writing-skills-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/writing-skills
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill writing-skills-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphviz.

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 the RED-GREEN-REFACTOR cycle of test-driven development to skill authoring, so every rule is verified against real baseline agent failures before deployment. ## Core Features & Use Cases - TDD-based skill authoring: Run baseline pressure scenarios with subagents, document verbatim rationalizations, write the minimal skill that addresses them, then close loopholes iteratively. - Discovery optimization (SDO): Guidance on writing trigger-focused descriptions, keyword coverage, naming conventions, and token-efficient structure so agents actually find and load the skill. - Bulletproofing toolkit: Rationalization tables, red-flag lists, persuasion principles, and form-matching rules to make discipline-enforcing skills resist workarounds. - Use Case: You want to create a new skill enforcing a code-review rule. You first run pressure scenarios (time pressure, sunk cost, authority) without the skill, record how agents violate the rule, then write and iteratively harden the skill until agents comply under maximum pressure. ## Quick Start Ask the agent to create a new skill following the writing-skills TDD process, starting with baseline pressure scenarios before writing any SKILL.md content.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I test a skill before deploying it?

Run pressure scenarios with subagents without the skill first to capture baseline failures verbatim, then write the skill addressing those failures and re-test until agents comply. Combine three or more pressures like time, sunk cost, and authority for realistic tests.

How to write a good skill description for discovery?

Start with "Use when..." and describe only triggering conditions and symptoms, never the skill's workflow. Descriptions that summarize the process cause agents to follow the description instead of reading the full skill body.

What makes a discipline-enforcing skill resist rationalization?

Close every loophole explicitly with prohibition lists, build a rationalization table from observed excuses, add a red-flags self-check list, and state that violating the letter violates the spirit. Re-test after each addition until no new rationalizations appear.

When should I not create a new skill?

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

Can I render flowcharts from a SKILL.md file?

Yes, the included render-graphs.js script extracts dot blocks from SKILL.md and renders them to SVG using graphviz. Run it with the skill directory path, optionally with --combine to merge all diagrams into one SVG.