Stats
Actions
Available In
Tags
Xsolla — Claude Code Plugin Marketplace
v0.0.1 — A plugin marketplace for Claude Code and Cowork. Meta-skills, reusable agents, MCP connections, and nested skill hierarchies — packaged as installable plugins.
Quick Start
# Add the marketplace
/plugin marketplace add xsolla/claude-plugin-marketplace
# Browse available plugins
/plugin marketplace list xsolla
# Install a plugin
/plugin install work@xsolla
In Cowork, use the plugin manager UI or ask Claude to install a plugin by name.
Core Concepts
Plugins
A plugin is the distribution unit — a .plugin zip containing skills, scripts, MCP server definitions, and commands. Each plugin has a plugin.json manifest and lives under plugins/<name>/.
plugin-name/
├── .claude-plugin/plugin.json # Manifest (name, version, description)
├── skills/ # Skill definitions (SKILL.md files)
├── scripts/ # Bundled Python/Shell implementations
├── commands/ # Slash commands (.md files)
├── .mcp.json # MCP server definitions (optional)
└── README.md
Skills
A skill is defined by a single SKILL.md file with YAML frontmatter. It is the atomic unit of capability — a set of instructions that tells Claude how to accomplish a specific task.
---
name: work-m365
description: "Microsoft 365: Mail, Calendar, Teams, Files, Tasks"
user-invocable: true
---
The description doubles as the trigger — Claude reads it to decide when to invoke the skill.
Meta-Skills (Routing & Dispatch)
A meta-skill is a skill that performs no work itself. It acts as a router: its SKILL.md contains a routing table that tells Claude which sub-skill to invoke based on context.
Example — the work meta-skill routes like this:
| Request mentions | Routes to |
|---|---|
| Outlook, Exchange, Teams, OneDrive | work-m365 |
| Gmail, Google Drive | work-google |
| Slack messages, channels | work-slack (MCP) |
| Jira issues, Confluence pages | work-jira (MCP) |
| Ambiguous "email" | Asks the user |
There is no hardcoded dispatcher. Routing is natural language in markdown — Claude reads the routing section and makes a judgment call. This makes the system flexible and context-aware without requiring code changes.
Nesting & Hierarchy
Skills nest up to two levels:
Meta-skill (router)
└── Concrete skill (does work)
└── Nested workflow (sub-task within a skill)
Real example:
work/ ← meta-skill (routes by platform)
├── work-m365/ ← concrete skill (Graph API)
├── work-slack/ ← concrete skill (Slack MCP)
└── work-jira/ ← concrete skill (Atlassian MCP)
├── triage-issue/ ← nested workflow
├── capture-tasks-from-meeting-notes/
├── generate-status-report/
├── spec-to-backlog/
└── search-company-knowledge/
Deeper nesting is intentionally avoided to keep the mental model simple.
Connections (MCP Servers)
Plugins connect to external services via MCP servers defined in .mcp.json:
| Connection | Protocol | Auth |
|---|---|---|
| Slack | https://mcp.slack.com/mcp | OAuth |
| Atlassian (Jira/Confluence) | https://mcp.atlassian.com/v1/mcp | Browser auth |
| voidtools Everything | Local uvx process | None |
| Microsoft Graph API | CLI script (m365.py) | Azure Key Vault client credentials |
MCP connections provide tools that skills can use. CLI scripts provide capabilities where no MCP server exists.
Reusable Agents
Skills and their scripts are designed to be reusable across plugins. The manage-skills skill provides a full lifecycle for plugin development: review feedback, patch, test, rebuild .plugin zip, deploy. Version tracking is enforced — every change bumps the patch version in both plugin.json and SKILL.md frontmatter.
Using Cowork & Dispatch
Cowork Mode
In Cowork (Claude desktop app), plugins are installed via the UI or by asking Claude. Once installed, skills appear in Claude's available skill list and are triggered automatically by keywords in your request.
How dispatch works: When you say "check my Jira backlog", Claude matches your request against installed skill descriptions, loads the work meta-skill, reads its routing table, and dispatches to work-jira. No slash commands needed — just describe what you want.
