One-click install
npx skills add https://github.com/akillness/jeo-skills --skill obsidian-akillness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian
Source: https://github.com/akillness/jeo-skills/tree/main/.agent-skills/obsidian
Command: npx skills add https://github.com/akillness/jeo-skills --skill obsidian-akillness

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill unifies Obsidian plugin development and desktop automation, reducing repetitive setup, validation, and manual tasks by providing boilerplate tooling, ESLint enforcement, and CLI-driven workflows.

Core Features & Use Cases

  • Plugin development boilerplate: generate clean plugin scaffolds ready for submission.
  • ESLint validation with Obsidian-specific rules to ensure code quality and accessibility.
  • CLI automation for desktop Obsidian: vault targeting, search, read, daily notes, plugin reload, and URI handoffs.
  • Markdown patterns, Obsidian Bases, and JSON Canvas patterns to structure knowledge graphs.
  • Use Case: a plugin author quickly scaffolds a new plugin, runs lint, tests, and validates URI handoffs in developer mode.

Quick Start

Install the skill and start the boilerplate workflow to scaffold a plugin and begin CLI automation with Obsidian.

Frequently Asked Questions about obsidian

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

FAQPage Schema
How do I scaffold an Obsidian plugin and automate vault tasks from the CLI?

You can scaffold an Obsidian plugin by generating clean boilerplate ready for submission, and automate desktop vault tasks using CLI commands for targeting, search, daily notes, and plugin reload. This provides an end-to-end development loop.

What ESLint rules do I need for Obsidian plugin development?

Obsidian plugin development requires ESLint validation with 27 specific rules to ensure code quality and accessibility. This structured enforcement reduces repetitive validation tasks and maintains security standards across your plugin codebase.

Does Obsidian URI automation work for desktop power users without manual handoffs?

Yes, Obsidian URI handoffs are fully automated via CLI commands. You can trigger vault operations, search, read files, and manage daily notes programmatically using obsidian:// URIs without manual intervention.

Can I use Node.js and TypeScript for Obsidian vault management and plugin validation?

Yes, the tooling stack relies on Node.js and TypeScript to execute scripts, validate code with 27 ESLint rules, and interact with Obsidian via CLI and obsidian:// URIs. This enables full automation of vault management and plugin validation workflows.

What's the best way to structure markdown patterns and JSON Canvas in an Obsidian vault?

Use content-pattern tooling to structure markdown patterns, Obsidian Bases, and JSON Canvas patterns within your knowledge graph. This approach organizes vault content systematically and supports structured frontmatter metadata for security and quality.

Why does my Obsidian plugin boilerplate need frontmatter metadata and optional directories?

Frontmatter metadata enforces security and quality standards, while optional directories support scripts, references, and assets organization. This structured approach ensures your plugin scaffold meets submission requirements and maintains code quality.