system-audit
Skill34 starsChanged 22 days agoMITView on GitHub
Health check of the assistant's own setup: agents, hooks, skills, settings, memory, and vault structure. Use for /system-audit, \"is everything wired up\", or after changing the configuration. It reports MCP servers only as connected or failing; to debug one, use /mcp-debug.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- vorteg/swagenticstheir own version, first seen Oct 13, 2026
- cogpros/system-audittheir own version, first seen Jul 4, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- vorteg/swagentics★ 1same name
- cogpros/system-audit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- add-agentSkill
- build-listSkill
- chart-tufteSkill
- councilSkill
- design-precheckSkill
- document-exportSkill
- handoverSkill
- index-memorySkill
- log-decisionSkill
- mcp-debugSkill
- meeting-prepSkill
- memory-debtSkill
- merge-contactsSkill
- morning-briefSkill
- post-callSkill
- reflectSkill
- setupSkill
- tasksSkill
- visual-explainerSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Verify the assistant's own configuration is intact and consistent.
- Very specific: line 12
Setup complete: Search the repo for unfilled placeholders, the pattern setup.sh fills (double braces around capitals, e.g.
- Very specific: line 13
Agents: Every file in .claude/agents/ (except _-prefixed ones) has valid frontmatter with name, description, and tools.
- Very specific: line 14
Hooks: Every hook referenced in .claude/settings.json exists on disk.
- Very specific: line 15
Skills: Every directory in .claude/skills/ has a SKILL.md with name and description frontmatter.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
System Audit
Verify the assistant's own configuration is intact and consistent. Run it after customizing the kit, or any time something feels off.
Checks
- Setup complete. Search the repo for unfilled placeholders, the pattern
setup.shfills (double braces around capitals, e.g. the assistant-name token). Any hit outsidedocs/or a.templatefile means setup did not finish. Report each one. - Agents. Every file in
.claude/agents/(except_-prefixed ones) has valid frontmatter withname,description, andtools. Thedescriptionsays when to use the agent. Flag any agent with an empty or vague description (routing will suffer). - Hooks. Every hook referenced in
.claude/settings.jsonexists on disk. Runbash scripts/init.shand report its result. - Skills. Every directory in
.claude/skills/has aSKILL.mdwithnameanddescriptionfrontmatter. - Settings.
.claude/settings.jsonis valid JSON.settings.local.jsonexists (created bysetup.sh). - Memory.
memory/MEMORY.mdexists and its links intomemory/topics/resolve. - Vault.
vault/has the expected folders andvault/00-Home.mdexists. - Modules. For each enabled module, its own check passes (see the module's README).
Output
A short verdict first: all green, or N issues. Then a checklist with PASS / WARN / FAIL per item, and for each FAIL the concrete fix. End with the single most important thing to fix, if anything.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.