CLEAR Context OS is the maintenance layer your second brain never had: ownership boundaries enforced mechanically, staleness surfaced on a schedule, drift propagated across linked docs, a dispatcher that learns from your clicks. One source of truth per topic. Searchable. Task-aware.
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…
The single entry point for getting anything new into your context architecture. Takes any input (documents, URLs, YouTube, meeting notes, pasted content) and triages it: dump to inbox, park in planned, or integrate into active docs. WHEN TO USE: "Here's a document — integrate it into my context" "Save this for later"…
First-run onboarding skill. Gets a new user from zero to a working context system. Claude asks one direct question upfront to pick the right scaffolding, then works from what the user shares — no long assessment ceremony beyond that. Creates a checklist that tracks setup progress across sessions and self-removes when…
Cross-zone retrieval and task-driven bundle resolution for BCOS. /context search ranks docs across every zone in one shared schema; /context bundle (P5) returns a curated, freshness-flagged, source-of-truth-aware context bundle for a declared task. Mechanical-first; LLM is opt-in via --semantic / --resolve-conflicts /…
Strategic reflection skill. Step back from daily work to think about the bigger picture of your context architecture, identify gaps, and envision improvements.
Validates documentation quality: markdown syntax, cross-references, JSON structure. WHEN TO USE: Validating markdown files for quality issues Checking cross-references between documents Validating JSON structure in ecosystem files As part of FIXED END validation in any scenario WHEN NOT TO USE: Content quality…
Manage the BCOS self-learning ladder: list learned rules, forget a rule, regenerate learned-rules.json from resolutions.jsonl. Mechanical-only — reads/writes derived artifacts; the actual learning happens via recordresolution.py at click time. Invoke with /learning.
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…
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…
Shared TodoWrite patterns for consistent progress tracking across all BCOS skills. This is a PATTERN LIBRARY, not an invocable skill. Skills copy these patterns inline. WHY INLINE, NOT INVOKED: If todo-utilities were invoked as a Task(), its TodoWrite calls would execute in an isolated context — invisible to the user.…
★not rated 21 3mo agoA125 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: