Karpathy LLM Wiki
Astro-Han/karpathy-llm-wiki
A skill your agent uses when building or maintaining a personal LLM-powered knowledge base.
Review staged wiki writes and promote accepted pages to final locations when WIKISTAGEDWRITES is enabled.
Install Wiki Stage Commit
$ npx skills add Ar9av/obsidian-wiki --skill wiki-stage-commit -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-stage-commit --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.skills/wiki-stage-commit .claude/skills/wiki-stage-commit && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "wiki-stage-commit" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-stage-commit into .claude/skills/wiki-stage-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-stage-commit", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-stage-commitType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Ar9av/obsidian-wiki --skill wiki-stage-commit -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-stage-commit --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.skills/wiki-stage-commit .agents/skills/wiki-stage-commit && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "wiki-stage-commit" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-stage-commit into .agents/skills/wiki-stage-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-stage-commit", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ar9av/obsidian-wiki --skill wiki-stage-commit -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-stage-commit --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.skills/wiki-stage-commit .cursor/skills/wiki-stage-commit && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "wiki-stage-commit" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-stage-commit into .cursor/skills/wiki-stage-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-stage-commit", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Ar9av/obsidian-wiki.git --path .skills/wiki-stage-commit--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Ar9av/obsidian-wiki --skill wiki-stage-commit -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-stage-commit --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.skills/wiki-stage-commit .gemini/skills/wiki-stage-commit && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "wiki-stage-commit" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-stage-commit into .gemini/skills/wiki-stage-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-stage-commit", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Ar9av/obsidian-wiki wiki-stage-commitInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Ar9av/obsidian-wiki --skill wiki-stage-commit -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .github/skills && cp -r skills-src/.skills/wiki-stage-commit .github/skills/wiki-stage-commit && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "wiki-stage-commit" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-stage-commit into .github/skills/wiki-stage-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-stage-commit", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ar9av/obsidian-wiki --skill wiki-stage-commit -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ar9av/obsidian-wiki wiki-stage-commit --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.skills/wiki-stage-commit .opencode/skills/wiki-stage-commit && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "wiki-stage-commit" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/wiki-stage-commit into .opencode/skills/wiki-stage-commit/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "wiki-stage-commit", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
wiki-stage-commit- GitHub stars
- 3.5k
- Used in
- 1 other repo
- Token cost
- ~1.8k tokens
- SKILL.md length
- 683 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review staged wiki writes and promote accepted pages to final locations when WIKISTAGEDWRITES is enabled.
- Works in 5 steps: Inventory Staged Files → Per-File Review (interactive mode) → Apply Decisions → …
- Staging approval/commit
- SKILL.md covers Before You Start, Invocation Forms, Step 1: Inventory Staged Files and Step 2: Per-File Review…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Wiki Stage Commit is an agent skill from Ar9av/obsidian-wiki. Review staged wiki writes and promote accepted pages to final locations when WIKISTAGEDWRITES is enabled. Use for staging approval/commit; rejected pages return to raw/ for editing.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management, covering LLM wikis. The repository describes itself as: Framework for AI agents to build and maintain a digital brain through Obsidian wiki | Memory System for Agents. The licence is MIT.
When your agent uses it
- Staging approval/commit
- Rejected pages return to raw/ for editing
Example prompts
- “/wiki-stage-commit”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 0cc5d90. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Wiki Stage Commit loads about 1.8k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 683 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:14
. Set `WIKI_STAGED_WRITES=true` in your `.env` to use this feature." Then stop.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Ar9av/obsidian-wiki at commit 0cc5d90, republished under its MIT licence (© Ar9av). 683 words, ~1,833 tokens.
Download SKILL.mdSave it as
.claude/skills/wiki-stage-commit/SKILL.md (or your agent's skills folder).- name
- wiki-stage-commit
- description
- Review staged wiki writes and promote accepted pages to final locations when WIKI_STAGED_WRITES is enabled. Use for staging approval/commit; rejected pages return to _raw/ for editing.
Wiki Stage Commit — Staged Write Promotion
You are reviewing LLM-written pages that are waiting in _staging/ for human approval before they land in the live wiki. This skill is only useful when WIKI_STAGED_WRITES=true in the vault config.
Before You Start
- Resolve config — follow the Config Resolution Protocol in
llm-wiki/SKILL.md. This givesOBSIDIAN_VAULT_PATHandWIKI_STAGED_WRITES. - If
WIKI_STAGED_WRITESis not set or isfalse, tell the user: "Staged writes mode is not enabled. SetWIKI_STAGED_WRITES=truein your.envto use this feature." Then stop. - Read the
_staging/directory inventory.
Invocation Forms
/wiki-stage-commit # interactive review: show each file and ask accept/reject
/wiki-stage-commit --all # accept all staged files without per-file review
/wiki-stage-commit --reject-all # reject all staged files (move to _raw/ for manual editing)
/wiki-stage-commit --list # list staged files with summary, no changesStep 1: Inventory Staged Files
The CLI owns the inventory — don't glob _staging/ yourself:
obsidian-wiki staging list --jsonEach entry carries:
| Field | Meaning |
|---|---|
staged_path | vault-relative path of the staged file |
live_path | where it will land (a .patch.md targets the page it is named after) |
kind | new, update, or patch |
staged_revision | content hash of the staged file, as you are seeing it now |
live_revision | content hash of the live page, or null if there is none yet |
staged_mtime | when it was staged |
Keep staged_revision and live_revision for every file you show the user. They are what makes Step 3 refuse to overwrite an agent's concurrent write instead of silently clobbering it.
Report the inventory:
Staged files: 4 new pages, 2 updates
New pages:
_staging/concepts/attention-mechanism.md (staged 2026-09-08)
_staging/entities/andrej-karpathy.md (staged 2026-09-08)
Updates:
_staging/concepts/transformer-architecture.md (target: concepts/transformer-architecture.md)
Patches:
_staging/skills/prompt-engineering.patch.md (target: skills/prompt-engineering.md)If the list is empty, report: "Nothing staged. All writes have been committed or no staged writes have been produced yet."
Step 2: Per-File Review (interactive mode)
For each staged file (new pages first, then updates):
For new pages:
Display a summary:
--- New page: concepts/attention-mechanism.md ---
Title: Attention Mechanism
Tags: #ml #architecture
Summary: Core building block of transformers — computes weighted sum of values based on query-key similarity.
Tier: supporting
Confidence: 0.72
Sources: papers/attention.pdf
[Preview first 20 lines of body]
...
Accept [a], Reject [r], Skip [s], Preview full [p]?For patch files:
Display a structured diff:
--- Update: concepts/transformer-architecture.md ---
Source: _staging/concepts/transformer-architecture.patch.md
Proposed additions (+):
+ Transformers outperform RNNs on tasks requiring long-range dependencies. ^[inferred]
+ New source: papers/survey-2026.pdf
Proposed deletions (-):
- The attention mechanism was first described in [Bahdanau 2015]. (to be replaced by updated claim)
⚠️ Conflict check: live_revision no longer matches what was staged against. Review carefully.
Accept [a], Reject [r], Skip [s], Preview full diff [p]?If --all flag is set, skip prompting and accept every file.
If --reject-all flag is set, skip prompting and reject every file.
If --list flag is set, stop after printing the inventory (Step 1).
Step 3: Apply Decisions
The moves are mechanical and the CLI does them atomically. Pass the revisions from Step 1 so a decision made on stale information fails loudly.
Accepting a new page
obsidian-wiki staging promote <staged_path> \
--expect-staged <staged_revision> --expect-new--expect-new refuses if a live page has appeared since you listed — someone else got there first.
Accepting an update
obsidian-wiki staging promote <staged_path> \
--expect-staged <staged_revision> --expect-live <live_revision>Rejecting a file
obsidian-wiki staging discard <staged_path>It lands in _raw/rejected-<category>-<page>.md for manual editing. An earlier rejection of the same page is never overwritten — the second becomes -2.
Accepting a patch
promote refuses .patch.md files, because merging a human-readable diff into a page whose surrounding text may have moved is judgment, not a rename. Do it yourself:
- Read the target page and the patch.
- Apply the
+additions and-deletions as a merge — never overwrite the page wholesale. - Bump the target's
updatedfrontmatter. obsidian-wiki staging discard <patch staged_path>to clear the patch from the queue.
Show full SKILL.md (253 more words)Show less
When the CLI reports a conflict
Exit code 9 with conflict: ... on stderr means the staged or live file changed after you listed it. Nothing was moved. Do not retry with fresh revisions blindly — re-run staging list, show the user what changed, and ask again. The whole point of the check is that the content they approved is no longer the content that would land.
index.md is updated by the ingest that staged the page, so promotion does not touch it. log.md gets one STAGE_COMMIT line per invocation, written by the CLI.
Step 4: Update Tracking Files
The CLI appends the STAGE_COMMIT line to log.md itself. After processing all staged files, reconcile the index and hot cache so the promoted pages appear:
obsidian-wiki memory sync --takeaways "Committed N staged pages; rejected M."(No --verb: the log line was already written by staging promote.) Never hand-edit index.md, log.md, or hot.md — the command takes the lock that keeps a parallel writer from dropping your update.
Step 5: Report
Stage commit complete.
✅ Accepted (N):
concepts/attention-mechanism.md → now live
entities/andrej-karpathy.md → now live
concepts/transformer-architecture.md → updated (patch applied)
❌ Rejected (M):
skills/fine-tuning-llms.md → moved to _raw/rejected-skills-fine-tuning-llms.md
⏭️ Skipped (K):
references/attention-is-all-you-need.md → still in _staging/
Staging queue: K files remainingNotes
- Staged files use the same page template as live pages — they are ready to land, just awaiting approval
- Patch files use a human-readable diff format: lines starting with
+are additions, lines starting with-are deletions.staging promoterefuses them — merge them yourself (Step 3) index.mdandlog.mdare always updated immediately on ingest (they are low-risk tracking files) — only category pages go through staging- The moves live in
obsidian_wiki/staging.py; this skill supplies the judgment, not the file handling - The
_staging/directory is not tracked by Obsidian's graph view — pages only appear in the wiki after promotion
© Ar9av, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .skills/wiki-stage-commit of Ar9av/obsidian-wiki.
Open the folder on GitHubat commit 0cc5d90
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Ar9av/obsidian-wiki, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Wiki Stage Commit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Wiki Stage Commit this skillAr9av/obsidian-wiki | 3.5k | 1 repos | ~1.8k | Automated safety check: Notes | MIT | |
| Karpathy LLM WikiAstro-Han/karpathy-llm-wiki | 2.4k | — | ~3.6k | Automated safety check: Pass | MIT | |
| LLM Wiki Knowledge GraphEgonex-AI/Understand-Anything | 85k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| LLM Wikilewislulu/llm-wiki-skill | 655 | — | ~3.7k | Automated safety check: Pass | None | |
| Wiki Builderrohitg00/pro-workflow | 2.9k | — | ~1k | Automated safety check: Pass | None | |
| Wiki Queryrohitg00/pro-workflow | 2.9k | 1 repos | ~554 | Automated safety check: Pass | None |
Similar skills
LLM Wiki Knowledge Graph
Egonex-AI/Understand-Anything
Detects a Karpathy-pattern LLM wiki and builds an interactive knowledge graph with entities, implicit relationships and topic clusters.
LLM Wiki
lewislulu/llm-wiki-skill
Build and maintain a Karpathy-style LLM knowledge base — a self-compiling Obsidian markdown wiki where an Agent ingests raw sources, compiles cross-linked concept/entity/summary pages, answers…
Wiki Builder
rohitg00/pro-workflow
Start, structure, and grow a persistent research wiki indexed in pro-workflow's SQLite knowledge base.
Wiki Query
rohitg00/pro-workflow
Query pro-workflow wikis via SQLite FTS5 BM25 retrieval. An agent skill from rohitg00/pro-workflow.
Arkon Edit
nduckmink/arkon
Propose or directly apply edits to Arkon wiki pages, including proposing brand new pages.
More from Ar9av/obsidian-wiki
All 39 skills in this repoHermes History Ingest
Ar9av/obsidian-wiki
Ingest Hermes agent history into Obsidian as distilled knowledge.
Codex History Ingest
Ar9av/obsidian-wiki
Ingest Codex CLI conversation/session history into Obsidian as distilled knowledge.
Copilot History Ingest
Ar9av/obsidian-wiki
Ingest GitHub Copilot CLI/session history into Obsidian as distilled knowledge.
Obsidian Layout Adjustment
Ar9av/obsidian-wiki
Adjust the user's Obsidian visual layout with CSS snippets. An agent skill from Ar9av/obsidian-wiki.
Openclaw History Ingest
Ar9av/obsidian-wiki
Ingest OpenClaw session/history data into Obsidian as distilled knowledge.
Wiki Capture
Ar9av/obsidian-wiki
Turn the current conversation or finding into a structured permanent wiki note.
Related
Categories
Questions about Wiki Stage Commit
What does Wiki Stage Commit do?
Review staged wiki writes and promote accepted pages to final locations when WIKISTAGEDWRITES is enabled. Wiki Stage Commit is an agent skill from Ar9av/obsidian-wiki. Review staged wiki writes and promote accepted pages to final locations when WIKISTAGEDWRITES is enabled.
When should I use Wiki Stage Commit?
Wiki Stage Commit fits situations like: staging approval/commit; rejected pages return to raw/ for editing.
How do I install Wiki Stage Commit in Claude Code?
Run `npx skills add Ar9av/obsidian-wiki --skill wiki-stage-commit -a claude-code`. Or copy the skill folder (.skills/wiki-stage-commit in Ar9av/obsidian-wiki) into .claude/skills/wiki-stage-commit in your project. Claude Code loads it when a task matches its description.
How do I install Wiki Stage Commit in Codex?
Run `npx skills add Ar9av/obsidian-wiki --skill wiki-stage-commit -a codex`. Or copy the skill folder (.skills/wiki-stage-commit in Ar9av/obsidian-wiki) into .agents/skills/wiki-stage-commit in your project. Codex loads it when a task matches its description.
Can I use Wiki Stage Commit in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ar9av/obsidian-wiki --skill wiki-stage-commit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/wiki-stage-commit, .gemini/skills/wiki-stage-commit, .github/skills/wiki-stage-commit and .opencode/skills/wiki-stage-commit in your project.
What does Wiki Stage Commit need to run?
SKILL.md names no scripts, command-line tools or credentials: Wiki Stage Commit is instructions for the agent only.
Does Wiki Stage Commit access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Wiki Stage Commit safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Wiki Stage Commit use?
Wiki Stage Commit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Wiki Stage Commit use?
About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Wiki Stage Commit?
Skills that share tags, products or a category with Wiki Stage Commit: Karpathy LLM Wiki (Astro-Han/karpathy-llm-wiki, 2.4k stars), LLM Wiki Knowledge Graph (Egonex-AI/Understand-Anything, 85k stars), LLM Wiki (lewislulu/llm-wiki-skill, 655 stars) and Wiki Builder (rohitg00/pro-workflow, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Wiki Stage Commit?
Ar9av (a GitHub user) maintains it in Ar9av/obsidian-wiki, which has 3,529 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 6, 2026.
Source: Ar9av/obsidian-wiki on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.