plugins/obsidian-agent-tools/skills/obsidian-automation/SKILL.md
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.
npx skillsauth add tavva/ben-claude-plugins obsidian-automationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
The obsidian CLI controls a running Obsidian instance from the terminal. Anything you can do in Obsidian you can do from the command line.
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.
Commands use parameter=value pairs and boolean flags:
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.
The CLI covers the full Obsidian feature set:
Use these tools without being asked when:
# 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
# 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"
# Vault info
obsidian vault
# List files
obsidian files ext=md
# Check properties
obsidian properties file=MyNote
# View workspace layout
obsidian workspace
tools
This skill should be used when the user asks to "create a sprite", "run in sprite", "execute in sprite", "sprite exec", "open sprite console", "list sprites", "destroy sprite", "create checkpoint", "restore checkpoint", "proxy through sprite", or mentions Sprite, isolated environments, or persistent microVMs. Also triggers on requests to manage sprite authentication, checkpoints, or port forwarding.
tools
This skill should be used when working on frontend code, debugging UI issues, verifying visual changes, scraping web pages, testing web features, or inspecting page state. Also triggers on "open browser", "take screenshot", "navigate to URL", "scrape website", "extract page content", "check accessibility", or any web automation task. Use proactively during frontend development to verify changes visually.
tools
This skill should be used when the user asks to "send an email", "send email via Resend", "list emails", "check email status", "cancel scheduled email", "manage domains", "add domain", "verify domain DNS", "create API key", "list API keys", "manage templates", "create email template", or mentions Resend, transactional email, or email delivery. Also triggers on requests to configure Resend, check domain verification, or manage email infrastructure.
documentation
This skill should be used when the user asks to "create a README", "write a README", "generate a README", "improve my README", "make my README better", "README best practices", or mentions needing project documentation. Provides guidance for creating excellent READMEs following patterns from awesome-readme.