Skill 1
Exception trigger intake reviewer
Use when an agent exception, failed run, or proposed recovery action needs to be converted into a normalized escalation trigger before the agent continues.
Back to Skill Library
Agent governance workflow library
Agent Escalation Trigger Review
Turn vague agent exception handling into written stop, ask, downgrade, escalate, fail-closed, and resume rules before agents continue with tools.
This is a complete workflow library with 5 individual skills. Download the full library or pick the specific skill folder your team needs first.
Individual skills in this library
Use one skill at a time, or keep the full workflow together.
Some AI tools expect one skill folder per upload. Download the full library when you want the whole workflow, or download an individual skill when you only need one job done.
Skill 2
Action risk route mapper
Use when a proposed recovery action must be routed to stop, ask, downgrade, escalate, fail closed, or resume after approval.
Skill 3
Structured clarification ask builder
Use when an exception can be resolved by asking for missing non-sensitive information through a constrained clarification path.
Skill 4
Fail-closed evidence packet writer
Use when an exception involves prompt injection, hostile tool output, sensitive data, repeated tool failure, missing authority, or a high-impact action that must stop with evidence preserved.
Skill 5
Resume rule and owner recorder
Use when a stopped, downgraded, or escalated agent run needs a clear owner decision, expiry, rollback path, and resume condition before action continues.
Security fit check
Is the public Agent Escalation Trigger Review library enough, or does this need deeper review?
Use the public library when the workflow is low-risk, the inputs are already sanitized, and a team member can review the output before it reaches a buyer or customer.
Do deeper review when this workflow touches real tools, data sources, role ownership, approval paths, or customer-facing output.
Exception handlingAI OperationsSecurityWorkflow OwnerPlatform EngineeringTooling Owner
Good deeper-review trigger signals
- The workflow touches customer, prospect, CRM, proposal, security, pricing, or campaign data.
- Different teams disagree on the approved source of truth.
- The AI output could become customer-facing, revenue-impacting, or compliance-sensitive.
- You need reusable eval checks before asking more people to use the workflow.