writing-pulse-skills

What problem does it solve?

Prevents agents from rationalizing, skipping validation, or deploying brittle SKILL.md files by enforcing a test-driven workflow for creating and editing Pulse skills.

Core Features & Use Cases

• TDD-for-skills methodology: RED → GREEN → REFACTOR cycle that requires failing pressure tests before any skill content is written.
• Pressure testing templates & documentation: Ready-made scenarios and a CREATION-LOG template to record baseline failures, targeted fixes, and iterative verification.
• Validation checklist: Steps to run quick_validate.py, markdown link checks, and final verification to ensure repeatable compliance.
• Use case: A developer preparing to add or modify a Pulse skill runs baseline scenarios, documents rationalizations, writes the minimal SKILL.md to address those failures, and re-tests until the agent consistently complies.

Quick Start

Run three RED-phase pressure scenarios without the skill to capture baseline rationalizations, then write the minimal SKILL.md targeting those rationalizations and re-run the scenarios until they pass.