Is governance safe to install?

SaferSkills independently audited governance (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/governance/SKILL.md · 1 file

.claude/skills/governance/SKILL.md1.6 KB · Markdown

name: governance

description: Govern how the design system evolves — SemVer for tokens/components, the contribution workflow, deprecation policy, and change communication. Use when the user wants to add/promote/deprecate a component or token, decide a version bump, set up a contribution process, or keep the system from fragmenting.

Skill: Governance

Keep the system consistent as it grows. Apply versioning, contribution, and deprecation rules.

Steps

Read workflows/governance.md (SemVer table, contribution workflow, deprecation policy, change comms).
Classify the change: major (breaking — renamed/removed token or prop, changed anatomy/default), minor (additive — new token/component/variant/optional prop), patch (fix — contrast/bug/doc/value tweak in tolerance).
For a new component/token: confirm it serves a real, repeated need (≥ 2 places) before promoting product → candidate → core. Design it to the full quality bar (CLAUDE.md Component Quality Bar).
For a deprecation: mark with reason + replacement + removal version; keep working ≥ 1 minor cycle; provide a migration map (design-systems/crosswalk.md style); remove only in a major.
Wire any new file into CLAUDE.md (File Reference Map + relevant table/router) and add a changelog entry.

Verification (definition of done)

Change has a SemVer level and a changelog entry.
Removals have a deprecation window, a replacement, and a migration table.
New spec meets the 8-state + a11y + token-mapping bar and is reachable via the router.
python3 scripts/validate_tokens.py passes; contrast re-checked if colors changed.

governance— agent skill

Is governance safe to install?

Skill: Governance

Steps

Verification (definition of done)

Audit the pieces. Scan the whole. Decide.