obsidian
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.
What this skill does
# Obsidian Prompt Manager
Manage reusable prompts in your Obsidian vault from Claude Code using native tools.
## Configuration
Configuration is stored in the skill's `config.json`:
```json
{
"vaultPath": "/path/to/your/vault",
"promptsFolder": "Claude-Prompts"
}
```
**Config location:** `~/.claude/skills/obsidian/config.json` (personal) or `.claude/skills/obsidian/config.json` (project)
---
## Commands
### `/obsidian setup <vault-path>`
Configure your Obsidian vault path.
**Steps to execute:**
1. **Validate path exists:**
```
Use Bash: ls -la <vault-path>
```
If path doesn't exist, inform user and stop.
2. **Create prompts folder:**
```
Use Bash: mkdir -p <vault-path>/Claude-Prompts
```
3. **Save configuration:**
Use Write tool to update config.json:
```json
{
"vaultPath": "<vault-path>",
"promptsFolder": "Claude-Prompts"
}
```
4. **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:**
1. **Read config:**
Use Read tool on config.json to get vaultPath.
If vaultPath is empty, ask user to run `/obsidian setup` first.
2. **Get prompt content:**
Ask user: "What content should I save for this prompt?"
3. **Create markdown file:**
Use Write tool to create `<vaultPath>/Claude-Prompts/<title>.md`:
```markdown
---
title: "<title>"
date: <YYYY-MM-DD>
tags:
- claude-prompt
- <additional tags if provided>
---
# <title>
<prompt content>
```
4. **Confirm to user:**
"Saved: <vaultPath>/Claude-Prompts/<title>.md"
---
### `/obsidian list [--search <keyword>]`
List all saved prompts from your vault.
**Steps to execute:**
1. **Read config:**
Use Read tool on config.json to get vaultPath.
If vaultPath is empty, ask user to run `/obsidian setup` first.
2. **Find prompts:**
Use Glob tool: `<vaultPath>/Claude-Prompts/**/*.md`
3. **If --search provided:**
Use Grep tool to filter files containing the keyword.
4. **For each file found:**
Use Read tool to extract:
- Title (from frontmatter or filename)
- Preview (first line of content after frontmatter)
5. **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:**
1. **Read config:**
Use Read tool on config.json to get vaultPath.
If vaultPath is empty, ask user to run `/obsidian setup` first.
2. **Find the prompt:**
Use Glob tool: `<vaultPath>/Claude-Prompts/**/*.md`
Match filename or title (case-insensitive) to <prompt-name>.
3. **If not found:**
List available prompts and ask user to choose.
4. **Read prompt file:**
Use Read tool to get file contents.
5. **Extract content:**
Remove YAML frontmatter (everything between `---` markers).
Remove the title header line (starts with `# `).
6. **Execute the prompt:**
Treat the extracted content as if the user typed it.
Respond to it as a new instruction.
---
## Examples
### Setup Example
```
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
```
### Save Example
```
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
```
### List Example
```
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...
```
### Use Example
```
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]
```
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.