Menu
Test skills via TDD in fresh subagents. Use when validating behavior or preventing bias.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Detects AI-generated writing patterns in prose. Use when reviewing docs for slop, vague language, or identity leaks before publishing.
Audits Rust code for unsafe blocks, ownership issues, and Cargo dependency risks. Use when reviewing Rust code or before merging Rust changes.
Recommends context compression strategies for bloated or quota-heavy sessions. Use when context feels sluggish or quota burns faster than expected.
Guide minimal code via a decision ladder with full safety, edge, and negative-case coverage. Use when adding code, choosing a dependency, or auditing a diff.
Optimizes context window via MECW principles and memory tiering. Use when context exceeds 30% or before long multi-step tasks.
Generates or remediates documentation with human-quality writing. Use when creating new docs, rewriting AI-generated content, or applying style profiles.
| name | subagent-testing |
| description | Test skills via TDD in fresh subagents. Use when validating behavior or preventing bias. |
| alwaysApply | false |
| category | testing |
| tags | ["testing","validation","TDD","subagents","fresh-instances"] |
| token_budget | 30 |
| progressive_loading | true |
| modules | ["modules/testing-patterns.md"] |
| model_hint | standard |
Test skills with fresh subagent instances to prevent priming bias and validate effectiveness.
Fresh instances prevent priming: Each test uses a new Claude conversation to verify the skill's impact is measured, not conversation history effects.
Running tests in the same conversation creates bias:
Three-phase TDD-style approach:
Test without skill to establish baseline behavior.
Test with skill loaded to measure improvements.
Test skill's anti-rationalization guardrails.
# 1. Create baseline tests (without skill)
# Use 5 diverse scenarios
# Document full responses
# 2. Create with-skill tests (fresh instances)
# Load skill explicitly
# Use identical prompts
# Compare to baseline
# 3. Create rationalization tests
# Test anti-rationalization patterns
# Verify guardrails work
For complete testing patterns, examples, and templates: