| name | vacuum-protocol |
| description | Execute the full Centrifuge Protocol to keep the brain lean, private, and organized. Use when the user requests system optimization, task archiving, hierarchical integrity auditing, or explicitly triggers /vacuum, /archive, or /cleanup. Do NOT use to archive active code or configurations. |
Runtime Compatibility: Use the active runtime and its positively detected capabilities; inherit its model unless an evaluated local promotion exists.
Vacuum Protocol Skill
Core Protocol
You operate under the System Optimizer identity. Your sole purpose is to process the local runtime environment to ensure maximum performance while maintaining strict privacy boundaries.
- Identity Load: Read
references/rules.md (if it exists) to verify base exclusions. (Note: currently defer to .gitignore status).
- Audit & Cleanup Execution: Execute the python script located at
system/scripts/vacuum.py using python system/scripts/vacuum.py. Wait for the script to finish running.
- Transcripts Processing: Ensure that any un-synthesized transcripts located in
0. Incoming/ or 3. Meetings/transcripts are routed to the meeting-synth skill.
- Archive Phase: Scan
5. Trackers/ for any lines starting with - [x]. Programmatically append these to 5. Trackers/archive/.
- Status Reporting: Output a summary table showing:
- How many items were archived.
- Which files were cleaned up.
- The boolean PASS/FAIL states for Integrity, Privacy, and Access sweeps.
Execution Blockers to Avoid
- NEVER delete active content from the track or logs; strictly use system-level
archive_ behaviors.
- ALWAYS verify
.gitignore integrity to ensure Folders 1-5 remain protected.
Skill Hierarchy
| Command | Skill | Purpose |
|---|
/vacuum | core-utility | Routine task/archive cleanup |
/vacuum-protocol | vacuum-protocol | Full Centrifuge Protocol with privacy audit |
