← Back to Skills Marketplace
636
Downloads
0
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install anti-panic-protocol
Description
Handle tool failures under pressure with bounded retries, clean user communication, and safe escalation. Use when commands/tools fail, when repeated retries...
README (SKILL.md)
Anti-Panic Protocol
Core rule
Fail without collateral damage.
Workflow (strict)
- Identify the failure in one sentence.
- Attempt fix #1 (direct, safe, minimal).
- Attempt fix #2 (bounded alternative).
- Stop retrying.
- Escalate in plain language with next action.
Never exceed 2 fix attempts unless user explicitly asks.
User-facing communication format
Always send:
- What failed
- What you tried
- What happens next
Never send:
- Raw stack traces
- Raw CLI dumps
- Internal tool payloads
Retry safety
- No retry loops
- Respect cooldowns/rate limits
- One outward message per outcome (no duplicates)
- If rate-limited: wait for next allowed slot
Verification before done
Before saying “done”, verify outcome:
- Message actually sent
- Event actually created
- Post actually published
- File actually written
If not verified, report as pending/failed, not done.
Escalation template
Gebruik dit patroon:
"Dit faalde: \x3Ckorte oorzaak>. Ik heb \x3Cpoging 1> en \x3Cpoging 2> geprobeerd. Volgende stap: \x3Cconcrete actie of vraag>."
Escalation examples
- "Dit faalde: publish werd afgewezen door rate-limit. Ik heb 1) direct retry en 2) delayed retry geprobeerd. Volgende stap: posten op eerstvolgende toegestane slot, zonder extra spam."
- "Dit faalde: agenda-event create gaf validation error op datumveld. Ik heb 1) ISO-format gefixt en 2) timezone expliciet gezet. Volgende stap: jij bevestigt datum/tijd, dan maak ik het event direct aan."
- "Dit faalde: loginflow timed out. Ik heb 1) token-login geprobeerd en 2) browserflow herstart. Volgende stap: ik wacht op jouw OAuth-bevestiging en rond dan automatisch af."
Hard stops
Escalate immediately (skip retries) if:
- Risk of destructive action
- Risk of duplicate external sends
- Authentication/security boundary issue
- User says stop/pause
Usage Guidance
This skill is instruction-only and appears low-risk: it provides rules for how the agent should retry and escalate after failures and asks for nothing extra. Before installing, consider: (1) if you rely on the agent to verify external actions, ensure the agent already has appropriate, minimal access to those services (the skill itself does not request credentials); (2) the SKILL.md prohibits sending raw traces but doesn't prescribe exact redaction — if you need strict redaction rules, add them to your agent policy; and (3) because the skill can be invoked autonomously by default, make sure you trust your agent's configured tool permissions so verification checks or escalation steps won't cause unwanted actions. If those points are acceptable, the skill is coherent with its purpose.
Capability Analysis
Type: OpenClaw Skill
Name: anti-panic-protocol
Version: 0.1.1
The 'anti-panic-protocol' skill bundle is designed for safe and controlled error handling. The `SKILL.md` instructions explicitly forbid sending raw stack traces or internal payloads, limit retry attempts, and mandate immediate escalation for security boundary issues or destructive actions. There is no evidence of prompt injection, data exfiltration, malicious execution, or any other harmful intent. The instructions promote secure and transparent agent behavior.
Capability Assessment
Purpose & Capability
The name/description (handle failures, bounded retries, safe escalation) matches the SKILL.md content. There are no unexpected required binaries, env vars, or installs that would be inconsistent with this purpose.
Instruction Scope
The runtime instructions are narrowly focused on detecting failures, making up to two safe fix attempts, verifying outcomes, and escalating in user-friendly language. They do not instruct the agent to read unrelated files, harvest credentials, or transmit data to third-party endpoints. The verification steps imply the agent must check that an action completed (e.g., message sent, file written) which is appropriate for this purpose.
Install Mechanism
No install spec and no code files — instruction-only. This minimizes risk because nothing is downloaded or written to disk.
Credentials
The skill declares no environment variables, credentials, or config paths. The actions it prescribes do not require additional secrets beyond whatever the agent already has for the tools it is using.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or attempt to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but is not combined with other concerning privileges.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install anti-panic-protocol - After installation, invoke the skill by name or use
/anti-panic-protocol - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.1
Add escalation examples for rate-limit, validation, and login timeout
v0.1.0
Initial release
Metadata
Frequently Asked Questions
What is Anti Panic Protocol?
Handle tool failures under pressure with bounded retries, clean user communication, and safe escalation. Use when commands/tools fail, when repeated retries... It is an AI Agent Skill for Claude Code / OpenClaw, with 636 downloads so far.
How do I install Anti Panic Protocol?
Run "/install anti-panic-protocol" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Anti Panic Protocol free?
Yes, Anti Panic Protocol is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Anti Panic Protocol support?
Anti Panic Protocol is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Anti Panic Protocol?
It is built and maintained by Noël (@noelistired); the current version is v0.1.1.
More Skills