Menu
Escalate an issue with structured context via the configured alert channel.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | escalate |
| description | Escalate an issue with structured context via the configured alert channel. |
Create a structured escalation and deliver it to the owner via the configured alert channel.
exec cat memory/worker-handoff.json
Add new escalation entry with:
id: UUIDsource: the source systemurgency: high/medium/lowsummary: concise issue descriptiondetails: full contextcreatedAt: ISO timestampsurfacedAt: null (supervisor will set this)resolvedAt: nullWrite updated worker-handoff.json
If urgency is "high", immediately notify via the alert channel:
message(channel="$DELIVERY_CHANNEL", to="$ALERT_CHANNEL", text="<FORMATTED_ALERT>")
[urgency emoji] ESCALATION ([source])
[summary]
Context: [details]
Action needed: [suggested action]
Replace $DELIVERY_CHANNEL with your messaging channel (e.g., telegram, discord, slack).
Replace $ALERT_CHANNEL with the target chat/channel ID for high-urgency alerts.
Generate and apply structured code changes to a file
Fix agents that read stale production data instead of classifying direct benchmark prompts — add format detection at top of instructions
Diagnose and fix sub-agent configuration issues in YAML + instruction files that cause timeouts, tool failures, or degraded performance
Fallback persistence paths when primary tools (store_memory, create_note, write_file) are unavailable — memory blocks, task resolution fields, CRM notes, and reporting, in priority order.
Compose and send an email — using native GWS tools (never gog CLI for replies)
Create, advance, and resolve CRM tasks correctly — respecting status transitions, handling retries, and avoiding common API pitfalls.