obsidian-plugin

Scaffold, validate, and package Obsidian plugins with TypeScript and manifest checks.

40|9|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/akillness/jeo-skills --skill obsidian-plugin-akillness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-plugin
Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/obsidian-plugin
Command: npx skills add https://github.com/akillness/jeo-skills --skill obsidian-plugin-akillness

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Merges and centralizes Obsidian plugin development so teams can scaffold, validate, and publish plugins with consistent quality and governance.

Core Features & Use Cases

  • Boilerplate generation for Obsidian plugins, including manifest, TS sources, and build config.
  • ESLint-based validation, accessibility checks, and submission readiness guidance.
  • Redirects to the main obsidian skill for ongoing plugin development best practices.

Quick Start

Run the boilerplate generator to scaffold a new Obsidian plugin project and validate its readiness.

Frequently Asked Questions about obsidian-plugin

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

FAQPage Schema
How do I scaffold an Obsidian plugin with TypeScript and a valid manifest?

To scaffold an Obsidian plugin, you generate a boilerplate skeleton including TypeScript sources, manifest, and build configuration. This ensures your project meets Obsidian's standards-compliant structure from the start.

What checks are needed for Obsidian plugin submission readiness?

Obsidian plugin submission readiness requires passing ESLint validation, manifest metadata checks, and accessibility guideline reviews. The process enforces these checks to ensure your plugin meets community submission standards.

Can I validate my Obsidian plugin manifest and metadata before publishing?

Yes, you can validate your Obsidian plugin manifest and metadata before publishing. The validation process enforces manifest checks to ensure your plugin's metadata is standards-compliant prior to community submission.

What is the best way to manage memory and accessibility in Obsidian plugin development?

The best way to manage memory and accessibility in Obsidian plugin development is by following specific memory-management and accessibility guidelines. These references are provided to ensure standards-compliant plugin behavior.

Does the Obsidian plugin boilerplate include ESLint configuration?

Yes, the Obsidian plugin boilerplate includes ESLint configuration. It provides ESLint-based validation alongside the TypeScript-based plugin skeleton to enforce code quality and submission readiness.