Skip to content

coreyhaines31/makerskills / skills/second-brain

second-brain

Verified

When you want to capture into, compile, query, lint, or connect your personal Second Brain. Wraps the Karpathy LLM Wiki schema (Obsidian or any markdown vault) — raw/ (unprocessed sources), wiki/ (AI-compiled interlinked topic pages), outputs/ (generated artifacts). Vault defaults to ${SECOND_BRAIN_VAULT:-$HOME/Documents/SecondBrain}/. Six modes — capture (drop something into raw/), compile (process unprocessed raw files into wiki pages, update INDEX.md), query (answer a question from the wiki, save to outputs/), lint (orphans / contradictions / stale / unprocessed raw / topic gaps), connect (suggest new wikilinks between pages), search (quick lookup). Triggers on "/second-brain," "/sb," "capture this," "save this to my brain," "compile the wiki," "process raw notes," "query my wiki," "ask my brain," "lint the wiki," "find connections," "search my notes." Complements deep-research (external corpus) — this is the internal corpus. Team knowledge goes to company-brain, not here.

FileKindSize
SKILL.mdskill md11.7 KB
references/schema.mdmarkdown7.3 KB
references/templates/raw.mdmarkdown341 B
references/templates/wiki.mdmarkdown611 B
references/vault-config.mdmarkdown1.8 KB

references/schema.md

View on GitHub
# Schema (fallback)

**Authoritative source: `<vault>/CLAUDE.md` or `<vault>/AGENTS.md`.** This file is a fallback used only when the vault has neither.

The schema below mirrors the user's vault as of 2026-06-17. Update this file only if you're seeding a new vault from scratch.

---

## Folder structure

```
raw/          → Unprocessed source material (articles, highlights, ideas, notes, images)
wiki/         → AI-compiled knowledge base (topic pages, interlinked, with INDEX.md)
  INDEX.md    → Master index of all wiki pages with brief descriptions
outputs/      → Saved Q&A results, analyses, slide decks, research summaries
Projects/     → Project-specific notes (DO NOT modify)
Daily/        → Daily notes (DO NOT modify)
Templates/    → Note templates (DO NOT modify)
Inbox/        → Quick capture (DO NOT modify — see Inbox/Quick Capture.md)
```

## raw/ — file naming

Type prefixes:

**Personal / intellectual**
- `article-` — web article, blog post, news
- `idea-` — your own idea or proposal
- `highlights-` — book/article highlights
- `braindump-` — unstructured thinking
- `note-` — quick reference
- `resource-` — non-text (PDF, video, podcast, image)
- `tweet-` — single X post or thread
- `bookmark-` — URL + a one-line "why I saved this"

**Business / operational** (agency, consulting, client work)
- `call-` — call/meeting transcript (Riverside, Zoom, Otter)
- `meeting-` — meeting notes (your own, not auto-transcripts)
- `screenshot-` — image capture with context (UI, dashboard, competitor)
- `sop-` — standard operating procedure
- `email-` — customer / sales / prospect email worth preserving
- `objection-` — sales objection heard from a prospect (with context)
- `ticket-` — support ticket pattern worth remembering
- `person-` — contact / profile note (think CRM-lite, like Gbrain's people entity)

First line of each file:
```
source: <URL if applicable, or "call with X on YYYY-MM-DD", "email from X", etc.>
captured: YYYY-MM-DD
```

## wiki/ — page format

```markdown
# Topic Name

Brief summary (2–3 sentences).

## Key Concepts
- Concept with explanation

## Details
Main content organized by subtopic.

## Connections
- [[Related Topic]] — how it connects
- [[Another Topic]] — how it connects

## Sources
- `raw/article-example.md` — what was drawn from this source
```

## wiki/INDEX.md — format

```markdown
# Wiki Index

## <Category>
- [[Page Name]] — brief one-line description

## <Another Category>
- [[Page Name]] — brief one-line description
```

Standard categories (extend as needed):
- Creative
- Health & Longevity
- Faith & Personal Growth
- Business
- Personal Growth
- Tech
- Hobbies
- Sci-Fi
- Pets
- Personal Reference

### Suggested wiki pages that compose with other makerskills

Pages whose existence makes other skills sharper:

| Wiki page | Composes with | Why |
|---|---|---|
| **Decision Log** | `decide` | Narrative version of decisions made — the `decide` skill archives one-off decisions; the wiki page is the story of how decisions stacked over time on a topic |
| **Content Ideas** | `jab-hook` | Centralized hopper of hooks, frameworks, stories — drafted posts pull from here |
| **Customer Language** | positioning + sales | Verbatim phrases from prospects/customers — used for copy, headlines, objections |
| **Offer Notes** | positioning | What's been tried, what landed, what didn't |
| **Recurring Questions** | sales, client onboarding | Questions asked >3 times across calls; pre-answered for SOP / FAQ / scripts |
| **Workflow Docs** | `project-manager` | Documented operational patterns — what gets done, by whom, on what cadence |
| **People** | agency, fundraising, partnerships | Contacts with context — a CRM-lite. Inspired by Gbrain's people entity. |
| **Companies** | clients, prospects | Org profiles with last touchpoint, opportunity, status |
| **Sales Objections** | sales scripts | Library of objections + best responses |
| **Sales Scripts** | sales | Templates assembled from Customer Language + Objections |

### Outputs categories

The `outputs/` folder hosts generated artifacts. Common kinds:
- Posts (social drafts, blog drafts)
- Reports
- Proposals (especially for agency work)
- SOPs (your own + client deliverables)
- Audits (typical agency deliverable)
- Research briefs (composes with `deep-research`)
- Sales scripts
- Client summaries
- Slide deck content (handed off to `slide-deck`)

## Rules

- **One page per concept** — not per source
- **Use `[[wikilinks]]`** for all internal references
- **Keep pages focused** — split if >500 words
- **INDEX.md is the root** — keep current
- **Connections section is mandatory** — every page links to ≥1 other page
- **No orphan pages**
- **Summaries are concise**
- **Preserve nuance** — don't flatten contradictions

---

## Publishing alternatives — how to render `outputs/`

When `outputs/<file>.md` should leave the vault as a polished artifact (research brief to a client, summary to share, slide-deck source, archive PDF), use one of these:

### Default: pandoc + shared stylesheet

```bash
# PDF (requires basictex: brew install --cask basictex, then once:
# sudo tlmgr update --self && sudo tlmgr install collection-fontsrecommended)
pandoc "outputs/<file>.md" \
  --css ~/.local/share/makerskills/render.css \
  --metadata title="<title>" \
  --pdf-engine=xelatex \
  -o "outputs/<file>.pdf"

# HTML (standalone, CSS inlined — drop into a static host or email as attachment)
pandoc "outputs/<file>.md" \
  --standalone \
  --embed-resources \
  --css ~/.local/share/makerskills/render.css \
  --metadata title="<title>" \
  -o "outputs/<file>.html"
```

Shared stylesheet at `~/.local/share/makerskills/render.css` — also used by `read-book`. Edit freely; system-font + max-width 720 + print-optimized.

### Heavier option: Quarto (`.qmd`)

[Quarto](https://quarto.org) is Posit's publishing system — markdown-superset with executable code blocks (Python/R/Julia), native citations + bibliography, cross-references, equations, and multi-format output (HTML, PDF, slides, ePub, books, websites).

**Worth adopting if you want any of:**
- A renderable **public-facing personal handbook / book / website** from the wiki (Quarto projects build full sites with navigation, search, themes)
- **Native citations** in research briefs (BibTeX/CSL → consistent inline + bibliography)
- **Executable analysis** inline in notes (bloodwork charts, financial models, ML experiments)
- **Cross-references** to figures / tables / sections by name (richer than positional markdown links)

**Costs:**
- Obsidian doesn't render `.qmd` natively — daily-driver editing UX degrades
- `[[wikilinks]]` are Obsidian-only; Quarto wants standard markdown links
- YAML frontmatter conventions differ from Obsidian's
- New tool (`brew install quarto`, ~500MB) + optional Python/R engines
- Learning curve (callouts, cross-ref keys, project config, `_quarto.yml`)
- Most second-brain operations (capture, compile, query) gain nothing from Quarto

**Status: skipped by default.** Pandoc + shared CSS handles 80% of publishing needs with 5% of the complexity. Revisit Quarto if/when:
1. You decide to publish the wiki as a personal handbook site, OR
2. You start writing a book using the corpus, OR
3. You add executable analysis to your notes

For everyday capture / compile / query / outputs, plain markdown + pandoc is plenty.
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall