cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution
npx skills add a5c-ai/babysitter --skill knowledge-consolidation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
- Cluster related notes into coherent themes - Build structured frameworks: concept maps, key principles, examples, applications - Cross-reference with existing frameworks in 05-knowledge - Preserve source attribution through consolidation - Quality-gated framework building with iterative refinement - Identify knowledge gaps needing additional capture ## Tool Use Instructions 1. Use `file-search` to find notes not yet consolidated into frameworks 2. Use `file-read` to load candidate notes and existing frameworks 3. Cluster related notes by topic similarity 4. Build framework structure: concept map, principles, examples, applications 5. Use `file-write` to create or update frameworks in 05-knowledge 6. Add cross-references between new and existing frameworks 7. Use `git-commit` to commit consolidated frameworks ## Examples ```json { "vaultPath": "./cog-vault", "mode": "knowledge-consolidation", "userName": "Alex", "targetQuality": 80 } ```
- Tool Use Instructions
- Examples
What does the cog-knowledge-consolidation skill do?
Build structured knowledge frameworks from scattered vault notes with source attribution
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill knowledge-consolidation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.