Skill 1
Design Agent Control Contract
Use when a repeated agent workflow lacks explicit accepted inputs, source authority, done evidence, tool boundaries, blocked outputs, or accountable owners.
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 3 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
Preview Agent Side Effect
Use when an agent proposes a write, send, publish, deploy, payment, permission change, CRM update, or other action that changes external state.
Skill 3
Bound Agent Retries
Use when an agent operation can fail, time out, replan, repeat a side effect, or leave execution state uncertain.
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.