skill-system-auditor
Skill System Auditor
Audit a skill collection as a system rather than as isolated skill files.
Use this skill when:
- the user asks for a global consistency audit of a skill repository
- newly added skills may have made README, AGENTS, CLAUDE, lifecycle categories, or role categories stale
- cross-skill routing, pair-with guidance, or memory writeback expectations need alignment
- user-observed agent regressions need to become stronger routing rules, execution contracts, templates, or validation checks
- future-skill references, obsolete TODOs, or implemented-gap mentions need cleanup
- helper paths, templates, frontmatter, or validation scripts need a maintenance pass
- the user wants to decide what skills are missing next
Do not use this skill to design a single new skill from scratch. Use skill-creator for the skill design mechanics, then use this skill to check whether the resulting collection remains coherent.
Pair this skill with:
skill-creatorwhen audit findings lead to new or revised skill instructions
More from a-green-hand-jack/ml-research-skills
project-init
Initialize an ML research project control root. Use for paper/code/slides repos, shared memory, GitHub Project alignment, agent guidance, worktree policy, and lifecycle handoffs.
39init-python-project
Initialize or enhance a Python/ML project. Use for new repos or forks needing production structure, uv environment setup, and research evidence docs.
37new-workspace
Create Git branches or worktrees for research code and paper versions. Use for experiments, baselines, rebuttal fixes, arXiv/camera-ready branches, and worktree memory.
36project-sync
Sync verified code-side experiment results into paper memory. Use when logs, reports, run docs, or user-confirmed metrics should become paper-facing evidence.
36init-latex-project
Initialize a LaTeX academic paper project. Use for new conference or journal papers needing templates, macros, venue preambles, and writing guidance.
36add-git-tag
Create annotated Git milestone tags. Use when completing a phase, releasing a version, or marking a research checkpoint.
36