testing-skills-with-subagents

Test skills with subagents to verify resistance to rationalization under pressure.

3|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/seanGSISG/crispy-claude --skill testing-skills-with-subagents-seangsisg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-skills-with-subagents
Source: https://github.com/seanGSISG/crispy-claude/tree/main/.claude/skills/testing-skills-with-subagents
Command: npx skills add https://github.com/seanGSISG/crispy-claude --skill testing-skills-with-subagents-seangsisg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skills, especially those enforcing discipline, can be bypassed by AI agents under pressure or through rationalization, leading to inconsistent behavior. This skill applies TDD principles to process documentation, ensuring skills are robust and effective.

Core Features & Use Cases

  • TDD for Documentation: Guides through a RED-GREEN-REFACTOR cycle: running baseline tests without the skill, writing the skill to address failures, and iterating to close loopholes.
  • Pressure Scenario Testing: Creates realistic scenarios with combined pressures (time, sunk cost, authority) to test agent compliance under stress.
  • Rationalization Countermeasures: Identifies and explicitly negates common agent rationalizations, building a "bulletproof" skill.

Quick Start

Use the testing-skills-with-subagents skill to test my new 'code-review-protocol' skill for agent compliance under time pressure.

Frequently Asked Questions about testing-skills-with-subagents

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

FAQPage Schema
How do I test if my AI skill resists rationalization under pressure?

Testing skills with subagents applies TDD principles to process documentation by running baseline failure scenarios, implementing targeted fixes, then pressure-testing with combined stressors like time constraints and sunk-cost pressures to verify the skill closes loopholes and enforces compliance.

What is the RED-GREEN-REFACTOR cycle for documenting AI agent behavior?

RED-GREEN-REFACTOR is a test-driven approach where you first run baseline tests without the skill to establish failure modes, write the skill to address those failures, then iteratively refine it by capturing agent rationalizations verbatim and implementing countermeasures.

Can I verify agent compliance before deploying a new skill?

Yes. This skill enforces verification during skill creation or editing by running baseline and pressure scenario testing with subagents, capturing how agents rationalize non-compliance, and iterating fixes until the skill withstands realistic combined pressures.

How do I identify common agent rationalizations my skill needs to counter?

Pressure scenario testing creates realistic conditions combining time, sunk-cost, and authority pressures to expose how agents rationalize bypassing your skill; you capture these rationalizations verbatim and implement explicit countermeasures into the skill documentation.

What's the difference between baseline testing and pressure scenario testing for skills?

Baseline testing runs your skill against standard failure modes to verify basic functionality. Pressure scenario testing applies combined stressors to expose loopholes agents exploit under real-world conditions, ensuring the skill remains bulletproof even when agents face competing priorities.