Individual skill
cloudbase-all-in-one
Unified CloudBase execution guide for all-in-one skill installs. Use this first for CloudBase app tasks, especially existing apps with TODOs, fixed pages, or active handlers. Routes PostgreSQL / CloudBase PG / app.rdb() / queryPgDatabase / managePgDatabase work away from legacy NoSQL and old auth patterns.
config/source/skills/SKILL.md
Source commit c12186cd825b6f0af9fcb01c846d6ad442bf0c1e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 3, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,163
- Repository last updated
- Nov 7, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- cloudbase Repository topic
- mcp Repository topic
- miniprogram Repository topic
- tencent Repository topic
- web Repository topic
- aicoding Repository topic
- supabase Repository topic
- vibe-coding Repository topic
- database Repository topic
- engineering Derived category
- data Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
LICENSE.mddoc · 1,074 bytesSKILL.mdcore · 13,038 bytesSKILL.mdcore · 13,038 bytesSKILL.mdcore · 13,038 bytes
Read excerpt
# CloudBase All-In-One
## Step 0 — Confirm the site (domestic vs international)
CloudBase runs 国内站 (domestic, `cloud.tencent.com`) and 国际站 (international, `tencentcloud.com`) as **two independent account systems** — environments, consoles, API keys, and login state do not cross over. A wrong-site login looks like *"logged in, but no environments"* rather than a clear error, so settle the site before logging in or configuring MCP.
- **International (国际站)** — connect the international remote MCP endpoint directly: `https://tcb-api.tencentcloud.com/mcp/v1`. For local stdio set `TCB_SITE=intl` + `TCB_REGION=ap-singapore`; for the `tcb` CLI set `TCB_IS_INTL=true`.
- **Domestic (国内站)** — `https://tcb-api.cloud.tencent.com/mcp/v1`. Both switches are the defaults, so nothing extra to declare.
- Two gaps to plan around: remote endpoints take **no `site` / `region` query parameter** (the hostname decides), and the international site has **no NoSQL / document-database tools**.
## Workflow
Every CloudBase task follows this three-stage process: