Skill 1
Tool result contract writer
Use when a raw or planned tool result needs a structured contract before an agent can trust it, store it, cite it, or use it for the next workflow step.
Back to Skill Library
Agent governance workflow library
Tool result contract review
Define source, schema, freshness, error, influence, and review boundaries before agents trust tool outputs.
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
Source and schema validator
Use when a result needs source-specific provenance, schema validation, required-field checks, and postcondition checks before the workflow relies on the value.
Skill 3
Freshness and error state checker
Use when a tool result has observed time, last modified time, expiration, TTL, retry state, environment drift, partial failure, or ambiguous error handling that affects trust.
Skill 4
Allowed influence boundary setter
Use when a result may influence planning, memory, tool selection, recipient, command, credential, file path, selector, target URL, control flag, CRM update, publish action, or other authority-bearing argument.
Skill 5
Result review gate router
Use when a contract needs a continue, revise, block, or escalate decision before an agent summarizes, stores, acts, publishes, deploys, writes, sends, or hands work to another agent.
Security fit check
Is the public Tool result contract 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.
Tool governanceAI OperationsSecurityPlatform EngineeringWorkflow 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.