walm00

Natural-language editor for .claude/quality/schedule-config.json. Users talk about maintenance scheduling in everyday language ("run audit twice a week", "turn off deep daydream", "switch dispatcher to 08:30") — this skill parses intent, validates against the schema, shows a concrete diff, asks for confirmation, and writes the change. WHEN TO USE: - User wants to change how often a job runs - User

Periodic maintenance of institutional knowledge. Analyzes lessons for staleness, overlaps, and gaps. Keeps lessons.json healthy.

Audits context architecture for CLEAR compliance, boundary enforcement, and consistency. WHEN TO USE: - User says "audit context for CLEAR" - User asks "check for duplication across data points" - User requests "find boundary violations in [area]" - Planning restructuring work - Before adding new data points (cleanup existing first) - Context quality improvement initiatives WHEN NOT TO USE: - Plan

Single-task dispatcher for CLEAR Context OS scheduled maintenance. Runs from the daily scheduled task, reads schedule-config.json, determines which jobs are due today, runs them in sequence, appends to the diary, writes a consolidated morning digest, and surfaces any frequency-tuning suggestions. WHEN TO USE: - Invoked automatically each morning by the `bcos-{PROJECT}` scheduled task - User says "