Menu

Individual skill

escalation-design

0upvotes

When and how AI should escalate to humans, refuse, or ask for clarification.

skills/ai-alignment-reasoning/escalation-design/SKILL.md

Read pinned source

Source commit f41b650435b62dec6d5b1dc3598ac4679f8b7ae7

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
203
Repository last updated
Jun 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# 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)
Back to top