skills-governance
Use when auditing a large local skill collection, identifying duplicate or imported skills, comparing skill roots, or deciding what to keep, disable, or archive across Codex and adjacent agent skill directories.
Best use case
skills-governance is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when auditing a large local skill collection, identifying duplicate or imported skills, comparing skill roots, or deciding what to keep, disable, or archive across Codex and adjacent agent skill directories.
Teams using skills-governance should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/skills-governance/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How skills-governance Compares
| Feature / Agent | skills-governance | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when auditing a large local skill collection, identifying duplicate or imported skills, comparing skill roots, or deciding what to keep, disable, or archive across Codex and adjacent agent skill directories.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skills Governance ## Purpose Use the bundled scanner as the source of truth for local skill inventory. Base recommendations on real directories and `SKILL.md` frontmatter instead of stale catalogs or memory. ## When to Use - The user says they have too many skills and cannot tell what is useful. - The user wants a Codex-first keep or disable plan. - The user needs duplicate-name groups across multiple skill roots. - The user suspects imported plugin packs or mirrored skills are causing confusion. - The user wants a filesystem-backed inventory before changing skill settings. ## How to Run It Invoke the bundled `scan.js` from this skill directory. - Codex-first inventory: `node scan.js --mode codex --format markdown` - Cross-agent inventory: `node scan.js --mode all --format markdown` - Duplicate review only: `node scan.js --mode all --duplicates-only --format markdown` - Machine-readable output: `node scan.js --mode all --format json` ## Workflow 1. Run the scanner in `codex` mode first. 2. If the results still do not explain the user's confusion, rerun in `all` mode. 3. Explain the problem from roots, duplicate groups, and suspicious flags before recommending changes. 4. Prefer Codex `[[skills.config]]` disable suggestions over editing individual `SKILL.md` files unless the user explicitly asks for direct file edits. 5. Separate recommendations into three buckets: keep, disable for now, and archive or external mirror. 6. If the user asks to execute changes, list exact target paths and wait for confirmation first. ## Output Contract Report at least: - scanned roots - total skills - enabled and disabled counts - duplicate-name groups - suspicious flags such as `plugin-import`, `system`, or `backup-like` - a compact per-skill list when needed ## Acceptance A good run: - completes without external dependencies - reflects the actual filesystem state - shows duplicate groups by skill `name` - remains stable across repeated runs unless files changed
Related Skills
skill-governance-loop
Use when the user asks to review a skill, analyze skill quality, update a skill version, or run a repeatable keep/disable/archive decision loop from real failures instead of abstract best practices.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. Start with the skills.sh registry via `npx skills find`; if there are no good matches, fall back to a GitHub deep search for SKILL.md patterns before concluding no skill exists.
writing-anti-ai
This skill should be used when the user asks to "remove AI writing patterns", "humanize this text", "make this sound more natural", "remove AI-generated traces", "fix robotic writing", or needs to eliminate AI writing patterns from prose. Supports both English and Chinese text. Based on Wikipedia's "Signs of AI writing" guide, detects and fixes inflated symbolism, promotional language, superficial -ing analyses, vague attributions, AI vocabulary, negative parallelisms, and excessive conjunctive phrases.
xhs-note-creator
小红书笔记素材创作技能。当用户需要创建小红书笔记素材时使用这个技能。技能包含：根据用户的需求和提供的资料，撰写小红书笔记内容（标题+正文），生成图片卡片（封面+正文卡片），以及发布小红书笔记。
xhs-longform-private-publisher
This skill should be used when the user wants to publish an existing Markdown article to Xiaohongshu as a private longform post, keep the original wording and structure, insert inline images in order, use one-click layout, and verify the result in note manager.
timestamped-video-summary
Generate a detailed, professional video content summary from timestamped subtitles/transcripts (e.g., lines starting with 00:00 / 1:23:45). Enforce strict per-segment structure (timestamp range + bold segment title + 2-paragraph body: first-person creator summary + expert 【导师评注】 critique with uncertainty handling). Use when the user provides time-coded subtitles and asks for a规范化纪要/内容纪要/逐段总结, and optionally wants a clean PDF export (do NOT include the full raw transcript in the PDF unless explicitly requested).
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
session-recovery-codex
Use when recovering a Codex session, especially if the user provides a Codex session id or wants recent Codex sessions listed before resuming work.
research-lead-sidecar
Use when the user wants multi-agent division of labor for research-led work and the lead should stay on the critical path while 1-2 bounded sidecars handle low-coupling tasks. Do not use this for tiny tasks, fully sequential debugging, or overlapping refactors.
question-refiner
Use when a research question is still vague and must be clarified into a structured deep-research brief before actual literature research or execution. Skip this if the user already has a concrete paper draft or a ready-to-run research specification.
prompt-polisher
Use when receiving messy, unstructured input like voice transcriptions, stream-of-consciousness notes, or rough document content that needs to be transformed into a polished, optimized prompt. Cleans up filler words, extracts intent, asks clarifying questions, applies Claude 4.x/Opus 4.5/Sonnet 4.5 best practices, and previews the polished prompt for approval before execution. Trigger phrases include "polish this", "clean this up", "turn this into a prompt", or when input is clearly rough/unstructured.
proactive-explorer
落实 CLAUDE.md / AGENTS.md 中的“主动探索”原则，在向用户提问前自动使用 Grep、Read、Bash、WebSearch 等工具获取信息