tb2-playbook

Define TB2 evolution constraints for sandbox topology, tool constraints, and trajectory signaling.

415|49|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Darwin-Agent/HarnessX --skill tb2-playbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tb2-playbook
Source: https://github.com/Darwin-Agent/HarnessX/tree/main/recipe/tb2_evolver/skills/tb2-playbook
Command: npx skills add https://github.com/Darwin-Agent/HarnessX --skill tb2-playbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structural facts about TB2 that are not visible in trajectories and are required to author valid evolution candidates.

Core Features & Use Cases

  • Sandbox topology: clearly separates agent and verifier phases with no live file access, ensuring deterministic evaluation.
  • Tool constraint: enforces a single Bash tool and documents how to evolve the processor pipeline and system prompt.
  • Evolvable surface: specifies what in config.yaml, system prompts, and processor pipelines can be safely adjusted.

Quick Start

Consult this TB2 Playbook before drafting any evolution candidate that touches the system prompt, tool registry, or processor pipeline.

Frequently Asked Questions about tb2-playbook

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

FAQPage Schema
What is TB2 evolution and how does sandbox topology work?

TB2 evolution is the process of safely adjusting agent configurations within a sandbox topology that strictly separates agent and verifier phases with no live file access, ensuring deterministic evaluation.

How do I evolve the system prompt and processor pipeline in TB2?

To evolve the system prompt and processor pipeline in TB2, consult the playbook to understand the tool constraints, then safely adjust the evolvable surfaces specified in config.yaml and processor pipelines.

Can I use multiple tools in TB2 experimentation scenarios?

No, TB2 enforces a single Bash tool constraint. You must work within this limitation when evolving the processor pipeline and system prompts for safe experimentation.

What can I safely modify in config.yaml during TB2 evolution?

You can safely modify the evolvable surface specified in config.yaml, which includes adjustments to system prompts, processor pipelines, and trajectory signaling configurations.

Why does my TB2 evolution candidate fail validation?

TB2 evolution candidates fail validation when they violate structural facts about sandbox topology or tool constraints, such as attempting live file access or introducing tools beyond the single Bash tool.