Menú
Use when the user naturally asks to start, continue, monitor, or summarize a GenomeHarness campaign or sequential benchmark suite.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when a GenomeHarness v15 campaign has pending PROPOSE requests and proposal JSON must be written from request packets.
Use when a GenomeHarness campaign has a REPAIR request and repair JSON must be written without changing scientific protocol.
Use when generating or reviewing GenomeHarness v15 campaign reports from state.sqlite and trial artifacts.
Use when supervising an official GenomeHarness v15 campaign or sequential suite through the interactive CLI loop.
| name | genomeft-intake |
| description | Use when the user naturally asks to start, continue, monitor, or summarize a GenomeHarness campaign or sequential benchmark suite. |
Use plans/genomeharness_v15_plan.md as the active authority.
For a new campaign or suite:
nt as a benchmark. Use nt-suite for the NT benchmark family or a full task id such as nt/H2AFZ.genharness plan --dry-run --project <repo> --model <model> --benchmark <nt-suite|gb-suite|task_id> --scope <suite|campaign> --json
full_l3_async, full-data search, 4 slots, UCT settings, deadline+drain, GPU policy, confirmation/final policy, and test isolation.suite-init, preflight, or start.For explicit continue/status:
genharness status --campaign campaigns/X --brief
genharness advance --campaign campaigns/X --wait
If the runner is inconsistent:
genharness recover --campaign campaigns/X
The user should not need to copy shell commands. Execute the genharness tool calls yourself and report concise progress.
genharness status --brief for progress checks.