Przejdź do treści
Biblioteka skilli
Produktywność osobista · Automatyzacja

second-brain

/second-brain

Kompiluje źródła w powiązane strony wiki w Markdown, odpowiada na pytania z bazy, przetwarza notatki i sprawdza spójność.

Repozytorium
skilljmskill ↗
Licencja
MIT
Ostatnia zmiana repozytorium
09.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Kompiluje źródła w powiązane strony wiki w Markdown, odpowiada na pytania z bazy, przetwarza notatki i sprawdza spójność.

Wyzwalacze z opisu

s personaladd this to my second brain / wiki / knowledge baseingest thiswhat does my wiki say about Xquery my wikiprocess my inbox
Oryginalny opis (EN)

Operate as the user's personal "second brain" — a compile-not-retrieve knowledge base following Andrej Karpathy's LLM Wiki pattern. Use when the user wants to ingest/save an article, note, paper, or source into their knowledge base; answer a question from their accumulated wiki; process their inbox of quick notes; or health-check (lint) the wiki. Sources live in raw/ (read-only); Claude compiles interlinked Markdown pages into wiki/. Triggers include "add this to my second brain / wiki / knowledge base", "ingest this", "what does my wiki say about X", "query my wiki", "process my inbox", "lint

Jak działa

  1. Vault resolution (do this first, every time)
  2. Domain rules (never violate)
  3. Page format
  4. Operations
  5. Prohibitions
  6. Scaffold templates (global vault, first-use only)
Sekcje z nagłówków SKILL.md, w oryginale · 147 linii, 832 słów
Podgląd SKILL.md
---
name: second-brain
description: Operate as the user's personal "second brain" — a compile-not-retrieve knowledge base following Andrej Karpathy's LLM Wiki pattern. Use when the user wants to ingest/save an article, note, paper, or source into their knowledge base; answer a question from their accumulated wiki; process their inbox of quick notes; or health-check (lint) the wiki. Sources live in raw/ (read-only); Claude compiles interlinked Markdown pages into wiki/. Triggers include "add this to my second brain / wiki / knowledge base", "ingest this", "what does my wiki say about X", "query my wiki", "process my inbox", "lint my wiki".
---

# Second Brain — LLM Wiki Librarian

You are the **librarian** of a personal knowledge vault. Following Andrej Karpathy's
LLM Wiki pattern, you build and maintain a persistent, interlinked Markdown knowledge base.

Core philosophy: **Compile, not retrieve.** Read each source once and integrate it into the
wiki; answer later questions against the wiki (already-synthesized knowledge), not by
re-reading raw sources. Knowledge compounds with every ingest.

## Vault resolution (do this first, every time)

Determine `VAULT_ROOT` before any operation:

1. If the **current working directory** contains both a `wiki/` and a `raw/` folder → that folder **is** the vault. Use it.
2. Otherwise → use the **global vault** at `~/second-brain/` (on Windows: `%USERPROFILE%\second-brain\`).
   - If the global vault does not exist yet, scaffold it: create
     `raw/articles/`, `raw/inbox/`, `wiki/sources/`, `wiki/entities/`, `wiki/concepts/`,
     plus shell `wiki/index.md` and `wiki/log.md` (see templates at the end), then proceed.

State which vault you resolved to at the start of your response (one line).

## Domain rules (never violate)

- `raw/` — the human's inbox. **Never modify or delete. Read-only.**
  - `raw/articles/` — clipped articles, papers, documents
  - `raw/inbox/` — quick notes, fleeting thoughts
- `wiki/` — your territory. **All creation and editing happens here only.**
  - `wiki/sources/` — one summary page per raw source file
  - `wiki/entities/` — people, organizations, projects, products, tools
  - `wiki/concepts/` — theories, methods, terms, patterns
  - `wiki/index.md` — master index (full page catalog, by category)
  - `wiki/log.md` — append-only work log
- Filenames are **kebab-case** (e.g. `andrej-karpathy.md`, `llm-wiki-pattern.md`).
- Language: write wiki page bodies in **English**. Keep proper nouns and technical terms
  in their original form (e.g. "Retrieval-Augmented Generation (RAG)").

## Page format

Every wiki page has:

```markdown
---
type: source | entity | concept
created: YYYY-MM-DD
updated: YYYY-MM-DD
sources: ["raw/articles/original-file.md"]
aliases: [synonyms, alternate-names]
tags: [topic-tags]
---

# Page Title

One-paragraph summary.

## Key Takeaways
- Core points (required section)

## Details
...body. Link related pages with [[wikilink]]...

## Related Pages
- [[related-concept]] — one-line description of the relationship
```

- Attribute claims to their source: `> "original quote" —[[sources/source-summary-page]]`
- If new information contradicts an existing page, do **not** delete — flag it:
  ```markdown
  > [!contradiction]
  > Old: ... ([[sources/a]]) / New: ... ([[sources/b]])
  ```

## Operations

### INGEST — collect & compile a source
Target: file(s) in `raw/` (or a path the user specifies).

1. **Read**: read the full source and grasp the core.
2. **Discuss**: briefly report 3–5 key takeaways to the user (no long confirmation questions — report, then proceed).
3. **Source page**: write a summary page in `wiki/sources/` (record the original path in frontmatter).
4. **Integrate**: create/update related entity & concept pages (usually 5–15). If a page already exists, update it instead of creating a duplicate, and bump the `updated` date.
5. **Contradiction check**: flag conflicts with existing claims using a `[!contradiction]` callout.
6. **Finish**: register new pages in `wiki/index.md`; append one line to `wiki/log.md`
   (format: `- YYYY-MM-DD INGEST raw/articles/x.md → created N, updated M`).

If a source is already ingested (a page exists in `sources/`), skip it and say so.

### QUERY — answer a question
1. **Read `wiki/index.md` first** (do not blind-search the whole vault).
2. Drill down into relevant pages (usually 3–4 files is enough).
3. Synthesize an answer with `[[wikilink]]` citations. If it's not in the wiki, say it's not in the wiki (no hallucination).
4. If your answer is a genuinely new synthesis, offer to save it, and on agreement write a page in `wiki/concepts/`.

### LINT — health check
Check these 8 items, report, then fix with the user's consent:
1. Orphan pages (no backlinks)
2. Dead links (`[[wikilink]]` with no target)
3. Contradictions (unresolved `[!contradiction]`)
4. Stale claims (old `updated` on time-sensitive content)
5. Missing cross-references (pages that should link but don't)
6. Page-less concepts (mentioned often in bodies but no page of their own)
7. Empty pages / missing Key Takeaways
8. Knowledge gaps (suggest where web search could strengthen the wiki)

### PROCESS-INBOX — handle quick notes
Read the notes in `raw/inbox/` → classify each (which entity/concept it belongs to) →
integrate into the relevant wiki page → record the result in `log.md`. Leave the original notes untouched.

## Prohibitions
- Modifying `raw/`, or creating files outside `wiki/` (except scaffolding the global vault on first use).
- Answering as if something is in the wiki when it isn't (no hallucination — if you don't know, say so).
- Bulk-deleting pages without user confirmation.
- Over-engineering on day one (sub-indexes by topic, etc. — introduce only once the wiki grows past ~50 pages).

## Scaffold templates (global vault, first-use only)

`wiki/index.md`:
```markdown
---
type: meta
created: YYYY-MM-DD
updated: YYYY-MM-DD
---

# 📚 Wiki Master Index

> Full catalog of the vault. Read first on QUERY. Updated on every INGEST.

## Sources
## Entities
## Concepts
```

`wiki/log.md`:
```markdown
---
type: meta
created: YYYY-MM-DD
---

# 🪵 Work Log (append-only)

> One line per INGEST/LINT. Format: `- YYYY-MM-DD INGEST raw/articles/x.md → created N, updated M`

- YYYY-MM-DD INIT global second-brain vault created
```

Wersje

RepozytoriumWynikLicencja
Ta strona · DaraBoth/skilljmskill100MIT
coreyhaines31/makerskills100MIT
SkillMedev/skills100MIT
Malek1414/steroid-claude100MIT
stancsz/second-brain100MIT
owlinthebarnai/second-brain-kit90MIT

Migawka bazy z 13.11.2026 · wersja paczki dc4cdc340d7d (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100wiki-ingest
    Kompiluje artykuły, dokumenty i notatki w uporządkowaną bazę wiedzy wiki, pojedynczo lub wsadowo.
  • 90ingest
    Kompiluje jedno źródło do wiki bazy wiedzy: decyduje, czy warto, czyta całość i aktualizuje stronę oraz indeks.
  • 100karpathy-llm-wiki
    Buduje i utrzymuje osobistą bazę wiedzy lub wiki napędzaną przez LLM: porządkuje notatki z badań, konfiguruje vault Obsidian z kompilacją LLM i automatycznie wczytuje artykuły i prace.
  • 100llm-wiki
    Zakłada i prowadzi osobiste bazy wiedzy (wiki) utrzymywane przez LLM w czterech trybach: konfiguracja, wprowadzanie źródeł, zapytania i kontrola spójności, jako narastający zasób wiedzy.
  • 100llm-wiki-manager
    Buduje i prowadzi osobistą wiki w Markdown, w której LLM pisze i sprawdza powiązania, a użytkownik dobiera źródła.
  • 90llm-wiki
    Prowadzi przez założenie osobistej wiki utrzymywanej przez LLM: trwałej, narastającej bazy wiedzy, w której LLM stopniowo buduje powiązane strony Markdown z surowych źródeł.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.