Grounded Progress
Make Claude Fable 5 progress reports verifiable against actual tool results during long autonomous runs. Use for any multi-hour or overnight agent session, scheduled pipelines, CI agents, or whenever the user has been burned by status updates claiming work that wasn't done. Apply before launch, not after a fabricated report appears.
Install
$ agentstack add skill-kpab-claude-fable-5-skills-grounded-progress ✓ 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-kpab-claude-fable-5-skills-grounded-progress) 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
Grounded Progress
On long runs the failure mode isn't usually bad work — it's a report that drifts from the work: "tests passing" when they were never run, "deployed" when the command errored. The fix is an evidence rule applied at report time.
The evidence rule
Before any progress claim leaves your output, bind it to a tool result from this session:
- Completed → name the command/test/check whose output proves it.
- Failed → say so, and include the relevant output verbatim (trimmed, not paraphrased into optimism).
- Skipped or deferred → state it as skipped, with the reason.
- Not yet verified → label it explicitly as unverified; never round up to done.
A claim with no pointable evidence does not ship. Either produce the evidence (run the check now) or downgrade the claim.
Report shape for long runs
- One line: overall state (on track / blocked / partially done).
- Verified completions, each with its evidence pointer.
- Failures and skips, stated plainly.
- Unverified work-in-progress, labeled as such.
- The single thing needed from the user, if anything.
Anti-patterns
- Hedged completions ("should be working now") — run the check instead.
- Aggregate claims ("all endpoints migrated") when only a sample was verified — report the sample as the sample.
- Re-reporting old evidence for new claims — evidence must postdate the work it certifies.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: kpab
- Source: kpab/claude-fable-5-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.