@skill-mill/manage-governance
AManage governance policies for skills in config/governance.yaml. Set, remove, or list usage policies.
Install
agr install @skill-mill/manage-governance --target claudeWrites 1 file into .claude/skills/, pinned to git-618b8236.
- .claude/skills/manage-governance/SKILL.md
Document
name: manage-governance description: Manage governance policies for skills in config/governance.yaml. Set, remove, or list usage policies.
Manage Governance Policies
You are managing governance policies for the Agent Skill Harbor catalog.
File
- Config:
config/governance.yaml - Zod schema:
web/src/lib/schemas/governance.ts
Schema
usagePolicySchema: 'recommended' | 'discouraged' | 'prohibited' | 'none'
governancePolicySchema: {
usage_policy: UsagePolicy
note?: string
}
governanceSchema: {
policies: Record<string, GovernancePolicySchema> // key = skill path
}
Key Format
Skill path key: github.com/{owner}/{repo}/{skill-file-path}
Examples:
github.com/example-org/code-review/.claude/skills/review/SKILL.mdgithub.com/anthropics/prompt-library/SKILL.md
Actions
Parse the user's intent and execute the appropriate action below.
Set Policy
When the user wants to set a governance policy (e.g., govern github.com/owner/repo/SKILL.md recommended "reason"):
- Read
config/governance.yaml - Find or create an entry under
policieswith the skill path key - Set
usage_policyto one of:recommended,discouraged,prohibited - Optionally set
note - Write back
config/governance.yaml
Remove Policy
When the user wants to remove a governance policy or set it to none:
- Read
config/governance.yaml - Remove the entry from
policies - Write back
config/governance.yaml
List Policies
When the user wants to list governance policies:
- Read
config/governance.yaml - Display a table with: skill path, usage_policy, note
Important Notes
- All changes are made to local files only
- Remind the user to create a PR to apply changes
- After making changes, run
pnpm run build:catalogto regenerate the catalog
Trustgrade A
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- passLicense
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-618b823674ec2026-07-31