Individual skill

execution-hygiene

Runs computations so they finish, reproduce and fit the machine that will re-execute them, detaching long jobs through compute_job instead of blocking or sleeping shells, checkpointing so reruns resume, fixing seeds and capping BLAS and OpenMP threads, streaming large tables with explicit dtypes, writing outputs atomically, logging every command with its exit code and rerunning the final pipeline from scratch under the target limits before finishing. Use for any analysis or pipeline that runs longer than a minute, reads files larger than memory, or will be re-executed on a machine with tighter CPU, memory, wall-clock or network limits than this one; a one-off shell command whose output is read immediately does not need it.

backend/cli/skills/core/execution-hygiene/SKILL.md

Read pinned source

Source commit a08e0ad0ad3d6448123039ee4659163eb2e35d99

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
4,351
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Execution hygiene

A number that exists only in a terminal scrollback, or that came from a run on a machine
with more cores and memory than the one that will re-execute the pipeline, is not a
result yet. The habits below cost minutes and remove the two most common ways an analysis
fails after it "worked": it cannot be rerun, or it runs differently.

## Rules

1. **Detach anything that outlives a shell prompt.** A step that may exceed a few minutes
   goes through `compute_job start` (name, purpose, command, cwd, declared artifacts and
   checkpoint path). A job that settles within the dispatch's grace comes back in that step
   with its outcome, output tail and deliveries; a longer one wakes you when it ends, so go
   on with other work rather than `wait` on it, and read `compute_job logs` only when the