
second-brain-ingest
Process raw source documents into wiki pages. Use when the user adds files to raw/ and wants them ingested, says "process this source", "ingest this article", "I added something to raw/", or wants to incorporate new material into their knowledge base.
- Installs
- 2.5K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/nicholasspisak/second-brain --skill second-brain-ingest- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads second-brain-ingest automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Second Brain — Ingest
Process raw source documents into structured, interlinked wiki pages.
Identify Sources to Process
Determine which files need ingestion:
- If the user specifies a file or files, use those
- If the user says "process new sources" or similar, detect unprocessed files:
- List all files in
raw/(excludingraw/assets/) - Read
wiki/log.mdand extract all previously ingested source filenames fromingestentries - Any file in
raw/not listed in the log is unprocessed
- List all files in
- If no unprocessed files are found, tell the user
Process Each Source
For each source file, follow this workflow:
1. Read the source completely
Read the entire file. If the file contains image references, note them — read the images separately if they contain important information.
2. Discuss key takeaways with the user
Before writing anything, share the 3-5 most important takeaways from the source. Ask the user if they want to emphasize any particular aspects or skip any topics. Wait for confirmation before proceeding.
3. Create source summary page
Create a new file in wiki/sources/ named after the source (slugified). Include:
---
tags: [relevant, tags]
sources: [original-filename.md]
created: YYYY-MM-DD
updated: YYYY-MM-DD
---
# Source Title
**Source:** original-filename.md
**Date ingested:** YYYY-MM-DD
**Type:** article | paper | transcript | notes | etc.
## Summary
Structured summary of the source content.
## Key Claims
- Claim 1
- Claim 2
- ...
## Entities Mentioned
- [[Entity Name]] — brief context
- ...
## Concepts Covered
- [[Concept Name]] — brief context
- ...
4. Update entity and concept pages
For each entity (person, organization, product, tool) and concept (idea, framework, theory, pattern) mentioned in the source:
If a wiki page already exists:
- Read the existing page
- Add new information from this source
- Add the source to the
sources:frontmatter list - Update the
updated:date - Note any contradictions with existing content, citing both sources
If no wiki page exists:
- Create a new page in the appropriate subdirectory:
wiki/entities/for people, organizations, products, toolswiki/concepts/for ideas, frameworks, theories, patterns
- Include YAML frontmatter with tags, sources, created, and updated fields
- Write a focused summary based on what this source says about the topic
5. Add wikilinks
Ensure all related pages link to each other using [[wikilink]] syntax. Every mention of an entity or concept that has its own page should be linked.
6. Update wiki/index.md
For each new page created, add an entry under the appropriate category header:
- [[Page Name]] — one-line summary (under 120 characters)
7. Update wiki/log.md
Append:
## [YYYY-MM-DD] ingest | Source Title
Processed source-filename.md. Created N new pages, updated M existing pages.
New entities: [[Entity1]], [[Entity2]]. New concepts: [[Concept1]].
8. Report results
Tell the user what was done:
- Pages created (with links)
- Pages updated (with what changed)
- New entities and concepts identified
- Any contradictions found with existing content
Conventions
- Source summary pages are factual only. Save interpretation and synthesis for concept and synthesis pages.
- A single source typically touches 10-15 wiki pages. This is normal and expected.
- When new information contradicts existing wiki content, update the wiki page and note the contradiction with both sources cited.
- Prefer updating existing pages over creating new ones. Only create a new page when the topic is distinct enough to warrant its own page.
- Use
[[wikilinks]]for all internal references. Never use raw file paths.
What's Next
After ingesting sources, the user can:
- Ask questions with
/second-brain-queryto explore what was ingested - Ingest more sources — clip another article and run
/second-brain-ingestagain - Health-check with
/second-brain-lintafter every 10 ingests to catch gaps
FAQ
What does the second-brain-ingest skill do?
Process raw source documents into wiki pages. Use when the user adds files to raw/ and wants them ingested, says "process this source", "ingest this article", "I added something to raw/", or wants to incorporate new material into their knowledge base.
How do I install second-brain-ingest?
Run npx skills add https://github.com/nicholasspisak/second-brain --skill second-brain-ingest in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/second-brain-ingest/ (personal) or .claude/skills/second-brain-ingest/ (project).
Which AI agents can use second-brain-ingest?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is second-brain-ingest safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains second-brain-ingest?
It is published by nicholasspisak in nicholasspisak/second-brain. It has 2,516 recorded installs.
More from nicholasspisak/second-brain
second-brain
nicholasspisak/second-brain
Set up a new Obsidian knowledge base with the LLM Wiki pattern. Use when the user wants to create a second brain, initialize a vault, set up a personal knowledge base, or says "onboard". Guides through an interactive wizard to configure vault name, location, domain, agent support, and tooling.
second-brain-query
nicholasspisak/second-brain
Answer questions against the knowledge base wiki. Use when the user asks a question about their collected knowledge, wants to explore connections between topics, says "what do I know about X", or wants to search their wiki.
second-brain-lint
nicholasspisak/second-brain
Health-check the wiki for contradictions, orphan pages, stale claims, and missing cross-references. Use when the user says "audit", "health check", "lint", "find problems", or wants to improve wiki quality.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.