CloudBase Cloud Development Workflow Collection

Problem

In CloudBase cloud development workflows, the useful unit is often not a single command but a reusable set of steps: environment setup, configuration checks, task execution, and result validation. When those steps are scattered across scripts, docs, or chat history, engineers can miss variables, repeat setup, or give a model an unstable context. This collection groups multiple CloudBase workflow skills in one repository, exposing them as entries under ./skills/ so the task selection is explicit.

How it works

It is a multi-skill collection, not a single executor. The structure is intentionally simple: executable skills are maintained under ./skills/, and each skill has its own SKILL.md. The intended usage is:
- Pick the target workflow skill in ./skills/.
- Read that skill's SKILL.md to confirm commands, inputs, outputs, and prerequisites.
- Apply the required environment variables documented by the selected skill, then run the workflow.
This makes the chain “choose skill → read documentation → configure environment” usable as context for a model or script.

Boundaries

This skill set is best when you already know the CloudBase workflow you need and are willing to follow the sub-skill documentation for variables. The provided material does not describe automatic discovery of all skills, unified credential management, or cross-platform deployment. Treat unread sub-skills as not turnkey; keep credentials, permissions, and project IDs aligned with the specific SKILL.md and your CloudBase environment.