skills governance

Security Community

Skill notes

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 codex mode first. If the results still do not explain the user's confusion, rerun in all mode. Explain the problem from roots, duplicate groups, and suspicious flags before recommending changes. Prefer Codex [[skills.config]] disable suggestions over editing individual SKILL.md files unless the user explicitly asks for direct file edits. Separate recommendations into three buckets: keep, disable for now, and archive or external mirror.

Output Contract

Report at least: scanned roots total skills enabled and disabled counts duplicate-name groups

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
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
Detected file/system behavior
  • Read-only
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Author source file SKILL.md

# 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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.