Menu
Periodic integrity check. Reads memory, skills, vault state. Reports redundant rules, stale memories, broken links, drifted skills.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Personal Chief of Staff system for ADHD-ish operators. Vault-based, loop-driven, nervous-system-aware. Built and lived-in across daily sessions on real consulting, content, and long-running personal work.
First-time setup for the Chief of Staff system. Conversational, skippable, produces a working vault in about ten minutes.
Morning briefing. Reads vault state, delivers Must/Should/Could briefing, flags overdue waiting-for items.
Mid-session checkpoint. Saves to memory, flags Command Center or To-Do drift, rotates session context.
End of session. Reflects wins, updates Command Center, moves done tasks, writes to session log and memory.
| name | audit |
| description | Periodic integrity check. Reads memory, skills, vault state. Reports redundant rules, stale memories, broken links, drifted skills. |
| user_invocable | true |
Periodic integrity check. Run roughly every 7 sessions, or whenever the briefing surfaces an audit-due flag.
This is a read-mostly skill. Its job is to surface findings as a report. The user picks which fixes to make.
In parallel:
.claude/memory/MEMORY.md and every file it points at.SKILL.md under .claude/skills/.Command Center.md and To-Do.md from the vault._system/memory_firings.log.Walk through these in order. For each, return findings with concrete file paths and line references where applicable.
Are any two memory files saying the same thing? Are any two saying contradictory things? List candidates for merging or reconciliation.
Read each memory file's description frontmatter against the actual contents. Does the description still describe what's in the file? Flag mismatches.
For project-type memories: do the projects still exist and look active? Closed-project memories should be moved or marked.
Does MEMORY.md list every file in .claude/memory/? Is every file in the index actually present? Flag both directions of drift.
Scan memory files and skills for wikilinks ([[...]]) and markdown links ([...](...)) pointing at vault files. Flag any whose target doesn't exist.
For each SKILL.md, does the skill's described behavior match what CLAUDE.md, the docs, and the vault templates actually support? A common drift: a skill references a file or pattern that has since been renamed or removed.
Read _system/memory_firings.log. Count distinct session numbers. If under 10, skip this section with a short note: "Decay analysis is gated until the firings log holds 10 distinct sessions. Currently at N. Skipping."
If 10 or more, surface memory files that have not fired in the most recent 5 sessions. Don't recommend deletion. Surface for the user to review.
Return findings as a numbered list grouped by checklist section. For each finding: what's wrong, where it lives, a one-line proposed fix. Don't make any of the fixes. The user picks.
End the report with a one-line state summary: total memory files, total skills, last audit-counter value, decay-analysis status (gated or live).