obsidian-docs

Locate official Obsidian developer documentation and extract implementation implications.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/frznfrgg/obsidian_sync --skill obsidian-docs-frznfrgg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: obsidian-docs
Source: https://github.com/frznfrgg/obsidian_sync/tree/main/.agents/skills/obsidian-docs
Command: npx skills add https://github.com/frznfrgg/obsidian_sync --skill obsidian-docs-frznfrgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents implementation guesswork by guiding agents to the most up-to-date official Obsidian developer documentation when building or validating plugin behavior.

Core Features & Use Cases

  • Official-docs-first navigation: Locate the correct Obsidian developer docs pages for a specific plugin engineering question.
  • Implementation-relevant extraction: Turn the relevant doc sections into concrete constraints, confirmed API facts, and implications for desktop vs mobile behavior.
  • Release- and manifest-aware guidance: Help verify platform constraints, manifest fields, build/release requirements, and TypeScript API signatures.

Quick Start

Use the obsidian-docs skill to find the official guidance for how to access vault files via the Vault adapter and confirm any constraints for desktop versus Android.

Frequently Asked Questions about obsidian-docs

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

FAQPage Schema
How do I access vault files using the Obsidian vault adapter?

Accessing vault files via the Obsidian vault adapter requires reviewing the official developer documentation to confirm exact API signatures and file management constraints. This ensures correct plugin implementation for reading and writing data.

What are the mobile constraints for Obsidian plugin implementation?

Mobile constraints for Obsidian plugin implementation dictate specific API behaviors differing from desktop. Developers must verify platform constraints and UI wiring rules through official documentation to ensure proper functionality on mobile environments.

How do I handle secret storage and OAuth in an Obsidian plugin?

Handling secret storage and OAuth in an Obsidian plugin requires checking official developer documentation for secure credential management guidelines. This confirms the exact API methods available for authentication flows and secret protection.

What manifest rules are required for Obsidian plugin setup?

Obsidian plugin setup requires adhering to specific manifest rules defining platform constraints and build requirements. Reviewing official developer documentation confirms the exact manifest fields needed for successful plugin validation and release.

Does my Obsidian plugin need different code for desktop vs Android?

Your Obsidian plugin may require different code for desktop vs Android due to platform-specific constraints. Checking official developer documentation confirms API behavior differences and ensures your vault file access and UI wiring function correctly across platforms.

What is the best way to confirm Obsidian API signatures for plugin development?

The best way to confirm Obsidian API signatures for plugin development is by consulting official developer documentation. This provides exact TypeScript API facts and implementation implications needed to validate plugin behavior and avoid guesswork.