skill-governance-rule

Classify skill governance risks and assign binary control tiers for sensitive operations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nowonbun/nowonbun-harness --skill skill-governance-rule
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-governance-rule
Source: https://github.com/nowonbun/nowonbun-harness/tree/main/codex-skills/skill-management_skill-governance-rule
Command: npx skills add https://github.com/nowonbun/nowonbun-harness --skill skill-governance-rule

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about skill-governance-rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify risk triggers for destructive skill actions?

Classify risk triggers for destructive actions by evaluating file operations, external writes, credential handling, and runtime configuration changes against a closed strict trigger list to determine required governance controls. This mandates selecting either a baseline or strict tier.

How do I add compliance and approval rules to a skill that writes to external systems?

Add compliance and approval rules to a skill by assigning the strict governance tier, then explicitly documenting approvers, rollback steps, and verification tests for external system writes. This ensures reproducible trigger evaluations and safe sensitive operations.

What is deterministic governance for skill authoring?

Deterministic governance for skill authoring is a framework that mandates binary tier selection and a closed set of strict triggers to control destructive actions. It eliminates ambiguous management terms to ensure safety and compliance reproducibility.

Do I need to document rollback and verification steps for every skill governance policy?

You need to document rollback and verification steps for every skill governance policy classified under the strict tier. Mandatory history recording, explicit actor definitions, and retry limits are required so reviewers can reproduce trigger evaluations.

When should I select the strict tier over the baseline tier for skill runtime configuration changes?

Select the strict tier over the baseline tier when a skill performs destructive file operations, external system writes, credential handling, or runtime and API configuration changes. These closed strict triggers require explicit approval and rollback controls.