obsidian-plugin-development

Enforce Obsidian plugin coding standards and automated review rules for TypeScript.

6|2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/acaprino/anvil-toolset --skill obsidian-plugin-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-plugin-development
Source: https://github.com/acaprino/anvil-toolset/tree/main/plugins/obsidian-development/skills/obsidian-plugin-development
Command: npx skills add https://github.com/acaprino/anvil-toolset --skill obsidian-plugin-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers write Obsidian community plugins that adhere to strict coding standards and automated review checks, preventing common errors and ensuring a smooth submission process.

Core Features & Use Cases

  • Enforces Coding Standards: Ensures compliance with Obsidian's official guidelines, eslint-plugin-obsidianmd rules, and automated checks.
  • Prevents Common Errors: Catches issues like incorrect UI text casing, inline styles, unhandled promises, and improper DOM manipulation.
  • Use Case: When developing a new feature for your Obsidian plugin, use this Skill to proactively identify and fix potential violations before submitting a pull request to the Obsidian community plugins repository.

Quick Start

Use the obsidian-plugin-development skill to review the attached TypeScript file for compliance with Obsidian's plugin guidelines.

Frequently Asked Questions about obsidian-plugin-development

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

FAQPage Schema
How do I write an Obsidian plugin that passes the community review?

Obsidian plugin development requires adherence to official guidelines and automated review rules from eslint-plugin-obsidianmd and ObsidianReviewBot. This skill proactively checks your TypeScript code for compliance before submission.

What common errors cause Obsidian plugins to fail automated review?

Obsidian plugin reviews frequently fail due to incorrect UI text casing, inline styles, unhandled promises, and improper DOM manipulation. This skill identifies and helps fix these specific violations to ensure a smooth submission process.

Can I use this skill to check TypeScript files for ObsidianReviewBot compliance?

Yes, you can use this skill to review attached TypeScript files for compliance with ObsidianReviewBot standards. It enforces official Obsidian plugin guidelines and automated review rules across your TypeScript codebase.

Do I need eslint-plugin-obsidianmd to develop Obsidian community plugins?

Using eslint-plugin-obsidianmd is critical for developing Obsidian community plugins as it provides the automated review rules required for submission. This skill ensures your code adheres to these specific eslint standards.

What's the best way to ensure my Obsidian plugin handles promises and DOM manipulation correctly?

The best way to ensure correct promise handling and DOM manipulation in Obsidian plugins is to enforce strict coding standards against official guidelines. This skill catches unhandled promises and improper DOM manipulation before submission.