obsidian-automation
This skill should be used when working on Obsidian plugins, testing plugin changes, verifying plugin UI, debugging plugin behaviour, or running automated tests against Obsidian. Also triggers on "start Obsidian", "take Obsidian screenshot", "test plugin", "run plugin command", "execute in Obsidian", or any Obsidian automation task. Use proactively during plugin development to verify changes visually.
What this skill does
# Obsidian CLI The `obsidian` CLI controls a running Obsidian instance from the terminal. Anything you can do in Obsidian you can do from the command line. ## Prerequisites - Obsidian 1.12+ must be running - CLI registered via Settings → General → Command line interface ## Getting Help ```bash obsidian help # List all commands obsidian help <command> # Detailed help for a command ``` Always check `obsidian help <command>` for the full parameter list before using a command you haven't used before. ## Command Syntax Commands use `parameter=value` pairs and boolean flags: ```bash obsidian command parameter=value flag ``` Target a specific vault with `vault=name` as the first parameter. Target files with `file=name` (wikilink resolution) or `path=exact/path`. Use `--copy` on any command to copy output to clipboard. ## Capabilities The CLI covers the full Obsidian feature set: - **Files** — create, read, open, append, prepend, move, rename, delete - **Search** — full-text search with context, scoped to folders - **Daily notes** — open, read, append, prepend - **Properties** — read, set, remove frontmatter properties - **Tasks** — list, filter, toggle task status - **Links** — backlinks, outgoing links, orphans, unresolved links - **Tags** — list, filter, count - **Plugins** — list, enable, disable, install, uninstall, reload - **Commands** — list and execute any registered command - **Developer** — screenshots, JS eval, DOM inspection, console logs, CDP ## Proactive Use **Use these tools without being asked when:** - Implementing or modifying Obsidian plugin features — take screenshots to verify UI changes - Debugging plugin behaviour — execute commands and inspect state - Testing plugin with different vault configurations - Verifying that plugin changes work as expected ## Common Workflows ### Plugin Development ```bash # Reload plugin after code changes obsidian plugin:reload id=my-plugin # Take a screenshot to verify UI obsidian dev:screenshot # Execute a plugin command obsidian command id=my-plugin:do-something # List all commands from your plugin obsidian commands filter=my-plugin # Evaluate JS in Obsidian context obsidian eval code="app.plugins.plugins['my-plugin'].settings" # Check console for errors obsidian dev:errors obsidian dev:console level=error ``` ### File Operations ```bash # Read a file obsidian read file=MyNote # Create a file with content obsidian create name=Test path=folder/Test.md content="Hello world" # Search the vault obsidian search query="TODO" path=Projects obsidian search:context query="function.*export" # Append to daily note obsidian daily:append content="- Task from CLI" ``` ### Inspecting State ```bash # Vault info obsidian vault # List files obsidian files ext=md # Check properties obsidian properties file=MyNote # View workspace layout obsidian workspace ```
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.