Manage prompts in your Obsidian vault. Use for saving, listing, and loading reusable prompts. Triggers on /obsidian commands, Obsidian vault operations, or prompt management requests.
/plugin marketplace add leweii/obsidian-prompt-manager/plugin install obsidian@obsidian-pluginsThis skill is limited to using the following tools:
config.template.jsonManage reusable prompts in your Obsidian vault from Claude Code using native tools.
Configuration is stored in the skill's config.json:
{
"vaultPath": "/path/to/your/vault",
"promptsFolder": "Claude-Prompts"
}
Config location: ~/.claude/skills/obsidian/config.json (personal) or .claude/skills/obsidian/config.json (project)
/obsidian setup <vault-path>Configure your Obsidian vault path.
Steps to execute:
Validate path exists:
Use Bash: ls -la <vault-path>
If path doesn't exist, inform user and stop.
Create prompts folder:
Use Bash: mkdir -p <vault-path>/Claude-Prompts
Save configuration: Use Write tool to update config.json:
{
"vaultPath": "<vault-path>",
"promptsFolder": "Claude-Prompts"
}
Confirm to user: "Vault configured: <vault-path> Prompts folder: <vault-path>/Claude-Prompts"
/obsidian save "<title>" [--tags tag1,tag2]Save a prompt to your Obsidian vault.
Steps to execute:
Read config:
Use Read tool on config.json to get vaultPath.
If vaultPath is empty, ask user to run /obsidian setup first.
Get prompt content: Ask user: "What content should I save for this prompt?"
Create markdown file:
Use Write tool to create <vaultPath>/Claude-Prompts/<title>.md:
---
title: "<title>"
date: <YYYY-MM-DD>
tags:
- claude-prompt
- <additional tags if provided>
---
# <title>
<prompt content>
Confirm to user: "Saved: <vaultPath>/Claude-Prompts/<title>.md"
/obsidian list [--search <keyword>]List all saved prompts from your vault.
Steps to execute:
Read config:
Use Read tool on config.json to get vaultPath.
If vaultPath is empty, ask user to run /obsidian setup first.
Find prompts:
Use Glob tool: <vaultPath>/Claude-Prompts/**/*.md
If --search provided: Use Grep tool to filter files containing the keyword.
For each file found: Use Read tool to extract:
Display formatted list:
Found X prompt(s):
<Title 1>
Path: <relative-path>
Preview: <first 60 chars>...
<Title 2>
...
/obsidian use "<prompt-name>"Load and execute a saved prompt.
Steps to execute:
Read config:
Use Read tool on config.json to get vaultPath.
If vaultPath is empty, ask user to run /obsidian setup first.
Find the prompt:
Use Glob tool: <vaultPath>/Claude-Prompts/**/*.md
Match filename or title (case-insensitive) to <prompt-name>.
If not found: List available prompts and ask user to choose.
Read prompt file: Use Read tool to get file contents.
Extract content:
Remove YAML frontmatter (everything between --- markers).
Remove the title header line (starts with # ).
Execute the prompt: Treat the extracted content as if the user typed it. Respond to it as a new instruction.
User: /obsidian setup ~/Documents/MyVault
Claude: Let me configure your Obsidian vault...
[Uses Bash to verify path exists]
[Uses Bash to create Claude-Prompts folder]
[Uses Write to save config.json]
Vault configured: /Users/you/Documents/MyVault
Prompts folder: /Users/you/Documents/MyVault/Claude-Prompts
User: /obsidian save "Code Review Checklist" --tags review,quality
Claude: What content should I save for this prompt?
User: Review this code for: 1) bugs 2) performance 3) security
Claude: [Uses Write to create the markdown file]
Saved: /Users/you/Documents/MyVault/Claude-Prompts/Code Review Checklist.md
User: /obsidian list
Claude: [Uses Glob to find .md files]
[Uses Read to extract titles and previews]
Found 3 prompt(s):
Code Review Checklist
Path: Code Review Checklist.md
Preview: Review this code for: 1) bugs 2) performance...
Debug Helper
Path: Debug Helper.md
Preview: Help me debug this issue by...
User: /obsidian use "Code Review Checklist"
Claude: [Uses Glob to find the file]
[Uses Read to get contents]
[Extracts content, removing frontmatter]
Now executing prompt: "Review this code for: 1) bugs 2) performance 3) security"
[Claude then responds as if user typed that prompt]
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.