Menu
Periodic maintenance of institutional knowledge. Analyzes lessons for staleness, overlaps, and gaps. Keeps lessons.json healthy.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 "run today's maintenance now" (manual dispatch) - User says "run the [job-name] job" (runs one job on demand, skips others)
Strategic reflection skill. Step back from daily work to think about the bigger picture of your context architecture, identify gaps, and envision improvements.
Wiki zone manager for BCOS — the universal long-form and cross-cutting content destination per plugin-storage-contract.md Rule 2. Stores runbooks, SOPs, decision logs, how-tos, glossaries, post-mortems, FAQs, meeting notes, and plugin cross-cutting context (charters, transcripts, research, customer-call notes). Two ingest paths: Path B (local files, pasted text, inbox promotion — runbooks/scripts/SOPs/notes) and Path A (external URLs / GitHub / YouTube). Schema-validated frontmatter, banner citations, builds-on graph for references, two-tier refresh, supersedes chains. Schema-driven, CLEAR-governed, derived-artifact. Invoke with /wiki.
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" / "Dump these meeting notes" - "I have an idea — park it somewhere" - "Read this article — not sure if it's relevant" - "Our competitor just announced X — update positioning" - Any time new information needs to enter the context architecture - Raw material should become a wiki explainer rather than a canonical data point
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 done. WHEN TO USE: - "I want to set up my business context" - "Here's my website / pitch deck / LinkedIn" - "Scan my repo and show me what context exists" - "What do I do next?" (after install) - "Help me get started" - First time adopting CLEAR Context OS in any project
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 / --verify-coverage flags only. Invoke with /context.
| name | lessons-consolidate |
| description | Periodic maintenance of institutional knowledge. Analyzes lessons for staleness, overlaps, and gaps. Keeps lessons.json healthy. |
| category | maintenance |
This skill IS:
This skill IS NOT:
Check the current state of lessons.json:
python .claude/scripts/consolidate_lessons.py
Identifies:
After analysis, with user approval:
Generate a health summary:
Good lessons are:
Use this boundary when bcos-wiki exists:
| Content | Owning surface |
|---|---|
| Atomic, reusable rule for future agents or humans | lessons.json via ecosystem-manager |
| Narrative incident explanation, timeline, causes, and follow-up context | Wiki post-mortem page-type |
| Decision narrative, alternatives considered, and why a choice was made | Wiki decision-log page-type |
| Step-by-step operational response | Wiki how-to or runbook page-type |
Lessons should stay short and actionable. Wiki pages can carry the richer story.
If consolidation finds a lesson that is really a narrative, recommend moving the
detail to /wiki create and keeping only the distilled lesson in
lessons.json.
Cross-reference: docs/_bcos-framework/architecture/wiki-zone.md defines wiki
page-type semantics and schema governance.
Remove or archive when:
.claude/quality/ecosystem/lessons.json.claude/quality/ecosystem/lessons-schema.md.claude/scripts/consolidate_lessons.py