# Obsidian Deploy Integration

> Publish Obsidian plugins to the community plugin directory. Use when releasing your first plugin, updating existing plugins, or managing the community plugin submission process. Trigger with phrases like "publish obsidian plugin", "obsidian community plugins", "submit obsidian plugin", "obsidian plugin directory".

- Skill: `micsapp/obsidian-deploy-integration` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add micsapp/obsidian-deploy-integration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/micsapp/obsidian-deploy-integration/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- License: MIT
- Author: micsapp (https://skillmd.com/u/micsapp)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/micsapp/obsidian-deploy-integration

---

# Obsidian Plugin Deploy Integration

## Overview
Publish and distribute Obsidian plugins through the official community plugin directory. Covers the complete release workflow: building, versioning, creating GitHub releases, and submitting to the Obsidian community plugins repository for review and listing.

## Prerequisites
- Obsidian plugin with `main.ts`, `manifest.json`, and `styles.css` (if applicable)
- GitHub repository for your plugin
- Node.js build toolchain (esbuild recommended)
- Understanding of Obsidian plugin review requirements

## Instructions

### Step 1: Configure Build Pipeline

### Step 2: Version and Release Files

### Step 3: GitHub Release Workflow

### Step 4: Submit to Community Plugins

### Step 5: Version Bump Script

For full implementation details and code examples, load:
`references/implementation-guide.md`

## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Plugin not loading | Wrong manifest ID | Ensure `id` matches directory name |
| Build fails | Missing externals | Add `obsidian` to esbuild externals |
| Review rejected | Guidelines violation | Review obsidian.md/plugins/guidelines |
| Version mismatch | versions.json outdated | Run version-bump script before release |

## Resources
- [Obsidian Plugin Guidelines](https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines)
- [Sample Plugin Template](https://github.com/obsidianmd/obsidian-sample-plugin)
- [Community Plugins Repo](https://github.com/obsidianmd/obsidian-releases)

## Next Steps
For event handling, see `obsidian-webhooks-events`.

## Output

- Configuration files or code changes applied to the project
- Validation report confirming correct implementation
- Summary of changes made and their rationale

See [deployment implementation details](${CLAUDE_SKILL_DIR}/references/implementation.md) for output format specifications.

## Examples

**Basic usage**: Apply obsidian deploy integration to a standard project setup with default configuration options.

**Advanced scenario**: Customize obsidian deploy integration for production environments with multiple constraints and team-specific requirements.