system_skill

Overview

This skill performs system maintenance with three core operations: integrity checks to find and fix broken references, documenting the current session from the live transcript, and catching up documentation for changes since the last update. It also includes security and privacy workflows like secret scanning and privacy checks. The skill runs visibly in the foreground and emits voice and text notifications so you can follow progress and results.

How this skill works

Before running, the skill loads any user customizations from a local preferences directory and applies overrides. Core workflows (IntegrityCheck, DocumentSession, DocumentRecent) are routed by trigger phrases and can be composed: integrity checks may produce fixes that feed into a session document, and periodic catch-ups produce multiple update entries. Security workflows run tools such as a TruffleHog wrapper for secret scanning and grep-based privacy checks over target directories.

When to use it

• After major refactoring or before releases (integrity check)
• At the end of a work session to capture what changed (document session)
• To catch up docs for work since the last recorded update (document recent)
• Before pushing code publicly or when auditing for leaked credentials (secret scanning)
• When you need a timeline of past work or context about prior changes (work context recall)

Best practices

• Run DocumentSession at end of every significant session to keep history current
• Run IntegrityCheck after refactors and then DocumentSession to persist fixes
• Run SecretScanning before public commits and periodically for hygiene
• Keep the local customization directory for team preferences to ensure consistent behavior
• Review visible outputs and voice notifications to confirm automated fixes before committing

Example use cases

• User: “Run an integrity check” → spawns agents, finds broken refs, optionally fixes and reports to MEMORY/STATE
• User: “Document this session” → reads current transcript, extracts changes and rationale, writes PAISYSTEMUPDATES entry
• User: “What’s undocumented? Catch up the docs.” → compares git history to last update, generates missing update entries
• User: “Check for secrets before I push” → runs TruffleHog wrapper and reports any exposed keys
• User: “We just worked on X — why is it broken?” → runs WorkContextRecall to present timeline and likely regressions