Skip to content
cccskills
FreePublished on GitHub

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.

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os
Works withObsidian
See how to install

Files included (1)

  • SKILL.md3.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

  1. Read the source completely before writing anything. Partial reads produce pages built from the introduction, which is where sources are least specific.
  2. 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.
  3. Write the source page in wiki/sources/. Record claims as claims, with the source attached.
  4. 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.
  5. 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.
  6. Update index.md and append to log.md in the same run, because an index that lags is how a vault starts drifting.
  7. 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

context-audit

Free

Audit an agent's context layout against the four places: system prompt, tools, history, tail. Use when the user asks to audit, review or fix their agent's context, prompt caching, token spend per turn, or CLAUDE.md / AGENTS.md layout. Read-only: reports findings and a fix list, changes nothing. Do NOT use for writing evals (evals-bootstrap) or for loop design (goal-test).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

evals-bootstrap

Free

Scaffold a first eval suite for an agent: mine real failures into cases, write behavioural checks over traces, and generate the runner. Use when the user wants evals, regression tests for an agent, a golden set, or asks how to know a prompt/model change did not break things. Do NOT use for a single task's done-check (goal-test) or for auditing context (context-audit).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

gate-check

Free

Find the decisions in a pipeline that do not need the expensive model and propose the gate for each: a rule, a classic classifier, or a small model, with fail-closed routing. Use when the user asks to cut model costs or latency, says the big model handles everything, or wants a triage / routing / filter layer in front of an agent. Analysis plus an optional baseline scaffold. Do NOT use for auditing context layout (context-audit) or for building eval suites (evals-bootstrap).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

goal-test

Free

Turn a vague task into a testable definition of done and generate an executable goal-test script for it, optionally with a bounded retry loop around a headless agent. Use when the user wants to run an agent in a loop, asks how to know when an agent task is finished, or says a goal like "improve X" needs to become checkable. Do NOT use for building eval suites over many cases — that is evals-bootstrap.

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

harness-audit

Free

Audit an agent's harness against the four rings: containment, guides, sensors, permissions. Use when the user asks whether their agent setup is safe, wants a review of sandboxing / permissions / hooks / AGENTS.md guardrails, or asks what a bad session could break. Read-only: reports the blast radius and a hardening list, changes nothing. Do NOT use for context layout (context-audit) or cost routing (gate-check).

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

second-brain-backfill

Free

Import a large archive into the vault in controlled batches: triage what is worth ingesting, process oldest first, checkpoint after every batch, and keep cost visible. Use this skill whenever the user wants to import years of bookmarks, an export from another notes app, a downloads folder, a chat history dump, or says "backfill", "bulk import", "process my archive". Do NOT use for ingesting one or a few new sources, which is second-brain-ingest.

The English summary is being prepared. Showing the original description.

undefined-ui/second-brain-os1.1KUpdated Oct 14, 2026

See all skills by undefined-ui

Report a problem with this skill