obsidian

Guide Obsidian.md plugin development with API, UI, and testing standards.

Updated May 1, 2026

Search Tags:#accessibility #security #UI/UX #eslint #plugin development #obsidian #API standards

Ready to run

npx skills add https://github.com/legg/AgentLuhmann --skill obsidian-legg

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: obsidian
Source: https://github.com/legg/AgentLuhmann/tree/main/.tessl/tiles/gapmiss/obsidian-plugin-skill/.agents/skills/obsidian
Command: npx skills add https://github.com/legg/AgentLuhmann --skill obsidian-legg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill provides comprehensive development standards, best practices, and security guidelines for creating robust Obsidian.md plugins, ensuring consistent quality and security compliance.

Core Features & Use Cases

Guideline Reference: Offers detailed instructions on API usage, UI design, accessibility, and code quality standards for Obsidian plugins.
Development Assistance: Supports plugin developers in setting up ESLint, structuring files, and adhering to submission requirements.
Use Case: A developer prepares a new Obsidian plugin, consulting this Skill to ensure their code meets community standards and accessibility requirements before release.

Quick Start

Review the plugin development standards and implement accessible, theme-compatible code in your plugin project.

Frequently Asked Questions about obsidian

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

FAQPage Schema

How do I develop an Obsidian.md plugin that meets community accessibility and security standards?▼

Obsidian.md plugin development requires adhering to API best practices, UI/UX consistency, and robust testing procedures. This Skill provides comprehensive guidelines to ensure your plugin meets community standards for code quality, accessibility, and security compliance before release.

What are the API best practices for Obsidian plugin development?▼

API best practices for Obsidian plugin development involve following standardized API usage, maintaining UI design consistency, and implementing robust testing procedures. This Skill offers detailed instructions to ensure your code adheres to community expectations and submission protocols.

How do I set up ESLint for an Obsidian plugin project?▼

Setting up ESLint for an Obsidian plugin project involves configuring the linter to enforce code quality standards and community submission protocols. This Skill supports developers in structuring files and establishing ESLint to maintain consistent, accessible, and theme-compatible code.

Can I use this Skill to check if my Obsidian plugin meets submission requirements?▼

Yes, this Skill helps verify your Obsidian plugin meets submission requirements by providing detailed development standards and security guidelines. It emphasizes adherence to community standards for code quality, accessibility, and API best practices prior to release.

Why does my Obsidian plugin need to follow UI/UX and accessibility guidelines?▼

Obsidian plugins need UI/UX and accessibility guidelines to ensure consistent quality and theme compatibility across the application. This Skill provides detailed instructions on accessible UI design, ensuring your plugin delivers a standardized experience for all users.

What limitations exist when using community standards for Obsidian plugin development?▼

Community standards for Obsidian plugin development constrain you to specific API usage, accessibility requirements, and security compliance protocols. This Skill outlines these boundaries to ensure your plugin maintains robust testing procedures and code quality without violating submission rules.