#142 feat: ship a Cursor Marketplace plugin from the existing skills

Summary

Package this repo as a Cursor Marketplace plugin so Cursor users can install the existing Obsidian skills in one click, the same way Claude Code users already install obsidian@obsidian-skills.

No Cursor-specific skill rewrite is needed. The skills/ tree already follows the Agent Skills spec. Cursor auto-discovers skills/*/SKILL.md from a .cursor-plugin/plugin.json (Plugins reference).

I rechecked cursor.com/marketplace on 2026-09-08: search for obsidian still returns no results. There is also no .cursor-plugin/ on main, and no existing issue or PR for a Cursor plugin.

Related, not a duplicate: #65 / PR #110 add a Codex marketplace manifest. Same adoption idea, different client.

Why Marketplace (adoption)

Cursor users can already pull skills via npx skills add, but that lives outside the product. Marketplace is the in-client path:

discoverable from Customize / Marketplace
one install, skills loaded with the plugin
same git tree as the Claude plugin — one source of truth

Hugging Face already ships this dual layout from one repo (.claude-plugin + .cursor-plugin, same skills/) and lists it as Hugging Face.

A PR can add the Cursor manifest. Listing is a separate maintainer step: only the plugin author/owner can submit the public GitHub URL at cursor.com/marketplace/publish. Cursor reviews every plugin (and every update) by hand. Merging a PR does not publish the listing.

Current gap

README install paths today:

Claude Code marketplace (/plugin marketplace add kepano/obsidian-skills)
npx skills add
Codex / OpenCode copy-or-clone

There is no Cursor plugin manifest and no Marketplace listing, so Cursor users do not get the same first-class install as Claude Code users.

Proposed shape (small PR)

On current main (skills at repo root):

Add .cursor-plugin/plugin.json. Reuse the Claude plugin identity (name: obsidian, same description / author / keywords / version). Omit skills so Cursor’s default skills/ discovery picks up the five existing skills. No mcp.json — this repo has no MCP servers today.
README: add a short Cursor install section (Marketplace once listed; until then, npx skills plus local plugin test).
Optional: logo via relative path in the manifest. Not required.

If PR #110 lands first, put .cursor-plugin/plugin.json next to .claude-plugin and .codex-plugin under plugins/obsidian/, and include it in the version bump script. Same skills, no duplication.

Happy to open that PR if this shape is welcome. I will not open a competing implementation without maintainer direction.

Dual-client packaging (please read before adding MCP)

This repo is already a Claude Code plugin (.claude-plugin/). A Marketplace install clones the entire GitHub root, so .claude-plugin/ and .cursor-plugin/ will sit side by side. That is the intended dual-client layout.

Cursor’s documented MCP file is mcp.json. Claude Code’s is .mcp.json. If those two files both exist at the plugin root with different payloads, a Marketplace clone can start the wrong server. I hit that on another dual plugin: cursor/plugins#252.

This repo has neither file today, so the bug does not apply yet. If you add MCP later:

ship one shared config (Hugging Face uses .mcp.json only)
pin it in the Cursor manifest: "mcpServers": "./.mcp.json"
do not also leave a sibling mcp.json with a different server

That is what Hugging Face skills and Figma’s mcp-server-guide do.

Out of scope

Forking or rewriting SKILL.md files for Cursor
Adding an Obsidian MCP server
Submitting the Marketplace form from a contributor account (needs the maintainer)

Questions for maintainers

Is a Cursor Marketplace listing welcome, or should Cursor stay on npx skills only?
Plugin name: keep obsidian (matches the Claude plugin), or prefer obsidian-skills?
If (1) is yes, I can open the manifest + README PR against main, or against the plugins/obsidian/ layout from #110 if that is the intended tree. After merge, would you submit cursor.com/marketplace/publish with this repo URL?