OS Health Check

The problem

Personal knowledge systems often rot because maintenance is neglected. You build the structure, but over time, files go stale, handoffs are skipped, and unprocessed material piles up without any systematic oversight.

What it does

• Audits five specific dimensions of system health including unprocessed backlogs and handoff discipline.
• Maps your specific file structure and identifies "stuck" material lacking summary blocks.
• Calculates freshness scores for core knowledge files like bio, voice, and values.
• Verifies project README currency and next-action accuracy across all active streams.
• Generates a color-coded status report with a prioritized action list for maintenance.

Why this beats prompting it yourself

General prompting often ignores structural signals and silent failures like missing READMEs or placeholder dates. This skill applies hardened thresholds and weighted rules derived from real-world system failures to ensure your environment stays functional, not just populated.

Use cases

• End-of-session audits to ensure handoffs and next steps are captured correctly.
• Start-of-week system sweeps to identify which core knowledge files need updating.
• Onboarding checks to verify a project workspace has the necessary documentation overhead.
• Catching "context loss" when you return to a project after a long break.

Known limitations

This skill performs structural audits only. It flags maintenance gaps but does not edit files or fix metadata automatically.