obsidian

Review Obsidian plugin code against ESLint, TypeScript, and API guidelines.

1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/POWERFULMOVES/PMOVES-BoTZ --skill obsidian-powerfulmoves
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian
Source: https://github.com/POWERFULMOVES/PMOVES-BoTZ/tree/main/.claude/skills/obsidian
Command: npx skills add https://github.com/POWERFULMOVES/PMOVES-BoTZ --skill obsidian-powerfulmoves

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidelines and best practices for developing robust, user-friendly, and accessible Obsidian plugins, ensuring adherence to official standards and preventing common pitfalls.

Core Features & Use Cases

  • Plugin Development Standards: Covers ESLint rules, TypeScript best practices, memory management, and API usage.
  • UI/UX & Accessibility: Ensures plugins are intuitive, consistent, and accessible to all users.
  • Submission Readiness: Guides users through requirements for publishing plugins to the community directory.
  • Use Case: A developer is building a new Obsidian plugin and needs to ensure their code follows Obsidian's official guidelines for memory safety, type checking, and UI consistency before submission.

Quick Start

Review the top 27 most critical rules for Obsidian plugin development.

Frequently Asked Questions about obsidian

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

FAQPage Schema
What are the best practices for Obsidian plugin development?

Obsidian plugin development best practices include following ESLint rules, applying TypeScript standards, managing memory properly, and using the official API for vault operations and MarkdownView to ensure robust, accessible plugins.

How do I prepare an Obsidian plugin for community directory submission?

To prepare an Obsidian plugin for submission, ensure your manifest.json and main.ts files adhere to official guidelines, passing TypeScript type checking, memory safety rules, and UI consistency standards before publishing to the community directory.

Why does my Obsidian plugin fail TypeScript type checking?

Obsidian plugins fail TypeScript type checking when code deviates from official API usage standards. Following TypeScript best practices and proper API guidelines for the Plugin class and TFile operations ensures type safety and prevents common errors.

How do I manage memory in an Obsidian plugin?

Manage memory in an Obsidian plugin by adhering to official memory management guidelines, properly cleaning up resources and references within the Plugin class to prevent memory leaks during vault operations and MarkdownView interactions.

Can I use standard ESLint rules for Obsidian plugin development?

Obsidian plugin development requires specific ESLint rules tailored to the platform. Applying the official ESLint guidelines ensures your TypeScript code meets accessibility, UI/UX, and API usage standards required for directory submission.