skills-governance
- Repo stars 288
- Author updated Live
- Author repo ai-collab-playbook
- Domain
- Security
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @cnfjlhj · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Node.js
- Permissions
-
- Read-only
- Shell exec
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skills-governance
description: Use when auditing a large local skill collection, identifying duplicate or imported skills, comp…
category: security
runtime: Node.js
---
# skills-governance output preview
## PART A: Task fit
- Use case: 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. Use the bundled scanner as the source of truth for local skill inventory. Base recommendations on real directories and SKILL.md frontmatter inste….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Purpose / When to Use / How to Run It” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “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. Use the bundled scanner as the source of truth for local skill inventory. Base recommendations on real directories and SKILL.md frontmatter inste…”.
- **02** When the source has headings, the agent prioritizes “Purpose / When to Use / How to Run It” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, run shell commands, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Purpose / When to Use / How to Run It”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: skills-governance
description: Use when auditing a large local skill collection, identifying duplicate or imported skills, comp…
category: security
source: cnfjlhj/ai-collab-playbook
---
# skills-governance
## When to use
- Use when auditing a large local skill collection, identifying duplicate or imported skills, comparing skill roots, or…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Purpose / When to Use / How to Run It” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "skills-governance" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Purpose / When to Use / How to Run It
rules -> SKILL.md triggers / order / output contract
runtime -> Node.js | read files, run shell commands, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}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
- Run the scanner in
codexmode first. - If the results still do not explain the user's confusion, rerun in
allmode. - Explain the problem from roots, duplicate groups, and suspicious flags before recommending changes.
- Prefer Codex
[[skills.config]]disable suggestions over editing individualSKILL.mdfiles unless the user explicitly asks for direct file edits. - Separate recommendations into three buckets: keep, disable for now, and archive or external mirror.
- 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, orbackup-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
Decide Fit First
Design Intent
How To Use It
Boundaries And Review