Second Brain Ingest

CommunityPopular

undefined-ui

second-brain-ingest

Turn raw source material in a second-brain vault into linked wiki pages: read the source, split it into concepts and entities, write or update pages, connect them to existing pages, and record the run in the log. Use this skill whenever the user drops a file into raw/, pastes an article, transcript or PDF and asks to add it to the vault, says "ingest this", "add this to my second brain", "process raw", or asks to catch up on unprocessed sources, even if they do not name the ingest command. Do NOT use for answering questions from an existing vault, for linting or repairing pages, or for editing notes the user wrote by hand.

Overview

Publisher	undefined-ui
Repository	`second-brain-os`
Skill name	`second-brain-ingest`
Stars	1K
Forks	166
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by undefined-ui on GitHub. Read the source before you install it.

Installation

Install the Second Brain Ingest AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/undefined-ui/second-brain-os/tree/main/skills/second-brain-ingest
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/undefined-ui/second-brain-os.git /tmp/second-brain-os
mkdir -p .claude/skills
cp -r /tmp/second-brain-os/skills/second-brain-ingest .claude/skills/second-brain-ingest

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Second Brain Ingest in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Second Brain Ingest on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Second Brain Ingest is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Ingest a source

An ingest that only writes a summary page produces a vault that grows without getting smarter. The whole value is in the second half of the job: connecting the new material to what is already there. A page that lands unlinked is invisible within a week.

Core rule

Nothing is ingested until it is linked. Every run ends with the new pages connected to existing pages in both directions.

Workflow

Read the source completely before writing anything. Partial reads produce pages built from the introduction, which is where sources are least specific.
Check what already exists. Search the wiki for the main entities and concepts. Ingesting into an empty vault and ingesting into a vault of 300 pages are different jobs: in the second, most of your work is updating pages, not creating them.
Write the source page in wiki/sources/. Record claims as claims, with the source attached.
Extract concepts and entities. One page per idea. If a concept page exists, add what this source contributes and update updated:. If it contradicts what is there, record both positions rather than replacing.
Link in both directions. The source page links to every concept and entity it touches; each of those links back. Add any missing target pages, or list them under Gaps in index.md.
Update index.md and append to log.md in the same run, because an index that lags is how a vault starts drifting.
Report what changed.

Output format

End every run with this exact shape:


Ingested: <source name>
New pages: <n> (list)
Updated pages: <n> (list)
Links added: <n>
Contradictions found: <none | description>
Gaps created: <list of linked pages that do not exist yet>

Calibration

Over-extraction is the common failure: ten thin concept pages from one article, each a restated paragraph. A source usually yields one to three concepts worth their own page. If a candidate concept cannot be explained without referring back to this one source, it belongs inside the source page instead.

Under-extraction shows up as source pages that contain three separate ideas and link to nothing. If a page needs section headings for unrelated topics, split it.

Example

Input: the user drops raw/karpathy-llm-wiki.md, a clipped gist, into a vault that already has pages for [[Obsidian]] and [[Claude Code]].

Output: one source page; a new concept page [[LLM wiki]] explaining the pattern in plain language; an entity page [[Andrej Karpathy]]; updates to [[Obsidian]] and [[Claude Code]] noting their role in the pattern; a link from the existing [[Personal knowledge management]] concept to the new one; index and log updated; report showing 3 new, 3 updated, 11 links.

Frequently asked questions

What does the Second Brain Ingest AI skill do?

Why use Second Brain Ingest on TypingMind?

Because you install it once and use it with any model. Second Brain Ingest is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Second Brain Ingest in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/undefined-ui/second-brain-os/tree/main/skills/second-brain-ingest. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Second Brain Ingest?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Second Brain Ingest?

As many as you like. As long as a model supports skills, you can use Second Brain Ingest with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Second Brain Ingest AI skill free?

Yes. It is published on GitHub by undefined-ui under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Karpathy Guidelines

multica-ai

OrganizationPopular

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define…

Create Agent

Create a custom agent (.agent.md) for a specific job.

Create Hook

Create a hook (.json) to enforce policy or automate agent lifecycle events.

Generate Run Commands

microsoft

OrganizationPopular

Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Ingest a source

Core rule

Workflow

Output format

Calibration

Example

Frequently asked questions

Related AI Skills

Set up your own AI workspace now