testing-skills-with-subagents

Apply test-driven documentation to validate agent behavior under pressure scenarios.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Whaleylaw/llm-lawyer --skill testing-skills-with-subagents-whaleylaw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-skills-with-subagents
Source: https://github.com/Whaleylaw/llm-lawyer/tree/main/.claude/skills.old/testing-skills-with-subagents
Command: npx skills add https://github.com/Whaleylaw/llm-lawyer --skill testing-skills-with-subagents-whaleylaw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents skills from being bypassed or rationalized by agents by applying a test-driven process to skill documentation so authors see how agents fail and close those loopholes.

Core Features & Use Cases

  • RED-GREEN-REFACTOR cycle: Run realistic baseline (RED) scenarios, implement targeted skill changes (GREEN), and iteratively close loopholes (REFACTOR).
  • Pressure scenarios & rationalization capture: Create multi-pressure tests (time, sunk cost, authority) and record agent rationalizations verbatim to drive precise counters.
  • Verification & meta-testing: Pressure-test updated skills, require agents to cite sections, and perform meta-questions to identify remaining ambiguities.
  • Use case: Use when authoring or hardening compliance- or discipline-enforcing skills that agents might ignore under operational pressure.

Quick Start

Run three realistic pressure scenarios without the skill, record the agent failures verbatim, write minimal counters addressing those failures, and re-run scenarios until the agent consistently follows the skill.

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 prevent agents from rationalizing or bypassing instructions under pressure?▼

To prevent agents from bypassing instructions, apply test-driven documentation by running realistic pressure scenarios to observe failures, then write targeted counters to close those loopholes. This process hardens compliance-sensitive skills against rationalization.

What is the RED-GREEN-REFACTOR cycle for testing AI agent skills?▼

The RED-GREEN-REFACTOR cycle for agent skills involves running baseline scenarios to record failures (RED), implementing minimal counters to address those failures (GREEN), and iteratively updating rules to close remaining loopholes (REFACTOR).

How do I test agent skills against time, authority, or exhaustion pressures?▼

You test agent skills against operational pressures by creating multi-pressure scenarios involving time, sunk cost, or authority, capturing the agent's rationalizations verbatim, and using those records to drive precise documentation counters.

When should I use test-driven documentation for skill creation?▼

Use test-driven documentation when authoring or hardening compliance-sensitive or discipline-enforcing skills where agents may adapt, rationalize, or bypass instructions under operational pressure. It ensures instructions hold up under realistic stress.

How do I verify that an agent consistently follows updated skill instructions?▼

You verify agent compliance by pressure-testing updated skills, requiring agents to cite specific documentation sections during execution, and performing meta-questions to identify and resolve any remaining ambiguities in the instructions.

What are the limitations of using pressure scenarios for skill testing?▼

Pressure-based skill testing relies on running realistic scenarios to capture rationalizations, but it may not anticipate every edge case. Meta-testing and iterative refactoring are required to continuously identify and close remaining ambiguities.