Release Notes
RAIT-09/obsidian-agent-client
Generate a GitHub release note draft for this Obsidian plugin repository.
Agent skill
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.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-deploy-integration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "obsidian-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-deploy-integration into .claude/skills/obsidian-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-deploy-integration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-deploy-integrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-deploy-integration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/obsidian-deploy-integration .agents/skills/obsidian-deploy-integration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "obsidian-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-deploy-integration into .agents/skills/obsidian-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-deploy-integration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-deploy-integration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/obsidian-deploy-integration .cursor/skills/obsidian-deploy-integration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "obsidian-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-deploy-integration into .cursor/skills/obsidian-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-deploy-integration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/obsidian-deploy-integration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-deploy-integration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/obsidian-deploy-integration .gemini/skills/obsidian-deploy-integration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "obsidian-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-deploy-integration into .gemini/skills/obsidian-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-deploy-integration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-deploy-integrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/obsidian-deploy-integration .github/skills/obsidian-deploy-integration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "obsidian-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-deploy-integration into .github/skills/obsidian-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-deploy-integration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill obsidian-deploy-integration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace obsidian-deploy-integration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/obsidian-deploy-integration .opencode/skills/obsidian-deploy-integration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "obsidian-deploy-integration" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/obsidian-deploy-integration into .opencode/skills/obsidian-deploy-integration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obsidian-deploy-integration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
obsidian-deploy-integrationPublish 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. 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.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(git:*)Bash(gh:*)From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
ghnpmgitnodeFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comAlso links to:
docs.obsidian.mdFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
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.
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.
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.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 458 words, ~2,131 tokens.
.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.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.
main.ts, manifest.json, and styles.css (if applicable)gh CLI authenticated (gh auth status)obsidian-prod-checklist validationset -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"// 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:
{
"scripts": {
"version": "node version-bump.mjs && git add manifest.json versions.json"
}
}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-notesThe release must include these files at the root level (not nested in folders):
main.js — compiled plugin codemanifest.json — plugin metadatastyles.css — only if your plugin has custom stylesFirst-time submission requires a PR to the obsidian-releases repo:
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 entryconsole.log in production codeeval() or dynamic code executionisDesktopOnly is not setBefore submitting to community plugins, test your distribution via BRAT:
your-username/your-plugin-repoTo push a beta:
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')" \
--prereleaseFor users who prefer manual install or for testing outside BRAT:
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"main.js, manifest.json, and styles.css as GitHub release assetsversion-bump.mjs script for consistent versioning across all config filesobsidianmd/obsidian-releases for community plugin listing| Issue | Cause | Solution |
|---|---|---|
| Plugin not loading after install | id in manifest doesn't match directory name | Ensure the plugin folder name matches manifest.json id |
| Build output missing | esbuild outfile misconfigured | Set outfile: 'main.js' in esbuild config |
| Community PR rejected | Guidelines violation | Check Plugin Guidelines |
| Version mismatch | Forgot to run version-bump | Use npm version which triggers the script automatically |
| BRAT can't find releases | No GitHub release created | BRAT needs actual GitHub releases, not just tags |
gh release create fails | Not authenticated | Run gh auth login first |
| Manual install doesn't load | Missing manifest.json | All three files must be in the plugin directory |
Already listed? Just create a new release — Obsidian auto-detects new versions:
set -euo pipefail
npm version patch
git push origin main --tags
# Release workflow creates the GitHub release automaticallyUsers see the update in Settings > Community Plugins > Check for updates.
set -euo pipefail
# See if your plugin is already in the directory
gh pr list --repo obsidianmd/obsidian-releases --search "your-plugin-id" --state allFor 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
SKILL.md and 2 other files (references) in skills/.curated/obsidian-deploy-integration of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Obsidian Deploy Integration this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Release NotesRAIT-09/obsidian-agent-client | 2.4k | — | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Store Submitzhitongblog/solomd | 1.2k | — | ~1.7k | Automated safety check: Notes | MIT | |
| Lov Any2pdflovstudio/any2pdf | 211 | — | ~2.4k | Automated safety check: Notes | MIT | |
| Triageflowershow/flowershow | 1.1k | — | ~1.9k | Automated safety check: Pass | AGPL-3.0 | |
| Swarmvaultswarmclawai/swarmvault | 709 | — | ~6.1k | Automated safety check: Pass | MIT |
RAIT-09/obsidian-agent-client
Generate a GitHub release note draft for this Obsidian plugin repository.
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.
lovstudio/any2pdf
Convert Markdown documents to professionally typeset PDF files with reportlab.
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.
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…
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.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.