A marketplace for Claude Code plugins providing platform engineering tools and automation. This repository hosts multiple plugins that can be installed individually or as a collection.
| Plugin | Description | Version |
|---|---|---|
| datum-platform | Kubernetes platform engineering automation with aggregated API servers, controller patterns, and GitOps deployment | 1.5.0 |
| datum-gtm | Go-to-market automation with commercial strategy, product discovery, and customer support | 1.0.0 |
Add this marketplace to Claude Code:
# In Claude Code:
/plugin marketplace add datum-cloud/claude-code-pluginsOr configure it in your project's .claude/settings.json to prompt team members to install the marketplace when they trust the project folder:
{
"extraKnownMarketplaces": {
"datum-claude-code-plugins": {
"source": {
"source": "github",
"repo": "datum-cloud/claude-code-plugins"
}
}
}
}You can also pre-enable specific plugins:
{
"extraKnownMarketplaces": {
"datum-claude-code-plugins": {
"source": {
"source": "github",
"repo": "datum-cloud/claude-code-plugins"
}
}
},
"enabledPlugins": {
"datum-platform@datum-claude-code-plugins": true,
"datum-gtm@datum-claude-code-plugins": true
}
}Once the marketplace is added, install plugins by name:
/plugin install datum-platform@datum-claude-code-plugins
/plugin install datum-gtm@datum-claude-code-pluginsFor local development, add the marketplace from your local directory:
# In Claude Code:
/plugin marketplace add ./path/to/claude-code-plugins
/plugin install datum-platform@datum-claude-code-pluginsValidate the marketplace before distribution:
# From the command line:
claude plugin validate .
# Or from within Claude Code:
/plugin validate .claude-code-plugins/
├── .claude-plugin/
│ └── marketplace.json # Marketplace catalog
├── plugins/
│ ├── datum-platform/ # Platform engineering plugin
│ │ ├── .claude-plugin/
│ │ │ └── plugin.json # Plugin manifest
│ │ ├── agents/ # Specialized agents
│ │ ├── skills/ # Knowledge modules
│ │ ├── commands/ # Slash commands
│ │ ├── hooks/ # Automation hooks
│ │ └── scripts/ # Utility scripts
│ └── datum-gtm/ # Go-to-market plugin
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin manifest
│ ├── agents/ # Specialized agents
│ ├── skills/ # Knowledge modules
│ └── commands/ # Slash commands
└── README.md
Kubernetes platform engineering automation with aggregated API servers, controller patterns, and GitOps deployment for the Datum Cloud platform.
Features:
- 6 specialized agents (api-dev, frontend-dev, sre, test-engineer, code-reviewer, tech-writer)
- 26 skill modules covering Kubernetes patterns, Go conventions, deployment workflows, and more
- Pipeline orchestration for structured feature development
- Automatic learning engine for pattern extraction
Category: Platform Engineering Tags: kubernetes, go, infrastructure, multi-tenant, devops
Go-to-market automation with commercial strategy, product discovery, and customer support tools.
Features:
- 4 specialized agents (product-discovery, commercial-strategist, gtm-comms, support-triage)
- 3 skill modules for GTM workflows
- Commercial strategy and pricing analysis
- Customer support triage automation
Category: Business Tags: gtm, marketing, product, support, commercial
-
Create a directory under
plugins/:mkdir -p plugins/your-plugin-name/.claude-plugin
-
Create the plugin manifest at
plugins/your-plugin-name/.claude-plugin/plugin.json:{ "name": "your-plugin-name", "description": "Description of your plugin", "version": "1.0.0", "author": { "name": "Your Name", "url": "https://github.com/your-org" }, "repository": "https://github.com/datum-cloud/claude-code-plugins", "license": "MIT", "keywords": ["your", "keywords"] } -
Add your plugin components:
agents/- Agent definitions (markdown files)skills/- Knowledge modulescommands/- Slash commandshooks/- Automation hooks
-
Register your plugin in
.claude-plugin/marketplace.json:{ "name": "your-plugin-name", "source": "./plugins/your-plugin-name", "description": "Description of your plugin", "version": "1.0.0", "category": "your-category", "tags": ["tag1", "tag2"] } -
Submit a pull request.
- Each plugin should be self-contained within its directory
- Use
${CLAUDE_PLUGIN_ROOT}for path references in hooks and scripts - Include a README in your plugin directory with usage documentation
- Follow semantic versioning for plugin versions
- Test your plugin locally before submitting
For detailed guidance on plugin development, see the official Claude Code documentation.
- Create plugins - Guide to creating plugins with commands, agents, hooks, MCP servers, and more
- Discover and install plugins - Installing plugins from marketplaces
- Plugin marketplaces - Creating and distributing plugin marketplaces
- Plugins reference - Complete technical specifications and schemas
- Plugin settings - Configuration options
MIT