New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Nexus

by ProfSynapse in ProfSynapse/nexus

Read, search, and edit the user's Obsidian vault (notes, folders, canvas, bases, tasks, memory/workspaces, saved prompts) from the shell via the nexus CLI — no MCP connection needed.

MITAuto-check passedKnowledge Management

Install Nexus

skills CLI
$ npx skills add ProfSynapse/nexus --skill nexus -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ProfSynapse/nexus nexus --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ProfSynapse/nexus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill .claude/skills/nexus && rm -rf skills-src

Use ~/.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/

Facts

Skill name
nexus
GitHub stars
154
Token cost
~1.3k tokens
SKILL.md length
623 words
Files
6
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

Read, search, and edit the user's Obsidian vault (notes, folders, canvas, bases, tasks, memory/workspaces, saved prompts) from the shell via the nexus CLI — no MCP connection needed.

  • The user refers to their vault
  • SKILL.md covers Start here, The mindset (this is what… and The shape
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Asks you to find/read/change something stored there and the nexus command is on PATH

What it does

Nexus is an agent skill from ProfSynapse/nexus. Read, search, and edit the user's Obsidian vault (notes, folders, canvas, bases, tasks, memory/workspaces, saved prompts) from the shell via the nexus CLI — no MCP connection needed. Use whenever the user refers to their vault, notes, daily notes, second brain, or Obsidian, or asks you to find/read/change something stored there and the nexus command is on PATH. Do not use it to edit files in the current code repository; use normal file tools for those.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `playbooks/_preamble.md`, `playbooks/organize.md` and `playbooks/prompt.md`).

It sits in Knowledge Management, covering Second brain and Note-taking. It works with Obsidian and Model Context Protocol. The licence is MIT.

When your agent uses it

  • The user refers to their vault
  • Asks you to find/read/change something stored there and the nexus command is on PATH
  • Edit files in the current code repository
  • Use normal file tools for those

Example prompts

  • “/nexus”

What it can do on your machine

Read from SKILL.md and the folder at commit 6cb7bce. 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 powershell).

    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

Nexus loads about 1.3k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 623 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~117
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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 passed

The automated check found no risky patterns in SKILL.md.

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 ProfSynapse/nexus at commit 6cb7bce, republished under its MIT licence (© ProfSynapse). 623 words, ~1,327 tokens.

Download SKILL.mdSave it as .claude/skills/nexus/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
name
nexus
description
Read, search, and edit the user's Obsidian vault (notes, folders, canvas, bases, tasks, memory/workspaces, saved prompts) from the shell via the `nexus` CLI — no MCP connection needed. Use whenever the user refers to their vault, notes, daily notes, second brain, or Obsidian, or asks you to find/read/change something stored there and the `nexus` command is on PATH. Do not use it to edit files in the current code repository; use normal file tools for those.

Nexus vault CLI

nexus drives a running Nexus (Obsidian) vault from the shell over a local socket — no MCP config. It has two verbs: discover what you can do, then execute.

Start here

Run nexus --help first. It is the authoritative, always-current manual — commands, the context contract, CLI syntax, gotchas, and the tool catalog. It's offline and instant (no socket), so read it before your first real command instead of guessing.

For a common task, nexus playbook <name> gives you a ready-to-run recipe plus your workspaces and the exact tools it needs, in one call. Run nexus playbook to see what's available (typically: vault-work, organize, tasks, prompt).

The mindset (this is what --help can't teach you)

  • Explore → inspect → exploit. Search/list find locations; content read gets contents; then you write. A search hit is a {path, score}, not the note — never quote, summarize, or edit from a hit without reading it first.
  • nexus tools returns schemas, not data. It's discovery. Don't loop it hoping for vault content — that comes from nexus use --memory … --goal … -- content read ….
  • --memory and --goal are real and enforced. You're operating a person's live vault; pass a genuine running summary and objective, not placeholders.
  • --workspace and --session are pass-once. The vault remembers them: name a session and choose its workspace on the first call of a task (or run memory load-workspace <name>), then omit both — every later call continues that session and inherits its workspace. Nothing defaults silently: a session that never chose a workspace fails with "This session has no workspace yet" (only memory list-workspaces / load-workspace / create-workspace run before the choice). Pass a different value once to switch. nexus context shows what the vault currently remembers.
  • You can't escape the vault. Paths are vault-relative; .., ~, and absolute paths are rejected. That's a guardrail, not a bug.
  • Nothing is destroyed. The AI gets archive (reversible), not delete.
  • Windows: nexus vaults discovers local named pipes. If policy blocks enumeration, pass --vault <name> or set NEXUS_VAULT.
Show full SKILL.md (297 more words)Show less

The shape

nexus tools [selector]              # discover — tool schemas (never vault data)
nexus use --memory "<what you're doing>" --goal "<objective>" -- \
    <agent command --flags>         # execute — runs one tool, prints the result
nexus context                       # what this vault remembers: session + workspace

Add --session <name> --workspace <name> to the first use of a task only; the vault remembers both for every call after it.

The -- delimiter is canonical: context belongs before it; the tool command belongs after it. This avoids nested command-string quoting, especially in Windows PowerShell. The legacy one-string form remains supported.

Three rules that cover almost every way this goes wrong:

  • -- splits the two halves, and only that. Context flags (--memory, --goal, --session, --constraints, --vault) go before it; the agent name, tool name, and every tool flag go after it.
  • Pass a tool's required value positionally. Write memory load-workspace "Silicon Zone", not memory load-workspace --workspace "Silicon Zone". --workspace is also a context flag, so the positional form is the one that can't be misread.
  • Keep the agent name with the tool name. The command after -- is always <agent> <tool> [flags] — storage list, not list.
  • Context flags may sit before or after the verb. nexus --vault V use … and nexus use --vault V … are equivalent.

Malformed commands fail loudly with the corrected command in the error text — read it and retry rather than switching syntax forms. Nothing is silently dropped, so an error never means a partial write happened.

For multiline Markdown or content containing embedded quotes, keep the body out of shell argv. Any value-taking tool flag has a transport form: pipe with --<flag>-stdin or pass a local path with --<flag>-file (e.g. --content-stdin, --conversation-context-file ctx.md). Put the transport after the -- delimiter and do not also pass the flag directly. Never flatten multiline content to one line to dodge quoting:

powershell
Get-Content -Raw .\note.md |
    nexus use --memory "importing note" --goal "write note" -- content write --path Notes/Imported.md --content-stdin

Everything else — the flag table, per-tool schemas, syntax rules, the live per-vault catalog (including any enabled app agents) — comes from nexus --help, nexus tools <tool>, and nexus playbook <name>. Prefer those over guessing; they're always current.

© ProfSynapse, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files in skill of ProfSynapse/nexus.

  • SKILL.md
  • playbooks/_preamble.md
  • playbooks/organize.md
  • playbooks/prompt.md
  • playbooks/tasks.md
  • playbooks/vault-work.md

Open the folder on GitHubat commit 6cb7bce

Compare with similar skills

Nexus 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.

Nexus compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Nexus this skillProfSynapse/nexus154—~1.3kAutomated safety check: PassMIT
Obsidian Canvas BoardsAgriciDaniel/claude-obsidian15k—~1.4kAutomated safety check: PassMIT
Obsidian Bases EditorAgriciDaniel/claude-obsidian15k—~1.2kAutomated safety check: PassMIT
My LLM WikiMartinLwx/dotfiles140—~2.7kAutomated safety check: PassNone
Obsidian Knowledge BuilderMichael-OvO/obsidian-knowledge-agent205—~917Automated safety check: PassMIT
Obsidian Wiki IngestAgriciDaniel/claude-obsidian15k—~2kAutomated safety check: PassMIT

Similar skills

  • Obsidian Canvas Boards

    AgriciDaniel/claude-obsidian

    Creates, inspects and updates Obsidian JSON Canvas boards in a vault, with text, file, link, group and edge nodes, using safe recoverable edits.

    15k GitHub stars~1.4k tokensUpdated 27 days ago
    Knowledge ManagementAuto-check passed

  • Obsidian Bases Editor

    AgriciDaniel/claude-obsidian

    Explains, drafts and validates Obsidian Bases .base files, building filters, formulas and table, card or list views, and applying edits only through one inspected transaction.

    15k GitHub stars~1.2k tokensUpdated 27 days ago
    Knowledge ManagementAuto-check passed

  • My LLM Wiki

    MartinLwx/dotfiles

    Provides access to the user's personal wiki, including notes, research, project documentation, decisions, and archived knowledge.

    140 GitHub stars~2.7k tokensUpdated 18 days ago
    Knowledge ManagementAuto-check passed

  • Obsidian Knowledge Builder

    Michael-OvO/obsidian-knowledge-agent

    Turns PDFs, slides, syllabi, papers and transcripts into structured, teaching-quality Obsidian notes, matching how much structure is built to how much the material needs.

    205 GitHub stars~917 tokensUpdated 3 mo ago
    Knowledge ManagementAuto-check passed

  • Obsidian Wiki Ingest

    AgriciDaniel/claude-obsidian

    Files a single source or a bounded batch, pasted text, staged files or an approved URL, into an Obsidian vault as cross-linked notes with provenance, agreeing scope and network access first.

    15k GitHub stars~2k tokensUpdated 27 days ago
    Knowledge ManagementAuto-check passed

  • Obsidian Project Memory

    brycewang-stanford/Auto-Empirical-Research-Skills

    This skill should be used when the user asks to maintain an Obsidian knowledge base for a research project, import an existing research repository into Obsidian, keep project memory or daily notes…

    4.5k GitHub stars~2.4k tokensUpdated 2 days ago
    Knowledge ManagementAuto-check passed

More from ProfSynapse/nexus

All 12 skills in this repo

  • Nexus Agents

    ProfSynapse/nexus

    How to add, change and verify a Nexus agent or tool, and the contract every tool must satisfy.

    154 GitHub stars~843 tokensUpdated 5 days ago
    Auto-check passed

  • Nexus Eval Harness

    ProfSynapse/nexus

    Work on the Nexus LLM eval harness in tests/eval/ — author or fix a scenario fixture, write an eval config, change the executors, assertions or reports, or explain a run that produced nothing…

    154 GitHub stars~1k tokensUpdated 5 days ago
    Auto-check passed

  • Nexus Model Eval

    ProfSynapse/nexus

    Grade how well a model drives the Nexus two-tool protocol (getTools/useTools) and decide whether a low score is the model's fault or the harness's.

    154 GitHub stars~1k tokensUpdated 5 days ago
    Auto-check passed

  • Nexus Model Updates

    ProfSynapse/nexus

    Add, change or verify a Nexus LLM model definition — the registry entry, the provider default, and proof the model id actually works against the live endpoint.

    154 GitHub stars~1.1k tokensUpdated 5 days ago
    Auto-check passed

  • Nexus Release

    ProfSynapse/nexus

    Cut a Nexus release — bump the version with the repo's own machinery, get the docs and generated sources right, push a tag the GitHub Actions workflow will actually pick up, and recover when it does…

    154 GitHub stars~944 tokensUpdated 5 days ago
    Auto-check passed

  • Nexus Storage

    ProfSynapse/nexus

    How to change, persist, migrate and recover Nexus data without losing it.

    154 GitHub stars~749 tokensUpdated 5 days ago
    Auto-check passed

Works with

Categories

Questions about Nexus

What does Nexus do?

Read, search, and edit the user's Obsidian vault (notes, folders, canvas, bases, tasks, memory/workspaces, saved prompts) from the shell via the nexus CLI — no MCP connection needed. Nexus is an agent skill from ProfSynapse/nexus. Read, search, and edit the user's Obsidian vault (notes, folders, canvas, bases, tasks, memory/workspaces, saved prompts) from the shell via the nexus CLI — no MCP connection needed.

When should I use Nexus?

Nexus fits situations like: the user refers to their vault; asks you to find/read/change something stored there and the nexus command is on PATH; edit files in the current code repository; use normal file tools for those.

How do I install Nexus in Claude Code?

Run `npx skills add ProfSynapse/nexus --skill nexus -a claude-code`. Or copy the skill folder (skill in ProfSynapse/nexus) into .claude/skills/nexus in your project. Claude Code loads it when a task matches its description.

How do I install Nexus in Codex?

Run `npx skills add ProfSynapse/nexus --skill nexus -a codex`. Or copy the skill folder (skill in ProfSynapse/nexus) into .agents/skills/nexus in your project. Codex loads it when a task matches its description.

Can I use Nexus 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 ProfSynapse/nexus --skill nexus -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nexus, .gemini/skills/nexus, .github/skills/nexus and .opencode/skills/nexus in your project.

What does Nexus need to run?

SKILL.md names no scripts, command-line tools or credentials: Nexus is instructions for the agent only.

Does Nexus 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 Nexus safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Nexus use?

Nexus 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 Nexus use?

About 1.3k tokens (SKILL.md is roughly 5.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 Nexus?

Skills that share tags, products or a category with Nexus: Obsidian Canvas Boards (AgriciDaniel/claude-obsidian, 15k stars), Obsidian Bases Editor (AgriciDaniel/claude-obsidian, 15k stars), My LLM Wiki (MartinLwx/dotfiles, 140 stars) and Obsidian Knowledge Builder (Michael-OvO/obsidian-knowledge-agent, 205 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nexus?

ProfSynapse (a GitHub user) maintains it in ProfSynapse/nexus, which has 154 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 2, 2026.

Source: ProfSynapse/nexus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.