agentsclimarketplace

Offboard

Skill BlaiseMoses01/obsidian-second-brain-starter/.claude/skills/offboard

Kaparthy LLM wiki style Obsidian vault template for Claude Code knowledge consolidation

Install
npx -y skills add BlaiseMoses01/obsidian-second-brain-starter --skill offboard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Tear down this vault's machine setup — remove the global skill symlinks from ~/.claude/skills and optionally clear SECOND_BRAIN_DIR. Never deletes vault content (skills, wiki/, dump/, notes). Use to uninstall the vault from a machine or before deleting the repo.

SKILL.md

1.3 KB, 274 tokens by cl100k_base, as published. Nobody here has run it

Offboard — remove this vault's setup

Reverses onboard. Removes only the global symlinks that resolve into this vault; your notes and the vault's own skills are left completely intact.

Steps

  1. Confirm intent. Ask whether to also clear SECOND_BRAIN_DIR from ~/.claude/settings.json (say no if other vaults or tools rely on it). Default: leave it.

  2. Run teardown: python3 ${CLAUDE_SKILL_DIR}/scripts/teardown.py $ARGUMENTS (append --remove-env only if the user said yes in step 1).

    • Removes every symlink in ~/.claude/skills that resolves into this vault.
    • With --remove-env, drops SECOND_BRAIN_DIR only if it equals this vault.
    • Read its UNLINKED= / SECOND_BRAIN_DIR: output.

  3. Report what was removed. Remind the user the vault itself (its .claude/skills, wiki/, dump/) is untouched — deleting the repo, if they want that, is a separate manual step.

Done when

  • This vault's global symlinks are gone and vault content is untouched.

Gives 0 of the 12 instructions most note taking skills give in 274 tokens

Counted across 686 of the 876 authors here whose files we hold, read 2026-08-06

  • include a visual element on every slidein 44 of 686, across 13 files
  • use wikilinks for internal vault linksin 35 of 686, across 11 files
  • commit to a single visual motif across every slidein 34 of 686, across 9 files
  • read pptxgenjs guide before creating presentations from scratchin 30 of 686, across 6 files
  • keep 0.5 inch minimum marginsin 30 of 686, across 7 files
  • use subagents to visually inspect rendered slidesin 30 of 686, across 6 files
  • re-verify affected slides after every fixin 27 of 686, across 5 files
  • run content QA checks before declaring successin 26 of 686, across 3 files
  • Use Markdown links for external URLs onlyin 26 of 686, across 10 files
  • pick a bold topic specific color palettein 24 of 686, across 2 files
  • read editing guide before editing existing presentationsin 23 of 686, across 1 file
  • use one dominant color across all slidesin 23 of 686, across 1 file

Said here and by no other author read

  • Confirm intent before clearing SECOND_BRAIN_DIR
  • Run the teardown script
  • Append --remove-env only if user confirmed
  • Read the unlinked and second-brain-dir output
  • Report what was removed
  • Remind user vault content is untouched

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.