escalation — for Claude Code escalation, git-review, community, for Claude Code, ide skills, capability-diagnostic, junior-coder, explainer, optimizer, failure

v1.0.0
GitHub

Sobre este Skill

Cenario recomendado: Ideal for AI agents that need haiku (junior-coder, docs, explainer, optimizer). Resumo localizado: escalation helps AI agents handle repository-specific developer workflows with documented implementation details.

Recursos

Haiku (junior-coder, docs, explainer, optimizer)
Sonnet (coder, tech-lead, reviewer, qa, architect, explorer)
Opus (senior-coder, planner, red-teamer)
ALWAYS try the next tier first before jumping to Opus
Haiku → Sonnet → Opus (never Haiku → Opus directly)

# Core Topics

for Claude Code capability-diagnostic junior-coder explainer optimizer failure
monktui monktui
[0]
[0]
Updated: 2/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
55
Canonical Locale
en
Detected Body Locale
en

Cenario recomendado: Ideal for AI agents that need haiku (junior-coder, docs, explainer, optimizer). Resumo localizado: escalation helps AI agents handle repository-specific developer workflows with documented implementation details.

Por que usar essa habilidade

Recomendacao: escalation helps agents haiku (junior-coder, docs, explainer, optimizer). escalation helps AI agents handle repository-specific developer workflows with documented implementation details.

Melhor para

Cenario recomendado: Ideal for AI agents that need haiku (junior-coder, docs, explainer, optimizer).

↓ Casos de Uso Práticos for escalation

Caso de uso: Applying Haiku (junior-coder, docs, explainer, optimizer)
Caso de uso: Applying Sonnet (coder, tech-lead, reviewer, qa, architect, explorer)
Caso de uso: Applying Opus (senior-coder, planner, red-teamer)

! Segurança e Limitações

  • Limitacao: Exception: if the task is known to require Opus (architecture, cross-cutting), start there
  • Limitacao: Do NOT Escalate When
  • Limitacao: Agent needs more context (add skills/instructions instead)

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is escalation?

Cenario recomendado: Ideal for AI agents that need haiku (junior-coder, docs, explainer, optimizer). Resumo localizado: escalation helps AI agents handle repository-specific developer workflows with documented implementation details.

How do I install escalation?

Run the command: npx killer-skills add monktui/git-review/escalation. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for escalation?

Key use cases include: Caso de uso: Applying Haiku (junior-coder, docs, explainer, optimizer), Caso de uso: Applying Sonnet (coder, tech-lead, reviewer, qa, architect, explorer), Caso de uso: Applying Opus (senior-coder, planner, red-teamer).

Which IDEs are compatible with escalation?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for escalation?

Limitacao: Exception: if the task is known to require Opus (architecture, cross-cutting), start there. Limitacao: Do NOT Escalate When. Limitacao: Agent needs more context (add skills/instructions instead).

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add monktui/git-review/escalation. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use escalation immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

escalation

Install escalation, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Model Escalation

Escalation Tiers

Haiku (junior-coder, docs, explainer, optimizer)
  ↓ on failure
Sonnet (coder, tech-lead, reviewer, qa, architect, explorer)
  ↓ on failure
Opus (senior-coder, planner, red-teamer)

Never Skip Tiers

  • ALWAYS try the next tier first before jumping to Opus
  • Haiku → Sonnet → Opus (never Haiku → Opus directly)
  • Each tier gets ONE attempt before escalation
  • Exception: if the task is known to require Opus (architecture, cross-cutting), start there

Escalation Signals

Escalate to the next tier when:

  • Test failures: Agent's code fails tests and agent can't fix in one retry
  • Clippy warnings: Agent introduces warnings it can't resolve
  • Wrong output schema: Agent produces output that doesn't match expected format
  • Tech-lead BLOCKED twice: Tech-lead rejects the same agent's work twice on the same task
  • Task timeout: Agent exceeds expected completion time by 2x
  • Repeated hook blocks: Agent triggers enforcement hooks 3+ times on the same operation

Do NOT Escalate When

  • Task is simply large (break it down instead)
  • Agent needs more context (add skills/instructions instead)
  • Infrastructure error (retry, don't escalate)
  • First-time failure on a reasonable task (retry once at same tier)

Escalation Protocol

  1. Diagnose the failure (see capability-diagnostic skill)
  2. Determine if it's a model capability issue (Step 3 of diagnostic)
  3. If yes: re-assign task to next tier agent with original prompt + "Previous attempt failed because: [reason]"
  4. If no: fix the actual issue (context, tools, spec) and retry at same tier

Tracking

  • Log escalations to claude-mem: "Escalated [task type] from [tier] to [tier] because [reason]"
  • After 3+ escalations of the same task type → update agent-routing defaults
  • The optimizer agent reviews escalation patterns periodically

Habilidades Relacionadas

Looking for an alternative to escalation or another community skill for your workflow? Explore these related open-source skills.

Ver tudo

openclaw-release-maintainer

Logo of openclaw
openclaw

Resumo localizado: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
Inteligência Artificial

widget-generator

Logo of f
f

Resumo localizado: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and

★ 149.6k
⑂ 0
Inteligência Artificial

flags

Logo of vercel
vercel

Resumo localizado: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
Navegador

pr-review

Logo of pytorch
pytorch

Resumo localizado: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 98.6k
⑂ 0
Desenvolvedor