By JSai23
Obsidian vault management: PARA filing, semantic search, backlinks, tags, inbox processing
Use this agent for processing inbox, filing notes, organizing the vault, updating living docs, maintaining backlinks and tags, and running audit passes. The organizer that turns raw captures into structured knowledge.
Use this agent for thinking through problems, exploring what your notes say, discussing where projects stand, and synthesizing across areas. A research partner that reads your vault and thinks with you. Writes synthesis to inbox.
Use this agent for interactive writing sessions. Drafts notes from conversation, encodes filing intent for the librarian, writes to inbox only. A transcription partner that captures your thinking well.
This skill should be used when the user asks to "process inbox", "auto process", "file this note", "triage inbox", "route this to the right place", or needs to automatically move notes from 0-Inbox to their correct PARA destination.
This skill should be used when the user asks to "add backlinks", "find related notes", "what should this link to", "update backlinks", "suggest connections", or needs to find appropriate wikilinks for a note.
This skill should be used when the user asks to "find connections", "what relates to this", "how does this connect", "map connections", "show related work", or needs to discover relationships across the vault.
This skill should be used when the user asks about "living documents", "living doc", "update MOC", "MOC maintenance", "how do MOCs work", "keep docs updated", "project brief", or needs to understand or apply the living document pattern.
This skill should be used when the user asks to "search notes", "find similar notes", "semantic search", "reindex vault", "rebuild index", "query vault", or needs to find notes by meaning rather than keywords.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Stop vibe-coding. Ship with structure.
Plugins that make Claude Code follow a real development process.
No frameworks. No dependencies. No bloat. Just markdown files that work.
You: "Build me an auth system"
Claude: *writes 500 lines*
Claude: "Done! Here's your auth system."
You: *tests it*
You: "This doesn't actually validate tokens."
Claude: "Oh right, let me fix that..."
Claude: *writes 200 more lines that break something else*
LLMs skip steps. They write code that looks right but doesn't work. They forget what they were doing between sessions.
Every AI coding tool adds more features, more complexity, more noise. This goes the other way: simple markdown files that enforce discipline.
Most AI tools just generate. This one asks.
┌─────────────────────────────────────────────────────────────────────────┐
│ │
│ TYPICAL AI THIS WORKFLOW │
│ │
│ You: "Build auth" You: "Build auth" │
│ │ │ │
│ ▼ ▼ │
│ AI: *generates 500 lines* AI: "JWT or session-based? │
│ │ What's the token lifetime? │
│ ▼ Refresh token strategy?" │
│ You: "This is wrong" │ │
│ │ ▼ │
│ ▼ You: *answers* │
│ AI: *generates 300 more* │ │
│ │ ▼ │
│ ▼ AI: *builds exactly that* │
│ You: "Still wrong" │ │
│ │ ▼ │
│ ▼ AI: "I built X, Y, Z. │
│ *repeat until frustrated* Is that what you meant?" │
│ │ │
│ ▼ │
│ You: "Yes" or "No, actually..." │
│ │ │
│ ▼ │
│ *catches drift before it compounds*│
│ │
└─────────────────────────────────────────────────────────────────────────┘
Questions appear at every phase:
LLMs are confident. Confident and wrong. Questions force verification before the wrong code compounds into a mess.
┌────────────────────────────────────────────────────────────────────┐
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ PLAN │───▶│ BUILD │───▶│ VERIFY │───▶│ AUDIT │ │
│ └─────────┘ └─────────┘ └─────────┘ └─────────┘ │
│ │ │ │
│ │ ┌─────────┐ │ │
│ └─────────────▶│ FIX │◀───────────────────┘ │
│ └─────────┘ │
│ │
└────────────────────────────────────────────────────────────────────┘
Plan before you code. Track deviations. Audit for fake code. Fix systematically.
git clone https://github.com/jsai/claude-tooling.git
cd claude-tooling && ./install.sh
npx claudepluginhub jsai23/claude-tooling --plugin vaultCreate and edit Obsidian vault files including Markdown, Bases, and Canvas. Use when working with .md, .base, or .canvas files in an Obsidian vault.
Obsidian CLI operations - vault management, search, properties, tasks, plugins, publish, and sync
Persistent Obsidian-based memory for coding agents. Automatically orients from a knowledge vault at session start, navigates project architecture via graph traversal, and writes discoveries back to the vault.
Manage an Obsidian vault as your development knowledge base and automatic work journal. Auto-captures commits, tasks, and Claude Code components with structured frontmatter.
Interact with Obsidian vaults using the official Obsidian CLI (v1.12+). Read, create, append, search, and manage notes, daily notes, properties, tags, tasks, bookmarks, templates, themes, sync, plugins, and links — all from the terminal.
Bidirectional knowledge flow between Claude Code and Obsidian — 20 MCP tools, skills, and hooks for PKM