القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Primary create-time entry for ClickHouse on KubeBlocks. Use when the user wants to provision ClickHouse and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown.
Primary create-time entry for Elasticsearch on KubeBlocks. Use when the user wants to provision Elasticsearch and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-elasticsearch skill remains only as a compatibility shim.
Primary create-time entry for Kafka on KubeBlocks. Use when the user wants to provision Kafka and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-kafka skill remains only as a compatibility shim.
Primary create-time entry for MariaDB on KubeBlocks. Use when the user wants to provision MariaDB and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown.
Primary create-time entry for Milvus on KubeBlocks. Use when the user wants to provision Milvus and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-milvus skill remains only as a compatibility shim.
Primary create-time entry for MinIO on KubeBlocks. Use when the user wants to provision MinIO and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown.
| 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. |
| compatibility | {"required_tools":["kubectl","helm"],"optional_tools":["npx"],"notes":"Requires Kubernetes access for install, preflight, provisioning, and operations. For local development, create a cluster first."} |
This root skill is router only. It should decide the next step, not become a second README and not restate every leaf workflow.
Use:
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
Operate an existing cluster Route to the matching capability layer:
Observability
Troubleshooting Route to troubleshoot from any stage when state is unknown, capability is unclear, or observed behavior is broken. For replica recovery or HA repair after troubleshooting, also consider rebuild-replica.
kubeblocks-addons or KubeBlocks core repo checkouts as runtime prerequisites. The runtime path must work from this repo plus official public docs.metrics-ready, scrape-ready, dashboard-ready, or alerting-ready.kubeblocks-addon-*, kubeblocks-create-cluster, or old Day-2 names as the primary path when the corresponding kubeblocks-engine-*, kubeblocks-engine-generic, or kubeblocks-op-* entry exists.kubeblocks-preflight should produce an environment profile / recommendation bundle that downstream engine-entry skills can consume. At minimum it must answer:
storageClassNameWaitForFirstConsumer storage is requiredexisting-stack or bootstrap-stackpreflight first. Do not jump directly from install to addon provisioning.observability-existing-stack, not full monitoring bootstrap.other-addons fallback.