Obsidian Knowledge Agent Skill
> {{customDescription}}
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/pandazki/pneuma-skills --skill obsidian-knowledgeThe instruction itself
4 sections, as written by the authorObsidian Knowledge Base
Every session starts from zero context. But the user has been thinking about these topics for weeks, months, sometimes years — and that thinking lives in their Obsidian vault. Notes, bookmarks, project docs, design decisions, research findings. When you search the vault before starting work, you're not just gathering information — you're respecting the context the user has already built, and producing output that fits into their existing mental model rather than a generic one.
The difference between good and great output is often grounding: the same presentation about "AI agent sandboxes" is dramatically better when it references the specific project the user bookmarked last month, uses their terminology, and connects to their existing knowledge graph.
When to Search
Search when the answer might already exist in the user's own words:
- Starting a new creative task — the user says "make a deck about X" or "write a doc about Y". Before planning, search for X or Y. Even a single related note changes your approach.
- A specific name appears — project names, tool names, people, concepts. If the user mentions "sandbox" or "better-auth" or any proper noun, search it. They bookmarked it for a reason.
- "Look up" / "check" / "find" / "reference" — the user is explicitly asking you to search. Their vault first, web second.
- You're about to use general knowledge — pause and consider: does the user have their own take on this? A quick search costs nothing; missing their existing notes costs relevance.
When a search returns nothing, that's fine — proceed with your own knowledge. The point is to check, not to force-find.
API
All endpoints use the Pneuma server's base URL.
Search — find notes by keyword:
POST /api/plugins/obsidian-memory/search
Body: { "query": "search terms", "limit": 5 }
→ { results: [{ entry: { path, title }, score, snippet }] }
Read — get full content of a note:
GET /api/plugins/obsidian-memory/read/{path}
→ { entry: { path, title, content } }
Write — create or update a note (only when user asks):
POST /api/plugins/obsidian-memory/write
Body: { "path": "folder/file.md", "content": "...", "tags": ["..."] }
Status — check availability (call once per session):
GET /api/plugins/obsidian-memory/status
→ { available: true/false }
Patterns
Search → Read: Search returns paths and snippets. If a snippet looks relevant, read the full note. One search + one read is the typical flow.
Cite casually: "I found a note in your vault about X" — not formally, not with full paths.
Don't over-search: One or two searches per topic. No results = the user doesn't have notes on this, move on.
Write sparingly: Only when the user explicitly asks to save something to their vault.
{{customGuidance}}
Other skills for the same job
different authors, same section of the catalogue
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks
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.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
How to use it
Take pandazki/obsidian-knowledge from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.