---
title: "obsidian-plugin-skill"
description: "Unofficial agent skills for scaffolding, building, verifying, reviewing, and shipping Obsidian community plugins. Not affiliated with Obsidian."
canonical: https://agentpluginsdirectory.com/plugins/obsidian-plugin-skill
last-updated: 2026-10-11
---

# obsidian-plugin-skill
Unofficial agent skills for scaffolding, building, verifying, reviewing, and shipping Obsidian community plugins. Not affiliated with Obsidian.
- Slug: obsidian-plugin-skill
- Publisher: Justin Wong
- Repository: https://github.com/justinw0ng/obsidian-plugin-skill
- Manifest: plugin.json
- Version: 1.0.0
- License: Apache-2.0
- Category (editorial): agent-tooling
- Skills: 6 (obsidian-plugin-architecture, obsidian-plugin-scaffold, obsidian-plugin-ship, obsidian-plugin-ui, obsidian-plugin-verify, obsidian-plugin)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-08-26
- Repository last pushed: 2026-08-26
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/obsidian-plugin-skill
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What obsidian-plugin-skill does, in the publisher's words

Unofficial agent skills for scaffolding, building, verifying, reviewing, and shipping Obsidian community plugins. Not affiliated with, published by, or endorsed by Obsidian or Dynalist Inc.

Playbook for TypeScript community plugins: vault-as-data, createEl UI, Selenium against real Obsidian, review-ban unit tests, and GitHub Releases the community directory can install.

Official docs stay canonical for APIs and listing rules: Build a plugin, Plugin guidelines. Each skill owns one phase. The hub only routes and lists hard stops. Do not copy phase how-to into a second skill.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/justinw0ng/obsidian-plugin-skill/HEAD/README.md

## Skills

- obsidian-plugin-architecture: Architecture for Obsidian plugins: pure core vs Vault adapter, vault-as-data, codeblocks, path safety, caching, and mobile/minAppVersion. Use when designing plugin structure, choosing where logic lives, or /obsidian-plugin-architecture.
- obsidian-plugin-scaffold: Bootstrap a new Obsidian community plugin from the sample plugin or a proven layout. Use when creating a new plugin repo, renaming the sample plugin, wiring esbuild/manifest/scripts, or /obsidian-plugin-scaffold.
- obsidian-plugin-ship: Ship an Obsidian community plugin: semver lockstep, GitHub Release assets (no v-prefix tags), community directory submission, and review-failure re-release. Use when releasing, bumping versions, fixing directory review, or /obsidian-plugin-ship.
- obsidian-plugin-ui: Obsidian plugin UI conventions: createEl DOM, data-testid hooks, settings sentence case, CSS variables, command callbacks, and community-review bans for HTML/CSS. Use when building settings tabs, views, codeblock renderers, or /obsidian-plugin-ui.
- obsidian-plugin-verify: Verify an Obsidian plugin with Node unit tests, typecheck, production build, and Selenium E2E against real Obsidian. Use for test:e2e harnesses, Cloud VM Obsidian install, data-testid health checks, or /obsidian-plugin-verify.
- obsidian-plugin: End-to-end playbook for building an Obsidian community plugin. Use when scaffolding, implementing, verifying, reviewing, or shipping any Obsidian plugin; for vault-as-markdown architecture, Selenium E2E, plugin-review lint, GitHub releases, community directory submission, or /obsidian-plugin.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.