What problem does it solve?
Provides a clear, reproducible governance framework for skill authors and reviewers to classify risk, select appropriate control tiers, and avoid ambiguous management terms that undermine safety and compliance.
Core Features & Use Cases
- Binary Governance Tiers: Mandates choosing either
baseline or strict based on deterministic triggers.
- Closed Strict Triggers: Defines a limited set of strict triggers for destructive actions, external writes, credential handling, and runtime or API configuration changes.
- Verification and Audit: Requires explicit actor/approval definitions, rollback and failure handling, retry limits, and mandatory history recording so reviewers can reproduce trigger evaluations and validate controls.
- Use Case: When authoring a skill that updates deployment configuration or writes to GitHub, use this rule to decide the
strict tier and document approvers, rollback steps, and verification tests.
Quick Start
Evaluate a draft skill by checking the strict trigger list, assign baseline or strict accordingly, and document required approvers, rollback paths, and verification steps.