Individual skill

skill-governance

Governs the Claude Code/Codex Skill surface: reconciles source/install/catalog-visibility drift without losing cold capability. Use when users ask how many Skills load, why the catalog is truncated, want routers visible while other bundles stay cold, or need duplicate/superseded-Skill or old-cache cleanup. Not for building a marketplace manifest (use marketplace-dev) or repo audits (use marketplace-health-check).

daymade-skill/skill-governance/SKILL.md

Read pinned source

Source commit 7c4d326ddd94d504e00e241ba49498e95160afbe

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,522
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Skill Governance

Govern the Skill surface the user actually experiences: the intended hot or
router entries are fully visible in a fresh host, cold capabilities remain
reachable, editable behavior has one canonical owner, and every retirement is
recoverable. A smaller directory count is not the outcome.

## Required outcome contract

Before acting, state in one sentence:

- which entries or routers must be model-visible;
- which capabilities must remain available cold;
- which layer the user authorized changing;