Lean body that assumes Claude's competence — no concept explanations, every line (modes, flags, pitfalls) earns its place, and detail is offloaded to references rather than repeated inline.

Provides fully executable boltz-api commands across all four modes with concrete flags, placeholders, and notes on output shape (streamed JSONL, head cap) — copy-paste ready.

Four numbered modes with an "Always Do This" checklist plus explicit error-recovery guidance (retrieve before download for idempotency_key, VALIDATION_ERROR semantics, never re-run start) give a clear sequenced workflow with feedback loops.

Body stays overview-level and points to two real one-level-deep references ([references/resume.md], [references/api.md]) that exist on disk, each clearly signaled for when it is needed.

Lists multiple concrete actions — "listing jobs, checking progress, resuming downloads, recovering results, or downloading an existing job ID" — rather than vague language.

Explicitly answers both what ("Boltz job status and result recovery") and when ("Use when listing jobs, checking progress...") plus an explicit exclusion ("Not for starting new jobs").

Uses natural phrases a user would say ("listing jobs", "checking progress", "resuming downloads", "recovering results") with good coverage and no jargon-only terms.

Clear niche (status/recovery of existing jobs) with an explicit negative boundary ("Not for starting new jobs") making conflicts with job-creation skills unlikely.