apecloud/kubeblocks
/SKILL.md
Route database work on Kubernetes to the right KubeBlocks skill. Use this as the top-level entrypoint when the user needs a database, database operations, or database observability on Kubernetes. The root skill only decides the next hop; detailed workflows live in the leaf skills.
$ install --global
skillsauthnpx skillsauth add apecloud/kubeblocks-skills kubeblocksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 18, 2026, 7:59 AM17.9s18 files scanned
SKILL.md
- name:
- kubeblocks
- version:
- 0.3.0
- description:
- Route database work on Kubernetes to the right KubeBlocks skill. Use this as the top-level entrypoint when the user needs a database, database operations, or database observability on Kubernetes. The root skill only decides the next hop; detailed workflows live in the leaf skills.
- notes:
- Requires Kubernetes access for install, preflight, provisioning, and operations. For local development, create a cluster first.
KubeBlocks Router
This root skill is a router only. It should decide the next step, not re-explain every workflow.
Use README.md for repository overview, installation instructions, and the full skill catalog.
Route Order
Always route in this order:
-
No Kubernetes cluster yet Route to create-local-k8s-cluster.
-
Kubernetes exists, but KubeBlocks is not installed Route to install-kubeblocks.
-
First-time provisioning, or environment readiness is unknown Route to kubeblocks-preflight before any engine-specific provisioning.
-
Provision a database after preflight
- MySQL → addon-mysql
- PostgreSQL → addon-postgresql
- Redis → addon-redis
- MongoDB → addon-mongodb
- Kafka → addon-kafka
- Elasticsearch → addon-elasticsearch
- Milvus → addon-milvus
- Qdrant → addon-qdrant
- RabbitMQ → addon-rabbitmq
- Other engines without dedicated entry skills → create-cluster
-
Operate an existing cluster Route to the matching Day-2 skill:
- lifecycle, scaling, backup, restore, parameters, switchover, rebuild, expose, TLS, accounts, or upgrade.
-
Observability
- Existing Prometheus/Grafana stack → observability-existing-stack
- No monitoring base yet → observability-bootstrap-stack
- If the user only says “set up monitoring”, use the shim setup-monitoring, which routes to the right observability branch.
-
Troubleshooting Route to troubleshoot.
Hard Routing Rules
- Do not route MySQL, PostgreSQL, Redis, MongoDB, or Kafka to the generic create-cluster path.
- Do not provision a first-time database without going through kubeblocks-preflight when environment readiness is unknown.
- Do not equate “metrics exist” with “monitoring is delivered”. Observability must declare whether it is only
metrics-ready,scrape-ready,dashboard-ready, oralerting-ready.
Recommendation Bundle Contract
kubeblocks-preflight should produce an environment profile / recommendation bundle that downstream engine-entry skills can consume. At minimum it must answer:
- Recommended
storageClassName - Whether topology-aware /
WaitForFirstConsumerstorage is required - Which engine entry skill to use
- Which generic paths are forbidden
- Demo vs production sizing guidance
- Whether observability should go to
existing-stackorbootstrap-stack
Common Misroutes To Prevent
- ACK multi-AZ + PostgreSQL/MySQL:
Route to
preflightfirst. Do not jump directly from install to addon provisioning. - Existing Prometheus/Grafana:
Route to
observability-existing-stack, not full monitoring bootstrap. - Unknown or low-frequency engines:
Only then use create-cluster as the
other-addonsfallback.
Related Skills
apecloud/kubeblocks-volume-expansion
devops
VerifiedTrustedCommunity
Expand persistent volume storage for KubeBlocks database clusters via OpsRequest. Requires the StorageClass to support volume expansion (allowVolumeExpansion=true). Use when the user needs more disk space, wants to increase storage, expand volumes, or resize PVCs. NOT for changing CPU/memory (see vertical-scaling) or adding more replicas (see horizontal-scaling). Note that volume shrinking is not supported by Kubernetes.
2SKILL.mdUpdated Apr 18, 2026
apecloud/kubeblocks-vertical-scaling
data-ai
VerifiedTrustedCommunity
Scale CPU and memory resources for KubeBlocks database clusters via OpsRequest (vertical scaling). Supports in-place updates when the feature gate is enabled. Use when the user wants to change, increase, decrease, resize, or adjust CPU or memory resources of a database cluster. NOT for adding/removing replicas or shards (see horizontal-scaling) or expanding disk storage (see volume-expansion).
2SKILL.mdUpdated Apr 18, 2026
apecloud/kubeblocks-upgrade
data-ai
VerifiedTrustedCommunity
Upgrade the KubeBlocks operator itself via Helm. Covers update operator, upgrade to v1.0, update kubeblocks version, and CRD updates. Use when the user wants to upgrade KubeBlocks, update the operator, or upgrade to a new KubeBlocks release. NOT for upgrading database engine versions (see minor-version-upgrade).
2SKILL.mdUpdated Apr 18, 2026
apecloud/kubeblocks-troubleshoot
development
VerifiedTrustedCommunity
Diagnostic guide for KubeBlocks-managed database clusters. Use when the user reports troubleshoot, debug, diagnose, not working, error, failed, stuck, CrashLoopBackOff, cluster exception, or similar problems with their database cluster. This skill guides the agent through diagnostic steps — it does NOT perform actions.
2SKILL.mdUpdated Apr 18, 2026