How do I install the Kubeblocks Engine Generic skill?

Run npx skillmds@latest add apecloud/kubeblocks-engine-generic in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Kubeblocks Engine Generic safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Kubeblocks Engine Generic?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Kubeblocks Engine Generic free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Kubeblocks Engine Generic?

apecloud (@apecloud) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Kubeblocks Engine Generic by apecloud

Name: Kubeblocks Engine Generic
Rating: 4.5 (4 reviews)
Author: apecloud

Kubeblocks Engine Generic

Generic create-time fallback for KubeBlocks engines that do not yet have a dedicated kubeblocks-engine-* entry. Use this only after kubeblocks-preflight and only when the engine is not locked into the Tier-1 dedicated set. The legacy kubeblocks-create-cluster skill remains only as a compatibility shim.

apecloud Updated Sep 10, 2026

File contents

Generic Engine Fallback

Use this only when all three statements are true:

kubeblocks-preflight has already produced a recommendation bundle.
references/coverage/engine-tier-map.yaml does not place the target engine in the Tier-1 dedicated set.
references/routing/route-matrix.yaml allows the request to continue through kubeblocks-engine-generic.

What This Entry Must Decide

Before applying any generic Cluster manifest, make the following explicit:

clusterDef and topology
serviceVersion
storageClassName and any topology-aware storage requirement from preflight
sizing profile
connection / verification plan
next-hop operations and observability path

Generic Workflow

Confirm the engine really belongs to the generic fallback.
Gather clusterDef, topology, and component names from the live environment.
Fill the preserved generic Cluster template in legacy reference.md.
Validate with kubectl apply --dry-run=server.
Apply and verify the cluster reaches Running.

Never use this as the default path for any Tier-1 engine.

Frequently asked questions