competitive-evolution

Run PROD or DEBUG variants against a 2,200-case test bank with isolated state.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/whichguy/c-thru --skill competitive-evolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competitive-evolution
Source: https://github.com/whichguy/c-thru/tree/main/skills/competitive-evolution
Command: npx skills add https://github.com/whichguy/c-thru --skill competitive-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a controlled, repeatable environment to stress-test agentic logic while enforcing statelessness and deterministic evaluation across a large test bank.

Core Features & Use Cases

  • Stateless, isolated runs for each test case
  • Large test bank (2,200 cases) with 100-point scoring
  • Fresh context for each run and hermetic archival of results
  • PROD and DEBUG variants support
  • Primary tool: c-thru-tournament

Quick Start

Invoke the batch benchmark to run PROD or DEBUG variants against the test bank.

Frequently Asked Questions about competitive-evolution

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

FAQPage Schema
How do I run stateless stress-testing for agentic workflows?

Stateless stress-testing for agentic workflows is executed by running prompt variants through a 2,200-case test bank in fully isolated contexts. The environment enforces statelessness, applies fresh supervisor states, and archives results hermetically.

What is isolated benchmark scoring for prompt variants?

Isolated benchmark scoring evaluates PROD and DEBUG prompt variants by applying a fresh supervisor state for each run across a 2,200-case test bank. It enforces deterministic evaluation using a standardized 100-point scoring system.

How do I benchmark PROD and DEBUG variants without state interference?

To benchmark PROD and DEBUG variants without state interference, you run them through a test bank using a fully isolated context. The workflow enforces statelessness by applying a fresh supervisor state for each individual run.

Does agentic statelessness testing support large-scale test banks?

Agentic statelessness testing supports large-scale test banks by processing 2,200 cases in a controlled, repeatable environment. Each case runs in a fresh context with hermetic archival of results to ensure deterministic evaluation.

Why does my agentic logic fail under repeatable stress-testing?

Agentic logic fails under repeatable stress-testing when state leakage occurs between cases. This workflow prevents failures by enforcing statelessness and applying a fresh supervisor state for each run across the test bank.