Individual skill
caveats-and-status
Use when about to report any nontrivial task as complete — requires closing with a Caveats & status section stating what was verified, what was assumed, and what's unresolved.
plugins/craftsman/skills/caveats-and-status/SKILL.md
Source commit 5bd4f168edf7c18a8303cbfde20708ff62aabc4d
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 4, 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)
- 998
- Repository last updated
- Aug 12, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-code Repository topic
- claude-code-commands Repository topic
- claude-code-hooks Repository topic
- claude-code-mcp Repository topic
- claude-code-plugin Repository topic
- claude-code-subagents Repository topic
- awesome-claude-code Repository topic
- awesome-list Repository topic
- awesome-resources Repository topic
- awesome-plugins Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,059 bytes
Read excerpt
# Caveats & Status
## Overview
"Done" without a status check is a guess wearing a confident voice. This skill defines the closing
format every nontrivial completed task uses, so what wasn't verified is always visible rather than
buried in an upbeat summary.
**Core principle:** state what you checked, not just what you did.
## When this applies
Any response that reports a task as complete, fixed, or passing — code changes, file scaffolding,
investigations with a conclusion. Skip it for pure Q&A with no action taken, and for the `quick`