Escalation Design
When and how AI should escalate to humans, refuse, or ask for clarification.
Install
/plugin marketplace add Owl-Listener/ai-design-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Owl-Listener/ai-design-skills --skill escalation-designgit clone --depth 1 https://github.com/Owl-Listener/ai-design-skills.git /tmp/ai-design-skills
mkdir -p ~/.claude/skills
cp -r /tmp/ai-design-skills/claude-plugin/ai-alignment-reasoning/skills/escalation-design ~/.claude/skills/escalation-designPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Escalation Design Escalation is what happens when the AI reaches the boundary of what it should handle alone. Designing escalation well means the user gets help instead of a dead end — and the AI knows its limits. ## Escalation Triggers The AI should escalate when: - **Confidence is low**: The AI isn't sure its output is correct or helpful - **Stakes are high**: The decision has significant consequences (financial, medical, legal, safety) - **Emotional distress**: The user shows signs of crisis, distress, or vulnerability - **Ambiguity is unresolvable**: The AI can't determine intent even after clarification - **Scope boundary**: The request is outside what the AI is designed to handle - **Policy boundary**: The request approaches or crosses a guardrail - **Conflict**: The user disagrees with the AI and the disagreement can't be resolved ## Escalation Types - **To human support**: Transfer to a human agent with full context - **To the user themselves**: "This decision is yours to make" — handing back agency - **To a specialist**: Routing to domain-specific help (medical, legal, technical) - **To a supervisor/admin**: Flagging for organisational review - **Self-escalation**: The AI flags its own output for review before delivering it ## Designing the Escalation Experience The user's experience of escalation matters: - **Context transfer**: When escalating to a human, pass the full conversation. Don't make the user repeat themselves.
Details
- Skill name
escalation-design- Repository
- Owl-Listener/ai-design-skills
- Path
claude-plugin/ai-alignment-reasoning/skills/escalation-design/SKILL.md- License
- MIT
- Repo updated
- 9 June 2026
FAQ
What does the Escalation Design skill do?
When and how AI should escalate to humans, refuse, or ask for clarification.
How do I install the Escalation Design skill?
Claude Code plugin: /plugin marketplace add Owl-Listener/ai-design-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Escalation Design popular?
It lives in Owl-Listener/ai-design-skills, which has 207 GitHub stars and 37 forks.
Related skills
Agent Role Design
207Owl-Listener/ai-design-skills
Defining what each agent does, knows, and owns in a multi-agent system.
Behavioral Consistency
207Owl-Listener/ai-design-skills
Ensuring the AI behaves predictably across sessions, edge cases, and modalities.
Bias Detection Design
207Owl-Listener/ai-design-skills
Designing review workflows to surface and mitigate bias in AI outputs.
Extract Design
292danielvm-git/bigpowers
Extract a Google DESIGN.md file from an HTML prototype (claude.ai/design or any styled page) using Puppeteer, producing machine-readable tokens and AI-generated prose. Use when the user has an HTML prototype and wants a DESIGN.md to anchor their project's visual identity, or when seed-conventions has just scaffolded a new project.
Error Personality
207Owl-Listener/ai-design-skills
How the AI communicates mistakes, uncertainty, and limitations gracefully.
Failure Recovery
207Owl-Listener/ai-design-skills
What happens when an agent fails — retry, fallback, escalate, or graceful degradation.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.