Agent skill · operations · daymade
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).
Why this skill is useful
Adds specific commands and workflows for managing skill caches and ensuring source-of-truth discipline that the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-08-07. 1,320 stars on the source repository.
What this skill does
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; what fresh-host evidence will prove success. If the request is only “how many / what is loaded / why”, stay read-only. System model Never collapse these layers into one: 1. Canonical source — where owned behavior may be edited. 2. Installed inventory — bundles and versions that exist on disk. 3. Discovery policy — what Claude or Codex may discover. 4. Model-visible catalog — metadata in a fresh model prompt. 5. Runtime resources — hidden scripts, references, and assets a router still needs. Installed does not mean active; active does not prove visible; visible does not prove usable. Counts and byte totals are diagnostic values only. Authority order Use current runtime truth, not remembered conventions: owned source repos and their manifests for editable Skill behavior; claude plugin ... --json for current Claude marketplace/install state; the explicit source-sync activation manifest for managed Daymade links; ~/.agents/skills as Codex's current user Skill root; exact-path ~/.codex/config.toml policy for Codex discovery disables; codex debug prompt-input for the actual fresh Codex catalog; the installed vendor bundle for third-party cold resources. ~/.codex/skills is legacy/system compatibility unless a current local contract explicitly assigns it another role. Never move third-party inventory into an owned-source activation manifest just to make ownership look complete. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/skill-governance