Cloudbase
Ship and run WeChat mini programs, Web/H5, or serverless backends on Tencent CloudBase with correct auth, data, deploy, and ops patterns in the agent.
Overview
CloudBase is an agent skill most often used in Build (also Ship and Operate) that routes solo builders through Tencent CloudBase patterns for auth, databases, cloud functions, hosting, AI, and troubleshooting on mini pro
Install
npx skills add https://github.com/tencentcloudbase/skills --skill cloudbaseWhat is this skill?
- Activation contract routes to auth-tool vs auth-web, platform split (Web/Mini Program vs Node/Python HTTP/CloudRun), and
- Covers Web (React, Vue, Vite, Next, Nuxt), WeChat mini programs, uni-app, and mobile clients via HTTP API
- NoSQL and MySQL guides plus security rules, cloud functions (scf_bootstrap, HTTP functions), CloudRun Dockerfile deploy,
- Built-in and third-party LLM flows (streamText, generateImage, TokenHub, LangChain/LangGraph) with AI safety routing
- Spec-style workflow hooks (requirements, architecture, tasks.md) and ops paths for health checks, logs, and troubleshoot
- Skill package version 2.19.5 documented in SKILL frontmatter
- Activation contract mandates routing via stable identifiers such as auth-tool and auth-web
- Platform split explicitly separates Web/Mini Program client stacks from Node.js/Python HTTP and CloudRun backends
Adoption & trust: 1 installs on skills.sh; 64 GitHub stars; 2/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
What problem does it solve?
You are shipping on Tencent CloudBase but easy-to-mix-up choices—Auth Tool vs Auth Web, platform split, security rules, and deploy type—cause broken login, unsafe data access, or failed cloud function deploys.
Who is it for?
Solo builders building or maintaining WeChat mini programs, CloudBase-backed Web/H5 apps, or serverless APIs who want the coding agent to enforce Tencent-specific auth, database, and deploy conventions.
Skip if: Teams standardized on AWS/GCP/Azure only, products with no WeChat or CloudBase dependency, or one-off scripts that never touch CloudBase environments or consoles.
When should I use this skill?
You develop, design, build, deploy, debug, migrate, or troubleshoot CloudBase (腾讯云开发, TCB, 微信云开发) projects across Web, mini programs, uni-app, or mobile HTTP clients.
What do I get? / Deliverables
The agent follows the CloudBase activation contract to the correct sub-skill, applies platform-appropriate auth and data rules, and leaves you with deployable functions, hosting, and ops steps aligned with CloudBase docs
- CloudBase-aligned auth, database, and API integration code
- Cloud function or CloudRun deploy configuration with correct platform split
- Ops and troubleshooting steps tied to CloudBase logs and environment checks
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Builders adopt CloudBase when wiring the product to Tencent’s managed database, functions, storage, and hosting—canonical shelf is platform integration during build, with deploy and ops as natural follow-ons. The skill is a routing hub for auth, NoSQL/MySQL, cloud functions, CloudRun, static hosting, and AI APIs—core value is integrating the full CloudBase stack into the app, not a single UI or test task.
Where it fits
Scope an MVP on CloudBase with requirements and tasks.md before wiring auth and the first cloud function.
Implement NoSQL or MySQL access with the correct security rules and server-side writes for user-owned data.
Choose Auth Tool for mini program silent login versus Auth Web with publishable key for an H5 dashboard.
Deploy a Dockerfile CloudRun service or HTTP cloud function and attach static hosting for the marketing site.
Run CloudBase diagnostics, trace function logs, and fix a broken deploy or migration without reverting to ad-hoc Stack Overflow guesses.
How it compares
Use this platform skill bundle for end-to-end CloudBase conventions—not generic serverless snippets or unrelated WeChat marketing copy without TCB wiring.
Common Questions / FAQ
Who is cloudbase for?
Indie and solo developers shipping on Tencent CloudBase: mini programs, uni-app, React/Vue/Next sites, dashboards, and HTTP-backed mobile clients who need guided auth, DB, functions, and deploy paths in the agent.
When should I use cloudbase?
Use it during build when integrating CloudBase services; during ship when deploying cloud functions, CloudRun, or static hosting; during operate when debugging logs and health; and during validate when scoping a CloudBase MVP or prototype with the spec workflow.
Is cloudbase safe to install?
Review the Security Audits panel on this Prism page for published audit results; the skill instructs agents to use publishable keys on Web, avoid exposing secrets in client code, and consult security-rule guides before production data access.
SKILL.md
READMESKILL.md - Cloudbase
# CloudBase Development Guidelines ## Activation Contract Read this section first. The routing contract uses stable skill identifiers such as `auth-tool`, `auth-web`, and `http-api`, so it works across source files, generated artifacts, and local installs. ### Standalone skill fallback If the current environment only exposes a single published skill, start from the CloudBase main entry: - CloudBase main entry: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/SKILL.md` - Sibling skill pattern: `https://cnb.cool/tencent/cloud/cloudbase/cloudbase-skills/-/git/raw/main/skills/cloudbase/references/<skill-id>/SKILL.md` When a skill body references stable sibling ids such as `auth-tool`, `auth-web`, `ui-design`, or `web-development`, replace `<skill-id>` with that published directory name to open the original file. If a skill points to its own `references/...` files, keep following those relative paths from the current skill directory. If the environment does not support MCP directly, read `cloudbase` first and follow its mcporter / MCP setup guidance before using any platform-specific skill. ### Global rules before action - Identify the scenario first, then read the matching source skill before writing code or calling CloudBase APIs. - Prefer semantic sources when maintaining the toolkit, but express runtime routing in stable skill identifiers rather than repo-only paths. Do not treat generated, mirrored, or IDE-specific artifacts as the primary knowledge source. - Use MCP or mcporter first for CloudBase management tasks, and inspect tool schemas before execution. - If the task includes UI, read `ui-design` first and output the design specification before interface code. - If the task includes login, registration, or auth configuration, read `auth-tool` first and enable required providers before frontend implementation. - Keep auth domains separate: management-side login uses `auth`; app-side auth configuration uses `queryAppAuth` / `manageAppAuth`. ### Universal guardrails - If the same implementation path fails 2-3 times, stop retrying and reroute. Re-check the selected platform skill, runtime, auth domain, permission model, and SDK boundary before editing more code. - Always specify `EnvId` explicitly in code, configuration, and command examples when initializing CloudBase clients or manager operations. Do not rely on the current CLI-selected environment, implicit defaults, or copied local state. - When saving MCP or tool results to a local file with a generic file-writing tool, pass text, not raw objects. For JSON output files, serialize first with `JSON.stringify(result,