Cmd Done Check
Ask the agent whether it finished everything or has more to do — a lightweight completeness gate for the end of any task
Install
$ agentstack add skill-olshansk-agent-skills-cmd-done-check ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-olshansk-agent-skills-cmd-done-check) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Done Check
A quick self-interrogation to catch loose ends before declaring a task complete.
Instructions
Answer each question honestly. If anything is incomplete, say so and ask the user whether to continue.
1. Did you do everything the user asked?
- Re-read the original request. Is every explicit ask addressed?
- Did you skip or defer anything without telling the user?
- Did you say "I'll also..." or "next, we should..." and then not do it?
2. Did you leave any loose ends?
- Are there TODOs, FIXMEs, or placeholder values you introduced that should be resolved now?
- Are there commented-out blocks, debug prints, or temporary stubs in the output?
- Are there follow-up steps you mentioned but didn't take?
3. Did you handle side effects?
- Are there related files, configs, or tests that should be updated but weren't?
- Did any rename, move, or deletion leave dangling references?
- If you added a skill/command/export — is it wired up and discoverable?
4. Are docs and metadata consistent?
- If you added or changed something user-facing, is the README or AGENTS.md updated?
- Are variable names, comments, and doc strings consistent with what shipped?
Output
If everything is done: say "Done — nothing left." in one line.
If something is incomplete: list each item as a bullet with what's missing and why, then ask:
> Want me to continue and handle these now, or are you good?
Do not pad the response. One sentence per finding.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Olshansk
- Source: Olshansk/agent-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.