{"slug":"knowledge-consolidation","title":"knowledge-consolidation","summary":"Build frameworks from scattered insights across all braindumps and notes","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-09-28T15:11:30.354355Z","repo":{"url":"https://github.com/huytieu/COG-second-brain","stars":1236,"forks":147,"license":"MIT","updatedAt":"2026-09-28T08:52:07Z"},"bodyHtml":"
\n

name: knowledge-consolidation\ndescription: Build frameworks from scattered insights across all braindumps and notes\nroles: [all]\nintegrations: []

\n

COG Knowledge Consolidation Skill

\n

Purpose

\n

Transform scattered insights from braindumps, daily briefs, and check-ins into coherent frameworks and \"single source of truth\" knowledge documents through pattern recognition and systematic synthesis.

\n

When to Invoke

\n\n

Agent Mode Awareness

\n

Check agent_mode in 00-inbox/MY-PROFILE.md frontmatter:

\n\n

Pre-Flight Check

\n

Get current timestamp (REQUIRED before generating any files):

\n
    \n
  1. Run date '+%Y-%m-%d %H:%M' using Bash to get the actual current date and time
    2. \n
  2. Store this value and use it for the created: frontmatter field
    3. \n
  3. NEVER guess or fabricate the time — always use the value returned by the date command
    4. \n
\n

Process Flow

\n

1. Data Gathering

\n

Scan vault for unprocessed or partially processed content:

\n\n

Determine scope:

\n\n

Gather statistics:

\n\n

2. Pattern Recognition

\n

Apply systematic pattern detection across all content:

\n

Frequency Analysis

\n

What comes up repeatedly?

\n\n

Temporal Clustering

\n

What insights emerged together?

\n\n

Domain Correlation

\n

What patterns cross domains?

\n\n

Contradiction Analysis

\n

Where does thinking conflict?

\n\n

Cross-Cutting Patterns

\n

Meta-patterns across all dimensions:

\n\n

3. Framework Development

\n

Synthesize patterns into actionable frameworks:

\n

Identify Core Principles

\n

From scattered insights to fundamental truths:

\n\n

Test Against Evidence

\n

Validate frameworks with source material:

\n\n

Define Boundaries

\n

When does framework apply/not apply?

\n\n

Create Applications

\n

How to use this framework:

\n\n

4. Knowledge Integration

\n

Update and create knowledge base documents:

\n

Update Existing Frameworks

\n

For each framework that needs updating, use the consolidated-knowledge template in references/templates.md.

\n

Save to: 05-knowledge/consolidated/[framework-name]-framework.md

\n

Create New Frameworks

\n

For newly identified frameworks, use the new-framework template in references/templates.md.

\n

Save to: 05-knowledge/consolidated/[framework-name]-framework.md

\n

Update Pattern Documentation

\n

Document the pattern using the pattern template in references/templates.md.

\n

Save to: 05-knowledge/patterns/pattern-[name].md

\n

Create Timeline Entries

\n

Build the timeline entry using the thinking-evolution template in references/templates.md.

\n

Save to: 05-knowledge/timeline/[topic]-evolution-YYYY-MM.md

\n

5. Generate Consolidation Report

\n

Create the master consolidation document using the report template in references/templates.md.

\n

Save to: 05-knowledge/consolidated/consolidation-YYYY-MM-DD.md

\n

6. Cleanup and Archival

\n

Mark processed braindumps:\nUpdate frontmatter in processed braindumps:

\n
status: \"consolidated\"\nconsolidated_in: \"[[consolidation-YYYY-MM-DD]]\"\nconsolidated_date: \"YYYY-MM-DD\"\n
\n

Archive outdated content:\nMove superseded frameworks or insights to:\n00-inbox/archive/[filename]-archived-YYYY-MM-DD.md

\n

Add note explaining why archived and what supersedes it.

\n

Maintain clean knowledge base:

\n\n

7. Confirm Completion

\n

After consolidation:

\n\n

Loop Engineering

\n

Consolidation is a loop-until-dry extraction with a completeness critic, not a single scan. See .claude/skills/loop-engineering/SKILL.md for the shared vocabulary.

\n

The loop: scan a batch of in-scope documents → extract themes, patterns, and candidate framework principles → run the completeness critic (\"any in-scope doc not yet read? any theme recurring across N+ docs that no framework captures yet?\") → if the critic surfaces something new, run another extraction pass → stop when 2 passes in a row surface nothing new (dry). In agent_mode: team, the first scan fans out as one worker per domain (personal / professional / per-project / briefs); each returns its conclusions only, and a synthesis pass merges them.

\n

The verifier (deterministic where it can be):

\n\n

Termination conditions (layered):

\n\n

Patterns: loop-until-dry (the spine) + plan-execute-verify (each pass) + orchestrator-workers (team-mode domain scans) + completeness critic.

\n

In-loop context: write the consolidation report incrementally and dedup new themes against the running set, not against the conversation. Externalizing to the report file is what keeps a large corpus from overflowing the window.

\n

Consolidation Guidelines

\n

Quality Over Quantity

\n\n

Preserve Nuance

\n\n

Maintain Traceability

\n\n

Living Documents

\n\n

Analysis Techniques Reference

\n

Pattern Detection Methods

\n
    \n
  1. Frequency Analysis: Count mentions, cluster topics
    2. \n
  2. Temporal Clustering: Group by time, track evolution
    3. \n
  3. Domain Correlation: Cross-domain connections
    4. \n
  4. Contradiction Analysis: Identify conflicts, track resolution
    5. \n
  5. Energy Pattern Detection: Emotional and practical patterns
    6. \n
\n

Framework Synthesis Process

\n
    \n
  1. Identify Core Principles: Extract fundamental truths
    2. \n
  2. Test Against Evidence: Validate with sources
    3. \n
  3. Define Boundaries: Establish applicability
    4. \n
  4. Create Applications: Develop use cases
    5. \n
  5. Document Evolution: Track development over time
    6. \n
\n

Timeline Construction Method

\n
    \n
  1. Mark Inflection Points: When thinking shifted
    2. \n
  2. Identify Catalysts: What triggered changes
    3. \n
  3. Document Evolution: How understanding developed
    4. \n
  4. Extract Learnings: What evolution teaches
    5. \n
\n

Success Metrics

\n\n

Common Use Cases

\n\n

Philosophy

\n

The knowledge consolidation skill embodies COG's self-evolving intelligence:

\n\n","files":[{"path":"references/templates.md","sizeBytes":11927,"isText":true},{"path":"SKILL.md","sizeBytes":11654,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"clean","suspicious":0,"notes":0,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-28T15:11:58.957932Z","sha256":"2302960C7D5E00C0FFDC011B7971B8C64D9031A565DD1CD8BC6660D754CC5A47","sizeBytes":8891},"review":null,"source":{"repositoryUrl":"https://github.com/huytieu/COG-second-brain","path":"skills/knowledge-consolidation","license":"MIT","commit":"4cdb6015dc6eb66f74bac513856ff6446ecb5d1b","subtreeSha":"D7FCA98B8C209A21F010FE675579B555D8612C17E2828A791060340DB289B0BF","lastSyncedAt":"2026-09-28T15:11:28.148164Z"},"reviewedAt":"2026-09-28T15:12:26.877863Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/huytieu/COG-second-brain/tree/main/skills/knowledge-consolidation"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install huytieu-cog-second-brain@llmmart"},{"target":"git","command":"git clone https://github.com/huytieu/COG-second-brain.git"}]}