What to say while long work is still running, and what a legal mid-task stop looks like. Use during any run over a few minutes — migrations, sweeps, babysit loops, automations, deploys — and at the moment you are tempted to stop and ask, report a blocker, or answer "how's it going?".
69
87%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Measured on 2026-08-12, "had to chase status on a long-running run" was the single most frequent correction in this repo — 86 in two weeks, more than false-done and collisions combined. Every one of them is the user asking a question the agent could have answered before being asked.
Done, with the artifact that proves it — a command's output, a sha, a URL,
a screenshot file. verifying-changes says which artifact per area. A sentence
describing a check you would run is not an artifact.
Blocked, on one line:
BLOCKED: <what is stopping you> — unblock: <one thing the user can do in under a minute>Anything else is a stall. "I'm looking into it", "let me know how you want to proceed", and a status paragraph with no ask are all stalls.
In the measured cases, every single "blocked" was a step the agent could have taken:
.env files.A missing credential, a genuinely destructive action, and a decision only the user can make are blockers. Nothing else on this list is.
Post a delta, not a heartbeat. "Tick 14, still running" is noise; the user reads it as nothing happening — which, in the measured cases, it usually was.
Never message another agent's thread to report your own progress, and never tell peer threads to pause. Their work is not yours to stop.
a941a2e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.