kriscard/kriscard-claude-plugins
Overview
This skill handles Obsidian vault operations with a CLI-first approach and an explicit MCP fallback. It covers reading, creating, appending, searching, listing files, daily notes, tasks, tags, links, templates, and vault metadata. Use it whenever you need reliable, scriptable access to an Obsidian vault.
How this skill works
The skill first detects if the Obsidian CLI is available and running; if so, it runs obsidian commands or the shared obsidian-utils.sh script for precise operations. If the CLI is unavailable, it asks the user for permission and then uses MCP tools to perform the same actions. All operations support flags like silent, format=json, inline, overwrite, and permanent to control behavior and output.
When to use it
- Reading note contents or resolving wikilink-style names
- Creating notes, templates, or appending/prepending content
- Searching the vault or listing files/folders programmatically
- Working with daily/periodic notes and automated task handling
- Inspecting tags, backlinks, unresolved links, or vault metadata
Best practices
- Prefer CLI commands when available; they are faster and preserve local context
- Always add silent for non-interactive operations to avoid opening the app
- Use format=json for machine parsing and file= for wikilink-style resolution when path is unknown
- Confirm with the user before using MCP fallback and before destructive actions (delete/permanent)
- Batch operations where possible for efficiency and use template= to create consistent notes
Example use cases
- Read a note by name, falling back to MCP only after confirmation
- Create a TIL note from a template and append a short note to today's daily note silently
- Search the vault for meeting notes and return results as JSON for further processing
- List files in a project folder, then update frontmatter properties across multiple files
- Find unresolved links and generate a report of orphan files for cleanup
FAQ
The skill notifies you CLI is unavailable and asks for permission to use MCP tools before proceeding.
When should I use file= vs path=?
Use file= for wikilink-style resolution when you know the note name but not the exact path; use path= when you know the exact vault-relative path.
13 skills
This skill enables efficient Obsidian vault management by executing CLI operations for reading, creating, appending, searching, and listing notes.
This skill guides you through system design choices, creates ADRs and C4 diagrams, and evaluates trade-offs for scalable architectures.
This skill helps you optimize Claude Code projects by analyzing usage, detecting structure, and surfacing community resources for actionable improvements.
This skill helps you build and maintain a powerful second brain in Obsidian using PARA, progressive summarization, and focused PKM workflows.
This skill acts as a proactive Staff Engineer workflow partner, monitoring activity and nudging actions to maintain focus, quality, and career progress.
This skill helps transform scattered technical notes into polished blog posts by guiding structure, voice, and SEO-ready writing.
This skill helps transform messy brain dumps into structured specifications and actionable PRD and spec artifacts through a guided, confidence-based workflow.
This skill helps you organize and reference your Obsidian vault layout, tagging, and templates for faster, accurate note placement.
This skill helps you build production LLM applications and RAG systems by guiding integration, retrieval, and orchestration decisions.
This skill provides dotfiles best practices and modern CLI tooling guidance to optimize configuration, security, and performance for productive shells.
This skill helps you quickly craft conference talk outlines and iA Presenter slides using the Story Circle framework for engaging, structured presentations.
This skill orchestrates a full startup-to-MVP workflow, guiding strategy, requirements, tech selection, design, and implementation for new projects.
This skill analyzes coding requests and coordinates the best specialist agents to write, debug, or refactor code efficiently.
