skills.rest
tavva
tavvaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

obsidian-automation

Launch and control CDP-enabled Obsidian test instances to validate plugin UI.

Updated Dec 15, 2025
Search Tags:#automation#testing#ui#obsidian#cdp#automate
One-click install
npx skills add https://github.com/tavva/ben-claude-plugins --skill obsidian-automation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: obsidian-automation
Source: https://github.com/tavva/ben-claude-plugins/tree/main/plugins/obsidian-agent-tools/skills/obsidian-automation
Command: npx skills add https://github.com/tavva/ben-claude-plugins --skill obsidian-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Obsidian plugin development often requires manual UI testing and state verification across vault configurations. This skill provides automated, CDP-enabled test instances to validate plugin behavior and UI changes without disrupting user data.

Core Features & Use Cases

  • Proactive UI verification: launch isolated Obsidian instances with CDP for automated UI checks.
  • End-to-end plugin testing: validate plugin commands, UI states, and vault configurations through scripted flows.
  • Regression and QA workflows: integrate into development pipelines to ensure consistent behavior across changes.

Quick Start

Start an isolated Obsidian test instance and run automated UI tests to verify plugin changes.

Frequently Asked Questions about obsidian-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Can I run automated UI checks across different Obsidian vault configurations?▼

Automate Obsidian plugin UI testing by launching isolated Obsidian test instances with CDP-enabled automation to validate plugin behavior and UI changes without disrupting user data.

What's the best way to validate Obsidian plugin commands without breaking my notes?▼

You can run automated UI checks across varying vault configurations by launching isolated test instances with CDP to validate plugin commands and vault state through scripted flows.

How does CDP automation work for Obsidian regression testing?▼

The best way to validate plugin commands without breaking notes is using isolated CDP-enabled test instances to inspect Obsidian state and run scripted validation flows.

Do I need specific test scripts to automate Obsidian UI checks?▼

CDP automation works for regression testing by starting, stopping, screenshotting, and inspecting isolated Obsidian instances to ensure consistent plugin behavior across development changes.

How do I integrate Obsidian plugin QA workflows into a development pipeline?▼

You need the plugin's test scripts and CDP tooling to automate Obsidian UI checks, which start, stop, screenshot, and inspect test instances for proactive development verification.

Why does my Obsidian plugin behave differently across vaults?▼

Integrate Obsidian plugin QA workflows into development pipelines by running CDP-enabled automated test instances to validate UI states and plugin commands across changes.

Related Skills

Explore More Software Engineering Skills→
tense-itense-i
1

browser

Control Chrome via CDP to navigate, evaluate scripts, and capture screenshots.

Community
Intermediate
jikig-aijikig-ai
12

reproduce-bug

Reproduce GitHub-reported bugs via logs, code inspection, and Playwright.

Official
Intermediate
pipecrew-aipipecrew-ai
16

simulate-run

Generate a demo workspace with plugin schema artifacts for testing.

Community
Intermediate
roach88roach88
2

browser

Automate Chrome via Chrome DevTools Protocol without extensions or MCP tooling.

Community
Intermediate