writing-pulse-skills

Enforce test-driven RED→GREEN→REFACTOR cycles for Pulse SKILL.md files.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/quanpersie2001/pulse --skill writing-pulse-skills
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-pulse-skills
Source: https://github.com/quanpersie2001/pulse/tree/main/plugins/pulse/skills/writing-pulse-skills
Command: npx skills add https://github.com/quanpersie2001/pulse --skill writing-pulse-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about writing-pulse-skills

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

FAQPage Schema
How do I prevent agent rationalization when deploying SKILL.md files?

To prevent agent rationalization when deploying SKILL.md files, enforce a test-driven skill development workflow that requires agents to pass pressure tests with realistic A/B/C choices before any skill content is written.

What is the RED GREEN REFACTOR cycle for test-driven skill development?

The RED GREEN REFACTOR cycle for test-driven skill development requires running failing pressure test scenarios first to capture baseline rationalizations, then writing minimal skill content to pass tests, and finally refining the logic for repeatable compliance.

How do I pressure-test pulse plugin skills during creation?

To pressure-test pulse plugin skills during creation, run baseline scenarios without the skill to document rationalizations, then apply targeted fixes to the SKILL.md file and re-run the scenarios until the agent consistently complies.

What validation steps are needed to ensure SKILL.md files are not brittle?

Validation steps to ensure SKILL.md files are not brittle include running quick_validate.py, performing markdown link checks, and completing final verification to guarantee repeatable compliance across pressure testing templates.

Do I need a CREATION-LOG to document pressure testing for skill development?

A CREATION-LOG is required to document pressure testing for skill development, providing a ready-made template to record baseline failures, targeted fixes, and iterative verification during the RED to GREEN transition.

What's the best way to enforce test-driven workflows for pulse skill development?

The best way to enforce test-driven workflows for pulse skill development is to apply pressure-test templates across planning, validating, and deployment scenarios, ensuring agents are evaluated with realistic A/B/C choices before finalizing the SKILL.md file.