Run any Skill in Manus with one click

Get Started

vault-setup

Stars2

Forks1

UpdatedApril 12, 2026 at 08:08

One-time setup to configure MCPVault for cross-project Obsidian vault access. Run this once per machine.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ciaranRoche

ciaranRoche/ducky

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	vault-setup
description	One-time setup to configure MCPVault for cross-project Obsidian vault access. Run this once per machine.
allowed-tools	["Bash"]
argument-hint	[vault-path]

Vault Setup: Configure Cross-Project Access

Register the MCPVault MCP server at user scope so every Claude Code session can access the Obsidian vault, regardless of which project directory you're in.

Behavior

Determine the vault path:
- If the user provided a path as an argument, use that
- Otherwise, default to /home/croche/Vault/Notes
- Verify the path exists using ls
Check if MCPVault is already configured:
```
claude mcp list --scope user
```
If an obsidian server is already listed, tell the user and ask if they want to reconfigure.

Register MCPVault at user scope:

claude mcp add obsidian --scope user -- npx @bitbonsai/mcpvault@latest [vault-path]

Report the result:
- Confirm the server was registered
- List the vault path configured
- Explain that all projects now have access to the vault via mcp__obsidian__* tools
- Note that Claude Code needs to be restarted for the new MCP server to take effect
Recommend global install for faster startup:
```
npm install -g @bitbonsai/mcpvault
```
This avoids the npx fetch delay on each session start. If globally installed, the user can reconfigure with:
```
claude mcp add obsidian --scope user -- mcpvault [vault-path]
```

Output Format

### Vault Setup Complete

MCPVault registered at user scope.
- Server: obsidian
- Vault: [path]
- Scope: user (available in all projects)

Restart Claude Code for the MCP server to activate.

For faster startup, install globally:
  npm install -g @bitbonsai/mcpvault

Available tools after restart:
  /webby:daily          — read today's daily note
  /webby:session-log    — log session summary to daily note
  /webby:vault-query    — search the vault
  /webby:vault-save     — save new knowledge to the vault

Notes

This only needs to be run once per machine
The vault path is machine-specific. On a new machine, run this with the correct path
The plugin's .mcp.json also includes MCPVault as a fallback, but user-scope registration ensures it works from every project

More from this repository

same repository

backlog-grooming

ciaranRoche/ducky

Weekly backlog audit — field completeness, staleness tiers, and duplicate detection. Run during grooming to clean up the backlog.

2026-05-262

create-bug

ciaranRoche/ducky

Creates a JIRA Bug with steps to reproduce, expected/actual behavior, and fix criteria. Activates when users ask to create a bug report, file a bug, or report an issue.

2026-05-262

create-epic

ciaranRoche/ducky

Creates a JIRA Epic with scope, success criteria, and child story breakdown. Activates when users ask to create an epic.

2026-05-262

create-story

ciaranRoche/ducky

Creates a JIRA Story with user story format, acceptance criteria, and technical notes. Activates when users ask to create a story or user story.

2026-05-262

create-task

ciaranRoche/ducky

Creates a JIRA Task for tech debt, infrastructure, documentation, or spike work. Activates when users ask to create a task, spike, tech debt ticket, or infrastructure work.

2026-05-262

daily-report

ciaranRoche/ducky

Daily briefing — sprint progress, new tickets, and recent comments in one report. Run this to get oriented at the start of the day.

2026-05-262

Vault Setup: Configure Cross-Project Access

Register the MCPVault MCP server at user scope so every Claude Code session can access the Obsidian vault, regardless of which project directory you're in.

Behavior

Determine the vault path:

If the user provided a path as an argument, use that
Otherwise, default to /home/croche/Vault/Notes
Verify the path exists using ls

Check if MCPVault is already configured:

claude mcp list --scope user

If an obsidian server is already listed, tell the user and ask if they want to reconfigure.

Register MCPVault at user scope:

claude mcp add obsidian --scope user -- npx @bitbonsai/mcpvault@latest [vault-path]

Report the result:

Confirm the server was registered
List the vault path configured
Explain that all projects now have access to the vault via mcp__obsidian__* tools
Note that Claude Code needs to be restarted for the new MCP server to take effect

Recommend global install for faster startup:

npm install -g @bitbonsai/mcpvault

This avoids the npx fetch delay on each session start. If globally installed, the user can reconfigure with:

claude mcp add obsidian --scope user -- mcpvault [vault-path]

Output Format

### Vault Setup Complete MCPVault registered at user scope. - Server: obsidian - Vault: [path] - Scope: user (available in all projects) Restart Claude Code for the MCP server to activate. For faster startup, install globally: npm install -g @bitbonsai/mcpvault Available tools after restart: /webby:daily — read today's daily note /webby:session-log — log session summary to daily note /webby:vault-query — search the vault /webby:vault-save — save new knowledge to the vault

Notes

This only needs to be run once per machine

The vault path is machine-specific. On a new machine, run this with the correct path

The plugin's .mcp.json also includes MCPVault as a fallback, but user-scope registration ensures it works from every project