Agent skill

Obsidian Deploy Integration

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Publish Obsidian plugins to the community plugin directory. An agent skill from jeremylongshore/tons-of-skills-marketplace.

MITAuto-check passed

Install Obsidian Deploy Integration

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-deploy-integration --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/obsidian-deploy-integration .claude/skills/obsidian-deploy-integration && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
obsidian-deploy-integration
GitHub stars
2.8k
Token cost
~2.1k tokens
SKILL.md length
458 words
Files
3 (incl. references)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Publish Obsidian plugins to the community plugin directory. An agent skill from jeremylongshore/tons-of-skills-marketplace.

  • Works in 6 steps: Build Release Assets → Version Bump with version-bump.mjs → Create GitHub Release → …
  • Releasing your first plugin
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 4 more sections
  • Calls gh, npm and git; reaches github.com

What it does

Obsidian Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. 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".

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/implementation-guide.md` and `references/implementation.md`). Compatibility notes: Designed for Claude Code

It works with Obsidian and GitHub. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Releasing your first plugin
  • Updating existing plugins
  • Managing the community plugin submission process
  • With phrases like publish obsidian plugin

Example prompts

  • “publish obsidian plugin”
  • “obsidian community plugins”
  • “submit obsidian plugin”
  • “/obsidian-deploy-integration”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(git:*), Bash(gh:*)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Build Release Assets
  2. Version Bump with version-bump.mjs
  3. Create GitHub Release
  4. Submit to Community Plugins
  5. BRAT for Beta Testing
  6. Manual Installation

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash(git:*)
    • Bash(gh:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh
    • npm
    • git
    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    Also links to:

    • docs.obsidian.md

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Obsidian Deploy Integration loads about 2.1k tokens when it runs, and up to ~4.3k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 458 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~2.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 458 words, ~2,131 tokens.

Download SKILL.mdSave it as .claude/skills/obsidian-deploy-integration/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
obsidian-deploy-integration
description
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".
allowed-tools
Read, Write, Edit, Bash(git:*), Bash(gh:*)
compatibility
Designed for Claude Code
version
1.13.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
saas, obsidian, obsidian-deploy

Obsidian Plugin Deploy Integration

Overview

Release and distribute Obsidian plugins through multiple channels: the official community plugin directory, GitHub releases, BRAT beta testing, and manual installation. Covers the full lifecycle from building release assets to submitting your PR to the obsidian-releases repo.

Prerequisites

  • Obsidian plugin with main.ts, manifest.json, and styles.css (if applicable)
  • GitHub repository for your plugin (public)
  • gh CLI authenticated (gh auth status)
  • Plugin passes obsidian-prod-checklist validation

Instructions

Step 1: Build Release Assets
bash
set -euo pipefail
# Clean build for production
rm -f main.js
npm ci
npm run build

# Verify the three release files exist
for f in main.js manifest.json; do
  test -f "$f" || { echo "MISSING: $f"; exit 1; }
done
test -f styles.css && echo "styles.css included" || echo "No styles.css (OK if no custom styles)"

echo "Release assets ready"
Step 2: Version Bump with version-bump.mjs
javascript
// version-bump.mjs
import { readFileSync, writeFileSync } from 'fs';

const targetVersion = process.env.npm_package_version;

// Sync manifest.json
const manifest = JSON.parse(readFileSync('manifest.json', 'utf8'));
const { minAppVersion } = manifest;
manifest.version = targetVersion;
writeFileSync('manifest.json', JSON.stringify(manifest, null, '\t'));

// Sync versions.json — maps each plugin version to its minimum Obsidian version
const versions = JSON.parse(readFileSync('versions.json', 'utf8'));
versions[targetVersion] = minAppVersion;
writeFileSync('versions.json', JSON.stringify(versions, null, '\t'));

console.log(`Bumped to ${targetVersion} (requires Obsidian >= ${minAppVersion})`);

Wire it into package.json so npm version triggers it automatically:

json
{
  "scripts": {
    "version": "node version-bump.mjs && git add manifest.json versions.json"
  }
}
Step 3: Create GitHub Release
bash
set -euo pipefail
# Bump version, commit, and tag
npm version patch   # or minor / major
git push origin main --tags

# Create release with assets (or let the release workflow from obsidian-ci-integration handle it)
gh release create "$(node -p 'require("./manifest.json").version')" \
  main.js manifest.json styles.css \
  --title "v$(node -p 'require("./manifest.json").version')" \
  --generate-notes

The release must include these files at the root level (not nested in folders):

  • main.js — compiled plugin code
  • manifest.json — plugin metadata
  • styles.css — only if your plugin has custom styles
Step 4: Submit to Community Plugins

First-time submission requires a PR to the obsidian-releases repo:

bash
set -euo pipefail
# Fork and clone the releases repo
gh repo fork obsidianmd/obsidian-releases --clone
cd obsidian-releases

# Add your plugin entry to community-plugins.json
node -e "
  const fs = require('fs');
  const plugins = JSON.parse(fs.readFileSync('community-plugins.json', 'utf8'));
  const entry = {
    id: 'your-plugin-id',
    name: 'Your Plugin Name',
    author: 'Your Name',
    description: 'Brief description of what your plugin does.',
    repo: 'your-github-username/your-plugin-repo'
  };

  // Insert alphabetically by id
  const idx = plugins.findIndex(p => p.id.localeCompare(entry.id) > 0);
  plugins.splice(idx >= 0 ? idx : plugins.length, 0, entry);
  fs.writeFileSync('community-plugins.json', JSON.stringify(plugins, null, '\t') + '\n');
  console.log('Added', entry.id, 'at index', idx >= 0 ? idx : plugins.length);
"

git checkout -b add-your-plugin-id
git add community-plugins.json
git commit -m "Add your-plugin-id"
git push origin add-your-plugin-id
gh pr create --repo obsidianmd/obsidian-releases \
  --title "Add your-plugin-id" \
  --body "## Plugin submission

- **Repo:** https://github.com/your-username/your-plugin-repo
- **Description:** Brief description
- **I have tested on:** Desktop (macOS/Windows/Linux), Mobile (iOS/Android)"

Review requirements the Obsidian team checks:

  • manifest.json has all required fields (id, name, version, minAppVersion, description, author)
  • id in manifest matches the id in your community-plugins.json entry
  • No console.log in production code
  • No eval() or dynamic code execution
  • No remote code loading at runtime
  • Plugin works on mobile if isDesktopOnly is not set
Step 5: BRAT for Beta Testing

Before submitting to community plugins, test your distribution via BRAT:

  1. Users install BRAT from community plugins
  2. In BRAT settings, they click "Add Beta Plugin"
  3. They enter your GitHub repo URL: your-username/your-plugin-repo
  4. BRAT installs the latest release (including pre-releases)

To push a beta:

bash
set -euo pipefail
npm version prerelease --preid=beta
git push origin main --tags
gh release create "$(node -p 'require("./manifest.json").version')" \
  main.js manifest.json styles.css \
  --title "Beta: v$(node -p 'require("./manifest.json").version')" \
  --prerelease
Step 6: Manual Installation

For users who prefer manual install or for testing outside BRAT:

bash
set -euo pipefail
# Users copy files to their vault's plugin directory
VAULT_PATH="/path/to/vault"
PLUGIN_ID="your-plugin-id"
DEST="$VAULT_PATH/.obsidian/plugins/$PLUGIN_ID"

mkdir -p "$DEST"
cp main.js manifest.json "$DEST/"
test -f styles.css && cp styles.css "$DEST/"

echo "Installed to $DEST — restart Obsidian and enable in Settings > Community Plugins"
Show full SKILL.md (199 more words)Show less

Output

  • Production main.js, manifest.json, and styles.css as GitHub release assets
  • version-bump.mjs script for consistent versioning across all config files
  • PR to obsidianmd/obsidian-releases for community plugin listing
  • BRAT-compatible releases for beta testing
  • Manual install path for direct distribution

Error Handling

IssueCauseSolution
Plugin not loading after installid in manifest doesn't match directory nameEnsure the plugin folder name matches manifest.json id
Build output missingesbuild outfile misconfiguredSet outfile: 'main.js' in esbuild config
Community PR rejectedGuidelines violationCheck Plugin Guidelines
Version mismatchForgot to run version-bumpUse npm version which triggers the script automatically
BRAT can't find releasesNo GitHub release createdBRAT needs actual GitHub releases, not just tags
gh release create failsNot authenticatedRun gh auth login first
Manual install doesn't loadMissing manifest.jsonAll three files must be in the plugin directory

Examples

Update an Existing Community Plugin

Already listed? Just create a new release — Obsidian auto-detects new versions:

bash
set -euo pipefail
npm version patch
git push origin main --tags
# Release workflow creates the GitHub release automatically

Users see the update in Settings > Community Plugins > Check for updates.

Check Your Submission Status
bash
set -euo pipefail
# See if your plugin is already in the directory
gh pr list --repo obsidianmd/obsidian-releases --search "your-plugin-id" --state all

Resources

Next Steps

For event handling patterns, see obsidian-webhooks-events. For pre-release quality validation, see obsidian-prod-checklist.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/.curated/obsidian-deploy-integration of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • references/implementation-guide.md
  • references/implementation.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Obsidian Deploy Integration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Obsidian Deploy Integration compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Obsidian Deploy Integration this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.1kAutomated safety check: PassMIT
Release NotesRAIT-09/obsidian-agent-client2.4k—~4.2kAutomated safety check: PassApache-2.0
Store Submitzhitongblog/solomd1.2k—~1.7kAutomated safety check: NotesMIT
Lov Any2pdflovstudio/any2pdf211—~2.4kAutomated safety check: NotesMIT
Triageflowershow/flowershow1.1k—~1.9kAutomated safety check: PassAGPL-3.0
Swarmvaultswarmclawai/swarmvault709—~6.1kAutomated safety check: PassMIT

Similar skills

  • Release Notes

    RAIT-09/obsidian-agent-client

    Generate a GitHub release note draft for this Obsidian plugin repository.

    2.4k GitHub stars~4.2k tokensUpdated 8 days ago
    DevelopmentAuto-check passed
  • Store Submit

    zhitongblog/solomd

    Publish a SoloMD release to the stores that have no usable submission API — Google Play Console and Microsoft Partner Center — by driving them through the local Unzoo Browser REST API.

    1.2k GitHub stars~1.7k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Lov Any2pdf

    lovstudio/any2pdf

    Convert Markdown documents to professionally typeset PDF files with reportlab.

    211 GitHub stars~2.4k tokensUpdated 2 mo ago
    Documents & OfficeAuto-check: notes
  • Triage

    flowershow/flowershow

    Automatically triage a newly opened GitHub issue — categorise it, verify the claim, and apply the right category and state so a maintainer or agent can pick it up.

    1.1k GitHub stars~1.9k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Swarmvault

    swarmclawai/swarmvault

    Use SwarmVault when the user needs a local-first knowledge vault that writes durable markdown, graph, search, dashboard, review, chat-session, context-pack, task-ledger, static AI export, retrieval…

    709 GitHub stars~6.1k tokensUpdated 3 mo ago
    Knowledge ManagementAuto-check passed
  • Competitor Feedback

    zhitongblog/solomd

    Scan competing markdown editors' user feedback (GitHub issues/discussions/releases + closed-source forums) and synthesize themes cross-referenced against SoloMD's own gaps and roadmap.

    1.2k GitHub stars~1.2k tokensUpdated yesterday
    Knowledge ManagementAuto-check: notes

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated yesterday
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Works with

Questions about Obsidian Deploy Integration

What does Obsidian Deploy Integration do?

Publish Obsidian plugins to the community plugin directory. An agent skill from jeremylongshore/tons-of-skills-marketplace. Obsidian Deploy Integration is an agent skill from jeremylongshore/tons-of-skills-marketplace. Publish Obsidian plugins to the community plugin directory.

When should I use Obsidian Deploy Integration?

Obsidian Deploy Integration fits situations like: releasing your first plugin; updating existing plugins; managing the community plugin submission process; with phrases like publish obsidian plugin.

How do I install Obsidian Deploy Integration in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a claude-code`. Or copy the skill folder (skills/.curated/obsidian-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/obsidian-deploy-integration in your project. Claude Code loads it when a task matches its description.

How do I install Obsidian Deploy Integration in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a codex`. Or copy the skill folder (skills/.curated/obsidian-deploy-integration in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/obsidian-deploy-integration in your project. Codex loads it when a task matches its description.

Can I use Obsidian Deploy Integration in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/obsidian-deploy-integration, .gemini/skills/obsidian-deploy-integration, .github/skills/obsidian-deploy-integration and .opencode/skills/obsidian-deploy-integration in your project.

What does Obsidian Deploy Integration need to run?

Going by SKILL.md and its folder, Obsidian Deploy Integration needs the command-line tools its instructions call (gh, npm, git and node). Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(git:*), Bash(gh:*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Obsidian Deploy Integration access the network?

SKILL.md names 2 domains. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. As links in the text: docs.obsidian.md. This is read from the text; nothing was executed.

Is Obsidian Deploy Integration safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Obsidian Deploy Integration use?

Obsidian Deploy Integration is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Obsidian Deploy Integration use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.2k tokens, read only when the agent opens those files.

What are the alternatives to Obsidian Deploy Integration?

Skills that share tags, products or a category with Obsidian Deploy Integration: Release Notes (RAIT-09/obsidian-agent-client, 2.4k stars), Store Submit (zhitongblog/solomd, 1.2k stars), Lov Any2pdf (lovstudio/any2pdf, 211 stars) and Triage (flowershow/flowershow, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Obsidian Deploy Integration?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.