# Terminal-Bench Fix Loop

Runs one Terminal-Bench task through bounded smoke, diagnosis and fix cycles.

- Repository: https://github.com/paperclipai/paperclip (109885 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add paperclipai/paperclip --skill terminal-bench-loop -g -a claude-code -y`
Codex: `npx skills add paperclipai/paperclip --skill terminal-bench-loop -g -a codex -y`
Cursor: `npx skills add paperclipai/paperclip --skill terminal-bench-loop -g -a cursor -y`
Gemini CLI: `npx skills add paperclipai/paperclip --skill terminal-bench-loop -g -a gemini-cli -y`

## Description

Run one Terminal-Bench task through a bounded Paperclip smoke/diagnosis/fix loop. Use when asked to drive Terminal-Bench until it passes, rerun a Terminal-Bench loop, or iterate with board-gated fixes and diagnosis.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Terminal-Bench Loop

A repeatable operating skill for driving one Terminal-Bench problem to a passing smoke through Paperclip, with explicit issue topology, bounded runs, board-gated product fixes, and worktree continuity.

This skill is **operational + diagnostic**, not engineering. It coordinates issues, artifacts, and approvals around a Terminal-Bench loop. It does not authorize code changes, every accepted product fix lands as a separate implementation child issue after a board confirmation.

Canonical execution model: read `doc/execution-semantics.md` before starting a loop or moving any loop issue. Every loop issue must rest in a state the doc allows: terminal (`done`/`cancelled`), explicitly live (active run / queued wake), explicitly waiting (`in_review` with participant/interaction/approval), or explicit recovery/blocker (`blocked` with `blockedByIssueIds` and a named owner).

## When to use

Trigger on an assignment whose title or body matches any of:

- "run Terminal-Bench in a loop", "loop \<task-name\> through Paperclip"
- "drive Terminal-Bench fix-git", "iterate on Terminal-Bench until it passes"
- "Terminal-Bench smoke loop", "bench loop", "smoke loop on \<task-name\>"
- An attached link to a Terminal-Bench loop parent issue, plus a request to do another iteration

Also use when the user hands you an existing top-level loop issue and asks for the next iteration, diagnosis, or rerun.

## When NOT to use

The rest: https://github.com/paperclipai/paperclip/blob/HEAD/.agents/skills/terminal-bench-loop/SKILL.md