Agent skill · operations · paperclipai
terminal-bench-loop
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.
Why this skill is useful
Provides a structured operational framework for managing Terminal-Bench iterations and diagnostics that the AI wouldn't reliably generate on its own.
What it needs
About 12k tokens when loaded. Last updated 2026-08-07. 75,771 stars on the source repository.
What this skill does
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 (inreview 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 assignment is to build or change paperclip-bench itself (Harbor adapter, wrapper, telemetry). Use normal engineering flow on that repo. The assignment is to submit a benchmark result for ranking. This skill produces smoke/non-comparable runs by design — escalate full-suite or comparable runs to BenchmarkQualityManager. The assignment is a normal Paperclip product bug not surfaced by a Terminal-Bench loop. Use normal investigation. You have not been granted permission to install or assign company skills, and the asker actually wants library mutation. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills paperclipai/terminal-bench-loop