Menu
One-time setup to configure MCPVault for cross-project Obsidian vault access. Run this once per machine.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| 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] |
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.
Determine the vault path:
/home/croche/Vault/NoteslsCheck 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:
mcp__obsidian__* toolsRecommend 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]
### 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
.mcp.json also includes MCPVault as a fallback, but user-scope registration ensures it works from every projectWeekly backlog audit — field completeness, staleness tiers, and duplicate detection. Run during grooming to clean up the backlog.
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.
Creates a JIRA Epic with scope, success criteria, and child story breakdown. Activates when users ask to create an epic.
Creates a JIRA Story with user story format, acceptance criteria, and technical notes. Activates when users ask to create a story or user story.
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.
Daily briefing — sprint progress, new tickets, and recent comments in one report. Run this to get oriented at the start of the day.