How do I install the Anti Panic Protocol skill?

Run npx skillmds@latest add johnalbertini14-glitch/anti-panic-protocol in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Anti Panic Protocol safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Anti Panic Protocol?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Anti Panic Protocol free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Anti Panic Protocol?

johnalbertini14-glitch (@johnalbertini14-glitch) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Anti Panic Protocol by johnalbertini14-glitch

Name: Anti Panic Protocol
Rating: 4.2 (5 reviews)
Author: johnalbertini14-glitch

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 risk spam or rate limits, or when you need a strict error-response workflow (translate raw errors, attempt safe fixes, then escalate clearly).

File contents

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: . Ik heb <poging 1> en <poging 2> geprobeerd. Volgende stap: ."

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

---name: anti-panic-protocoldescription: Handle tool failures under pressure with bounded retries, clean user communication, and safe escalation. Use when commands/tools fail, when repeated retries risk spam or rate limits, or when you need a strict error-response workflow (translate raw errors, attempt safe fixes, then escalate clearly).--- # Anti-Panic Protocol ## Core rule Fail without collateral damage. ## Workflow (strict) 1. Identify the failure in one sentence. 2. Attempt fix #1 (direct, safe, minimal). 3. Attempt fix #2 (bounded alternative). 4. Stop retrying. 5. 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: <korte oorzaak>. Ik heb <poging 1> en <poging 2> geprobeerd. Volgende stap: <concrete 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

Frequently asked questions