brain-dump-ingestion

Converts unstructured notes into atomic topics via a three-tier landing zone workflow.

Updated Nov 5, 2025
One-click install
npx skills add https://github.com/wlfmnstr/agentic-knowledge-base --skill brain-dump-ingestion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brain-dump-ingestion
Source: https://github.com/wlfmnstr/agentic-knowledge-base/tree/main/.claude/skills/brain-dump-ingestion
Command: npx skills add https://github.com/wlfmnstr/agentic-knowledge-base --skill brain-dump-ingestion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of converting unstructured "brain dumps" (transcripts, notes, raw ideas) into organized, valuable knowledge base content. It eliminates the manual effort of sifting through raw information, ensuring no valuable insights are lost while maintaining traceability and saving you hours of content curation.

Core Features & Use Cases

  • Structured Knowledge Extraction: Break down large, unstructured dumps into atomic, focused topics ready for documentation.
  • Landing Zone Workflow: Implement a three-tier content structure (brain-dumps, staging, docs) to refine content before integration.
  • Use Case: You have a 30-minute meeting transcript. Use this Skill to automatically extract key decisions, action items, and conceptual explanations, structuring them into separate, review-ready documents for your team's knowledge base.

Quick Start

Explain the "Landing Zone Architecture" for brain dump ingestion, detailing the purpose of the brain-dumps/, staging/, and docs/ directories.

Frequently Asked Questions about brain-dump-ingestion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert unstructured notes into organized knowledge base content?

Converting unstructured notes into organized content involves extracting atomic topics from raw material, then routing them through a landing-zone workflow with three tiers: brain-dumps for raw input, staging for review and refinement, and docs for final integration. This Skill automates that extraction and routing while preserving source context and traceability.

What's the landing-zone architecture for processing brain dumps?

The landing-zone architecture uses three directories: brain-dumps stores raw transcripts and notes, staging holds extracted topics awaiting review with metadata like title, date, source, and status, and docs contains finalized knowledge base content. This three-tier structure ensures reviewability and safe integration before publishing.

Can I automate extracting key points from meeting transcripts and meeting notes?

Yes. This Skill ingests transcripts and stream-of-consciousness notes, automatically extracting key decisions, action items, and conceptual explanations as separate, atomic topics. It captures metadata including title, date, source, duration, tags, and related topics to maintain full traceability from source to structured output.

How do I preserve source context when turning raw ideas into documentation?

This Skill captures source metadata—including title, date, source, duration, tags, and integration notes—for every extracted topic. This traceability chain ensures you always know where each piece of knowledge came from and maintains a complete audit trail from brain dump to final documentation.

Does this work with transcriptions, problem-solving narratives, and ideation sessions?

Yes. This Skill applies to transcriptions, stream-of-consciousness notes, meeting transcripts, problem-solving narratives, and ideation sessions. It extracts atomic topics from any unstructured raw material and routes them through the landing-zone workflow for review before integration into your knowledge base.

Related Skills