Skill 1
Accountability map builder
Use when an AI workflow or agent action needs named accountability, reviewer authority, escalation ownership, stop conditions, and audit trail before autonomy increases.
Back to Skill Library
Agent governance workflow library
Agent launch evidence review
Review accountability, tool permissions, disagreement, runnable examples, evals, rollback, and approval before agent launch.
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
Tool permission manifest writer
Use when an agent is about to receive a browser, file handle, MCP server, API, database, memory store, message-sending tool, or workflow action.
Skill 3
Disagreement log keeper
Use when multiple agents, reviewers, sources, eval runs, or research notes disagree and a final synthesis could hide uncertainty, minority evidence, or unresolved conflicts.
Skill 4
Runnable example set builder
Use when a prompt, workflow note, or Skill needs runnable examples before promotion into a reusable Skill, agent instruction, or public library.
Skill 5
Launch evidence gatekeeper
Use when accountability, tool permissions, disagreement, examples, eval results, approval, and rollback evidence need a final launch decision before an agent receives or expands authority.
Security fit check
Is the public Agent launch evidence 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.
Launch readinessAI 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.