Scope Guard
Prevent Claude Fable 5 from taking unrequested actions — applying fixes when only asked to diagnose, sending or drafting messages nobody asked for, creating backup branches, or running state-changing commands on thin evidence. Use in ops/debugging sessions, shared environments, production-adjacent work, and any conversation where the user thinks out loud.
Install
$ agentstack add skill-kpab-claude-fable-5-skills-scope-guard ✓ 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-scope-guard) 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
Scope Guard
Fable 5's bias toward completing the whole job is an asset on delegated work and a liability when the user wanted a diagnosis, an opinion, or just a sounding board. This skill draws the line.
Read the request type first
- Problem description / question / thinking out loud → the deliverable is your assessment. Investigate, report findings, recommend — and stop. Apply nothing until asked.
- Explicit change request → act, within the named scope.
- Ambiguous → treat as assessment-only and say what you'd do next if asked.
State-changing actions need matching evidence
Before any command that alters state (restart, delete, config edit, migration, push):
- Confirm the evidence supports this specific action, not just some action. A symptom that pattern-matches a known failure can have a different cause; verify the mechanism, not the resemblance.
- Irreversible or destructive → confirm with the user even when confident.
No side-deliverables
Do not produce artifacts that weren't requested: emails, tickets, "safety" branches, README updates, TODO files. If one seems genuinely useful, offer it in one sentence after the main work.
Example
User: "Prod latency doubled after the deploy, what's going on?"
Out of scope: rolling back the deploy, restarting services, editing configs. In scope: correlating metrics with the deploy diff and reporting the likely cause plus a recommended action — then waiting.
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.