plugin-manager

Manage plugin packaging and configuration across Cursor and Claude Code.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/devsanthoshmk/MKS-Agency --skill plugin-manager-devsanthoshmk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plugin-manager
Source: https://github.com/devsanthoshmk/MKS-Agency/tree/main/.agent/skills/plugin-manager
Command: npx skills add https://github.com/devsanthoshmk/MKS-Agency --skill plugin-manager-devsanthoshmk

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of keeping plugin structure, shared skill content, and MCP configuration consistent across Cursor and Claude Code—without duplicating files or breaking repo conventions.

Core Features & Use Cases

  • Repository-wide plugin packaging: Creates or updates plugins under plugins/<plugin-name>/ with both Claude and Cursor manifests.
  • Shared skills via symlinks: Reuses top-level skills/ content by linking into each plugin’s skills/ folder to preserve a single source of truth.
  • Plugin-local MCP configuration: Ensures each plugin has its own plugins/<plugin-name>/mcp.json for MCP server wiring.
  • Marketplace registration: Registers each plugin in repo-root marketplace manifests so both ecosystems discover it reliably.
  • Guardrails for correctness: Promotes consistent naming (kebab-case), relative manifest paths, and validation of JSON and path references.

Quick Start

Add a new plugin by creating plugins/<plugin-name>/ with both marketplace manifests and mcp.json, then symlink the required shared skills from skills/ into plugins/<plugin-name>/skills/ and register the plugin in both .claude-plugin/marketplace.json and .cursor-plugin/marketplace.json.

Frequently Asked Questions about plugin-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I share skills across Cursor and Claude Code plugins without duplicating files?

You can share skills across Cursor and Claude Code by maintaining a top-level skills/ directory as the single source of truth and symlinking required entries into each plugin's plugins/<plugin-name>/skills/ folder. This preserves content consistency without duplication.

What directory structure is required for Claude and Cursor plugin packaging?

Required plugin directory structure uses plugins/<plugin-name>/ containing both .claude-plugin/plugin.json and .cursor-plugin/plugin.json manifests with plugin-local relative paths, an mcp.json for MCP wiring, and symlinked skills entries from the top-level skills/ source.

How do I wire MCP servers for individual plugins in a repository?

You wire MCP servers by creating a plugin-local plugins/<plugin-name>/mcp.json file for each plugin. This ensures each plugin maintains its own MCP server configuration independently within the repository structure.

Does Cursor require a logo for marketplace plugin registration?

Cursor supports an optional assets/logo.svg file within the plugin directory. Both .claude-plugin/marketplace.json and .cursor-plugin/marketplace.json manifests at the repo root are required to reliably register and discover the plugin in both ecosystems.

What are the naming and path constraints for Claude Code plugin manifests?

Plugin naming must use kebab-case, and manifests must use plugin-local relative paths for references. JSON structure and path references are validated to ensure correctness across both Claude and Cursor environments.