testing-skills-with-subagents

Apply RED-GREEN-REFACTOR testing to process documentation and capture rationalizations verbatim.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill testing-skills-with-subagents-h4v1d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-skills-with-subagents
Source: https://github.com/h4v1d/extension-collection-geminicli/tree/main/testing-skills-with-subagents
Command: npx skills add https://github.com/h4v1d/extension-collection-geminicli --skill testing-skills-with-subagents-h4v1d

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams test and validate the behavior of skills under pressure by guiding a RED-GREEN-REFACTOR cycle applied to process documentation, capturing failures, and iterating until compliance.

Core Features & Use Cases

  • Baseline testing: Run scenarios without the skill to reveal failures and rationalizations.
  • Verbatim documentation: Capture exact rationalizations and patterns to close holes.
  • Refactoring loop: Add explicit counters, red flags, and rationalization tables to ensure ongoing compliance across iterations.
  • Use Case: Before deploying a new skill, run a complete RED-GREEN-REFACTOR campaign on representative documentation tasks to guarantee robustness.

Quick Start

Start with a RED phase by running a baseline scenario without the skill, then implement the minimal skill and re-run the same scenario to confirm compliance, repeating the REFACTOR cycle until no new rationalizations emerge.

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 validate skill behavior under pressure before deployment?

You validate skill behavior under pressure by applying a RED-GREEN-REFACTOR testing cycle to process documentation, capturing rationalizations verbatim, and iterating until no new failures emerge.

What is TDD for process documentation and skill validation?

TDD for process documentation uses a RED-GREEN-REFACTOR loop to baseline test scenarios without a skill, capture exact rationalizations, and refactor with explicit counters and red flags to ensure compliance.

How do I start a RED-GREEN-REFACTOR cycle for subagent scenarios?

Start a RED-GREEN-REFACTOR cycle for subagent scenarios by running a baseline task without the skill, implementing the minimal skill, re-running the same scenario, and repeating until robustness is achieved.

Why do I need to capture rationalizations verbatim during skill testing?

Capturing rationalizations verbatim during skill testing exposes exact failure patterns and excuses, allowing you to close documentation holes and add explicit counters for iterative compliance improvement.

Does testing skills with subagents require any external dependencies?

Testing skills with subagents does not require external dependencies, relying instead on a disciplined workflow of baseline testing, rationalization tables, and red-flag updates to ensure bulletproof behavior.