ReddRadar
Agent skill
obsidian-knowledge
{{customDescription}}
Install this agent skill to your Project
npx add-skill https://github.com/pandazki/pneuma-skills/tree/main/plugins/obsidian-memory/skill
SKILL.md
Obsidian 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}}
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
pandazki/pneuma-skills
pneuma-illustrate
Pneuma Illustrate Mode workspace guidelines. Use for ANY task in this workspace: generating images, creating illustrations, editing visuals, managing content sets, organizing rows, crafting prompts, adjusting styles, or any image generation task. This skill defines the generation workflow, manifest format, prompt engineering, and content set organization for the AI illustration studio. Consult before your first edit in a new conversation.
pandazki/pneuma-skills
pneuma-preferences
Persistent user preference memory across sessions. Consult this skill BEFORE making any design, style, or aesthetic decisions — choosing colors, themes, layouts, fonts, tone of voice, content density, or visual direction. Also consult when starting a new creative task in any mode, when the user corrects your style choices, or when asked to analyze or refresh user preferences. Even if you think you know what to do, check preferences first — the user may have recorded specific constraints.
pandazki/pneuma-skills
pneuma-webcraft
Pneuma WebCraft Mode workspace guidelines with Impeccable.style design intelligence. Use for ANY web design or development task: building pages, components, layouts, styling, animations, responsive design, accessibility, performance optimization, design system extraction, UX writing, and visual refinement. This skill defines how the live-preview environment works, the Impeccable design principles to follow, and the 20 design commands available. Consult before your first edit in a new conversation.
pandazki/pneuma-skills
skill
pandazki/pneuma-skills
pneuma-doc
Pneuma Doc Mode workspace guidelines. Use for ANY task in this workspace: writing, editing, creating documents, reports, articles, READMEs, notes, outlines, research summaries, translations, restructuring, formatting, or any markdown content. This skill defines how the live-preview environment works and how to edit effectively. Consult before your first edit in a new conversation.
pandazki/pneuma-skills
pneuma-{{modeName}}
TODO: Describe what this mode's agent does and when it should activate. Example: "Expert at creating and editing [content type] in Pneuma {{displayName}} Mode. Works in a WYSIWYG environment where the user sees edits live in a browser preview panel."
Didn't find tool you were looking for?