# Skill: system-audit

- **Name:** System Audit, Full
- **Trigger:** "audit my system" · monthly, or after any big change
- **Requires:** file access to the whole vault · read access to whatever is connected (calendar, email, scheduled jobs) makes it complete · Level: Optimum
- **Output:** A map of what the system IS (auto-loaded files with token costs, skills, tools), what is broken (dead jobs, dead keys, unused skills), where the holes are (security), how it compares to what is publicly available, and the top 5 fixes ordered by impact.
- **Safety:** READ ONLY. It changes nothing, deletes nothing, tightens nothing. It reports. Every fix waits for your OK as a separate job.

## Before you run it

Use the strongest model you have access to, at maximum thinking or effort
setting, and let it use parallel agents if the tool supports it. This is
the one skill where model quality visibly changes the result. A real run
takes 30 to 50 minutes. Do not run it on a fast cheap model to save time;
you will get a summary, not an audit.

## Steps

1. SYSTEM MAP. Answer: what is this system? Which files load automatically
   at the start of every session? Measure each in tokens. Judge each:
   lean or bloated, current or stale, and do any two contradict each other?
2. SKILLS. List every skill or trigger word the system knows. For each:
   when was it last used (check logs, file dates, or ask)? Flag skills
   unused for 30+ days. Then flag what is MISSING: compare against what
   people publicly build today and name up to 3 skills this system lacks.
3. TOOLS. List every connected tool: MCP servers, APIs, scheduled jobs,
   messaging channels. TEST each one, do not assume: does it still answer?
   Flag broken scheduled jobs, deleted or expired API keys, channels that
   stopped posting, tools connected but never called.
4. SECURITY. Where are the holes? What can connect to this system from
   outside? Which credentials sit in plain text and where? Which tools can
   write or send externally, and is each one gated behind my approval?
   Name the first thing you would tighten.
5. COMPARE. Against what is publicly available right now, where is this
   system behind? One honest paragraph, no flattery.
6. Report in five short sections matching the five checks above, then
   finish with: TOP 5 FIXES, ordered by impact, one line each. Do not fix
   anything in this run.

## Example run

Me: audit my system

AI (after ~40 minutes):
SYSTEM MAP: 6 auto-loaded files, 11.8k tokens total. Constitution current.
Focus file references a project that ended 3 weeks ago.
SKILLS: 14 triggers. 3 unused for 30+ days (image-brief, meeting-prep,
old-review). Missing vs the field: a call-transcript skill.
TOOLS: 9 connected. BROKEN: the 05:00 morning brief cron has failed
silently for 6 days (expired token). The database API answers. Slack
channel #brief last posted 6 days ago, matches the dead cron.
SECURITY: email password in plain text in ops/mail/config. Calendar
delete is NOT gated behind approval. Two things to tighten, in that order.
COMPARE: solid memory layer; behind on multi-agent use and voice input.
TOP 5 FIXES: 1) renew cron token · 2) gate calendar delete · 3) move
email password to a credentials file outside the vault · 4) archive the
dead project from focus · 5) delete or revive the 3 unused skills.

Me: fix 1 and 2.

## Make it yours

- Frequency: monthly is the default; weekly while you are actively
  building, quarterly once stable.
- Add a cost check as step 5b: list every paid AI tool and subscription
  the system uses and what each costs per month.
- If you run nothing on a schedule yet, step 3 shrinks to MCP servers
  only; the skill still earns its keep on steps 1, 2 and 4.