Skill 1
Skill input contract writer
Use when an agent workflow needs accepted inputs, blocked inputs, approved sources, output shape, review gate, and eval cases before the agent runs.
Back to Skill Library
Agent governance workflow library
Agent workflow control review
Define input contracts, source labels, acceptance criteria, previews, approval packets, retry budgets, and permission receipts before agents act.
This is a complete workflow library with 7 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
Agent source labeler
Use when agent claims, proposed actions, summaries, or decisions need source identity before the workflow relies on them.
Skill 3
Agent acceptance criteria setter
Use when an agent task needs done criteria, evidence rules, source rules, tool rules, blocked outputs, and verification before work starts.
Skill 4
Agent action preview builder
Use when an agent proposes a write, send, deploy, publish, payment, CRM update, permission change, or other side effect.
Skill 5
Agent approval packet assembler
Use when a human reviewer needs the evidence packet for approving, rejecting, or escalating an agent action.
Skill 6
Agent retry budget setter
Use when an agent workflow needs retry limits, replanning limits, stop conditions, escalation triggers, and irreversible-action locks.
Skill 7
Tool permission receipt recorder
Use when an agent has used or is about to use a tool capability and the team needs an audit-ready record of why, how, and what changed.
Security fit check
Is the public Agent workflow control 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.
Workflow controlAI OperationsSecurityWorkflow 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.