Scope guard

Skill kpab/claude-fable-5-skills/skills/scope-guard

10 Fable 5-native agent skills — Works with Claude Code, Cursor, Copilot

Install

npx -y skills add kpab/claude-fable-5-skills --skill scope-guard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

14 stars14 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.8 KB, as published. Nobody here has run it

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.