By datum-cloud
Kubernetes platform engineering automation with aggregated API servers, controller patterns, GitOps deployment, and platform capabilities
Display user correction statistics and patterns. Shows recent corrections, their types, affected agents, and emerging patterns from user feedback.
Trigger deployment workflow for a feature. Invokes the SRE agent to handle deployment configuration, staging rollout, and production promotion.
Quick-start feature discovery. Creates a pipeline entry and invokes the product-discovery agent to begin the discovery process.
Analyze review findings and session learnings to extract patterns, update the pattern registry, and automatically promote high-confidence patterns to agent runbooks. Run periodically to keep runbooks current.
Display pattern statistics from the learning engine. Shows top patterns, their frequency, trends, and which agents are affected.
MUST BE USED for Go backend implementation on Kubernetes aggregated API servers. Use for implementing API types, storage backends, server configuration, request handlers, code generation, and any Go code in cmd/, internal/, or pkg/ directories. Use for running code generation, linting, and testing. Use AFTER architect has produced a design.
MUST BE USED as a post-implementation quality gate. Use after api-dev, frontend-dev, or sre complete changes. Use when someone says "review this" or "check this code" or "is this ready to merge." Reviews for correctness, security, convention compliance, and platform integration completeness. Read-only — produces findings, never modifies code.
MUST BE USED for React/TypeScript UI implementation, component development, page layouts, form implementation, dashboard creation, and any frontend code changes. Use for building admin UIs, service provider portals, consumer-facing resource management, or any browser-based tooling.
Use for architectural design and planning of Kubernetes platform features. Produces design documents for aggregated API servers, controllers, event processing pipelines, and platform capabilities. Use BEFORE api-dev or other implementation agents. Outputs designs to .claude/pipeline/designs/.
MUST BE USED for Kustomize manifests, CI/CD pipeline configuration, Dockerfile changes, RBAC configuration, observability setup, deployment configuration, container security, TLS configuration, FluxCD deployment, OCIRepository configuration, and any infrastructure-as-code changes. Use for anything in config/, .github/, Dockerfile, or infra repository changes.
Covers creating C4 architecture diagrams using PlantUML. Use when documenting system architecture, component relationships, or container layouts for technical documentation.
Covers activity timeline integration using the Activity system. Use when implementing ActivityPolicy resources, emitting Kubernetes events for activity tracking, or exposing activity timelines to users via CLI, UI, or API.
Decision framework for determining which platform capabilities a feature needs (Quota, Insights, Telemetry, Activity). Use when planning a new feature to assess which capabilities apply.
Covers proactive issue detection using the Insights system. Use when implementing InsightPolicy resources with CEL-based rules to automatically detect misconfigurations, health issues, or security concerns.
Covers resource quota integration using the Milo quota system. Use when implementing ResourceRegistration, ClaimCreationPolicy, or GrantCreationPolicy resources for quota enforcement and allocation.
Modifies files
Hook triggers on file write and edit operations
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
No model invocation
Executes directly as bash, bypassing the AI model
No model invocation
Executes directly as bash, bypassing the AI model
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 |
| milo-activity | Query audit logs, investigate incidents, and author ActivityPolicies using the Milo Activity service | 1.0.0 |
Add this marketplace to Claude Code:
# In Claude Code:
/plugin marketplace add datum-cloud/claude-code-plugins
Or 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-plugins
/plugin install milo-activity@datum-claude-code-plugins
For 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-plugins
Validate 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
│ └── milo-activity/ # Activity service plugin
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin manifest
│ ├── agents/ # Investigation & authoring agents
│ └── skills/ # Activity workflows & CEL reference
└── README.md
Kubernetes platform engineering automation with aggregated API servers, controller patterns, and GitOps deployment for the Datum Cloud platform.
Features:
Category: Platform Engineering Tags: kubernetes, go, infrastructure, multi-tenant, devops
Go-to-market automation with commercial strategy, product discovery, and customer support tools.
Features:
Category: Business Tags: gtm, marketing, product, support, commercial
Query audit logs, investigate incidents, and author ActivityPolicies using the Milo Activity service. Wraps the Activity MCP server with higher-level skills and agents that teach Claude how to use Activity for incident investigation, change auditing, and policy authoring.
npx claudepluginhub datum-cloud/claude-code-plugins --plugin datum-platformGo-to-market automation with commercial strategy, product discovery, and customer support tools for Datum Cloud
Query audit logs, investigate incidents, and author ActivityPolicies using the Milo Activity service
Skills for the Datum Cloud platform: Compute, DNS, AI Edge, WAF
Complete DevOps automation platform with CI/CD pipeline management, infrastructure as code, security scanning, and deployment automation. Includes hooks for config validation and MCP server for deployment tracking.
Practical guidance for platform engineers across Claude, Codex, Cursor, and Copilot: Kubernetes, Kyverno, Helm, Terraform, Flux CD (Flux Operator, FluxInstance, gitless OCI delivery, cluster debug, repo audit), Argo CD, GitHub Actions (composite actions, SHA pinning, OIDC, 11 production examples), AWS (CloudFront, WAF, Lambda@Edge, IAM, IRSA), Azure (AKS workload identity), GKE (Workload Identity Federation), Linkerd, Linux, networking, MCP development, observability, SOC 2 compliance, PR review, PR triage, KEDA autoscaling, Karpenter node autoscaling, supply chain security (Cosign, SBOM, SLSA), Falco runtime security, Chaos Engineering, DORA Metrics, LLM Observability (Datadog LLMObs), and animated docs. Every answer includes blast radius, validation steps, and rollback plan.
Claude Code skill pack for Cast AI (18 skills)
Platform engineering agents providing expertise in developer platforms, IaC, and tooling
Deployment engineering with Terraform and infrastructure as code
Use this agent when setting up CI/CD pipelines, configuring Docker containers, deploying applications to cloud platforms, setting up Kubernetes clusters, implementing infrastructure as code, or automating deployment workflows. Examples: <example>Context: User is setting up a new project and needs deployment automation. user: "I've built a FastAPI application and need to deploy it to production with proper CI/CD" assistant: "I'll use the deployment-engineer agent to set up a complete deployment pipeline with Docker, GitHub Actions, and production-ready configurations."</example> <example>Context: User mentions containerization or deployment issues. user: "Our deployment process is manual and error-prone. We need to automate it." assistant: "Let me use the deployment-engineer agent to design an automated CI/CD pipeline that eliminates manual steps and ensures reliable deployments."</example>