cloudbase-cli

Name: cloudbase-cli
Author: tencentcloudbase

github.com/tencentcloudbaseCloud & DevOps79238 installsUpdated today

About cloudbase-cli

cloudbase-cli is a skill for managing CloudBase resources with the `tcb` command-line tool. It is aimed at terminal, CI/CD, and batch workflows, and also serves as a fallback when CloudBase MCP tools are unavailable.

Key features

01Manage environments and resources
02Deploy and debug cloud services
03Inspect logs and metrics
04Configure access and authorization
05Use dry runs for destructive changes
06Verify changes with list and detail commands

Use cases

01Run CloudBase operations in CI/CD
02Manage resources before MCP is available
03Inspect cloud function or database logs
04Safely modify a selected environment

MCP support

This skill does not expose MCP tools. It provides a CLI fallback when CloudBase MCP tools are unavailable, while recommending MCP when those tools are already present unless CLI use is requested.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tencentcloudbase/skills --skill cloudbase-cli

After installing, type/cloudbase-cliin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

LICENSE.md

references/

access.md

agent.md

app.md

cloudrun.md

config.md

core.md

env.md

functions.md

hosting.md

integration.md

logs.md

lowcode.md

monitor.md

mysql.md

nosql.md

permission.md

sandbox.md

schema.md

storage.md

Details

From the project README

CloudBase CLI

Manage CloudBase resources via tcb CLI — deterministic, scriptable, auditable. Primary interface for CI/CD and batch ops; also the first-session fallback when MCP tools are not yet available in the conversation.

Sibling skills (local only)

Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/SKILL.md.

If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context.

Cross-cutting protocols (required before code changes or deployments):

Change Safety Protocol: ../cloudbase-platform/references/protocols/change-safety-protocol.md
Deployment Gate: ../cloudbase-platform/references/protocols/deployment-gate.md
MCP vs CLI fallback: ../cloudbase/references/tooling-fallback.md (packaged beside this skill as the cloudbase entry guideline)

Route, do not improvise — when a task belongs to another skill, hand over instead of guessing flags here:

PostgreSQL schema / RLS / pgstore → ../postgresql-development-cloudbase/SKILL.md
Data-model design (ER / Mermaid) → ../data-model-creation/SKILL.md
In-app SDK code (web / miniprogram / node) → the matching SDK skill

Core Principles

--help first — but its failure does NOT mean the command is missing. Run tcb <command> --help to check parameters and find official doc links. On current CLI versions many second-level commands reject --help (error: unknown option '--help'), while some accept -h, and tcb help <cmd> only works one level deep. Try -h, then tcb help <cmd>, then tcb docs search "<keyword>" — never conclude a command does not exist from a help error. tcb --help itself is a hand-maintained static list, so absence from it says nothing about lifecycle: init, pull, new, open, rollback, self-update, monitor, integration, service, cloudfunction, cloudrunfunction and run:deprecated are all registered yet unlisted. Absence from help ≠ deprecated, and "no marker" ≠ endorsed — the statuses differ: tcb monitor / tcb integration are officially supported (recommend normally), while tcb service and tcb cloudfunction / tcb cloudrunfunction are not recommended (product decision, no code marker). Full status table: references/core.md.
Confirm the site (国内站 / 国际站) as well as the envId. A credential from one site does not work on the other, and the failure looks like an auth error. One-off: tcb login --intl true|false; persistent: tcb config set isIntl true|false. Pick one mechanism and keep it consistent — see references/core.md / references/config.md.
Deployment Gate. Before any deployment, publish, custom domain, or CloudRun operation, you must first complete the checks in cloudbase-platform/references/protocols/deployment-gate.md.
Verify your work. After deploying or modifying any resource, run the corresponding list/detail command to confirm the change took effect.
Dry-run before destructive actions. Use --dry-run for delete/overwrite operations. Show the preview to the user and wait for explicit confirmation before executing.
Confirm environment first. Always verify envId with the user before operations. Run tcb env use <envId> to avoid accidentally modifying production.
Recover from errors, don't loop. If a command fails after 2-3 attempts, check the exit code ($?), read the error message, consult tcb docs search, and try a different approach.
First-session fallback, not MCP replacement. If CloudBase MCP tools are missing in this session, use this skill to unblock login/manage. Still configure MCP (plugin / mcp.json) so the next session can prefer MCP. When MCP tools are already available, prefer MCP unless the user asked for CLI/CI. Route deploy work through the domain reference table below — do not recommend tcb deploy.
No npm/npx. If Node/npm/npx are missing, tell the user to install Node.js LTS (or use the IDE marketplace MCP path) before retrying CLI/plugin install. See guideline tooling-fallback.md.

When to use this skill

Use when the user wants to manage CloudBase resources via command line, or when MCP is not usable yet:

First session / post-install: MCP not in the tool list, or just configured and needs restart → tcb login + the matching domain command now; leave MCP ready for next session
Deploy/debug cloud functions, static hosting, CloudRun services (via domain refs — not tcb deploy)
Manage storage, hosting, databases (NoSQL / MySQL / PostgreSQL), data models and migrations
Manage environments (create / package / renew / destroy, API Keys, login policy, safe domains, usage)
Configure resource authorization (tcb policy), roles, users, CORS, domains, routing
Search logs and read monitoring metrics
Manage sandbox, agent and integration instances
CI/CD scripting, batch operations, terminal-based resource management
User explicitly prefers CLI over MCP

Do NOT use for

SDK-based in-app integration (web/miniprogram/node) → use cloud-functions, cloudbase-document-database-web-sdk, auth-web-cloudbase, etc.
PostgreSQL schema design, RLS and migration workflow → postgresql-development-cloudbase
When CloudBase MCP tools are already available in this session and the user did not ask for CLI → prefer MCP
Console UI operations
CloudBase Agent SDK development → use cloudbase-agent-ts

How to use this skill (for a coding agent)

Always load references/core.md first — it covers authentication, site selection, environment switching, tcb docs queries, and error diagnosis.
Route to the correct reference using the Routing table below.
Load only the reference files that match the user's task. Do not preload all of them.
Stop loading more context once you have the workflow and command syntax for the current task.
If the task shifts to SDK/in-app code or PostgreSQL design, switch to the appropriate sibling skill instead.

Routing

User Task	Read
Login, site (国际站/国内站), env switching, `tcb docs`, error diagnosis	`references/core.md`
Create / modify / renew / destroy an environment, API Keys, login policy, safe domains, usage	`references/env.md`
`tcb config` (CLI settings, `cloudbaserc.json` sync), `tcb init` / `new` / `pull` / `open` / `validate` / `self-update` / `rollback`	`references/config.md`
Configure an AI tool + MCP + Skills (`tcb ai`)	`references/config.md`
Deploy/debug cloud functions, versions, provisioned concurrency, layers, triggers	`references/functions.md`
Deploy static site / SPA (preferred CLI web path)	`references/hosting.md`
Deploy CloudRun service, traffic/canary, versions, build & runtime logs	`references/cloudrun.md`
Experimental all-in-one web shorthand (`tcb deploy`, `tcb app build`) — avoid unless the user asks	`references/app.md`
Upload/download files, ACL rules, COS vs PG object storage	`references/storage.md`
NoSQL (MongoDB) database operations, collection dump	`references/nosql.md`
MySQL instance, SQL execution, backups, slow queries	`references/mysql.md`
Data model definitions, `sync-model-dts`, PostgreSQL migrations	`references/schema.md`
Search logs (CLS: functions / CloudRun / database / auth / LLM / gateway)	`references/logs.md`
Metric monitoring (functions, CloudRun, DB, hosting, auth, gateway…)	`references/monitor.md`
Resource authorization (`tcb policy`), roles, users	`references/permission.md`
CORS, custom domains, CDN cache purge, routing rules (`tcb routes`)	`references/access.md`
`tcb service` (HTTP 访问服务) — ⚠️ not recommended; read `access.md` for the `routes`/`domains` equivalent	`references/access.md`
WeDa / 微搭 low-code apps and components (`tcb lowcode`)	`references/lowcode.md`
Sandbox tools / instances / API keys	`references/sandbox.md`
Agent create / update / delete	`references/agent.md`
Integration instances (types, create, bind, delete)	`references/integration.md`
PostgreSQL schema / RLS / migration workflow (not just the CLI flags)	`../postgresql-development-cloudbase/SKILL.md`

Quick workflow

tcb login (check the site) → confirm envId with the user → tcb env use <envId>
Look up the command in the matching reference; verify syntax with tcb <command> --help (or -h)
Execute the command (with --dry-run for destructive ops)
Verify the result with the corresponding list / detail command
Report the outcome to the user

Minimum self-check

Loaded references/core.md before any domain module?
Confirmed the site (isIntl) and the target envId with the user?
Checked that --help failure was not misread as "command missing"?
Used --dry-run before destructive operations?
For PG environments: switched to the PostgreSQL skill instead of reusing NoSQL/MySQL paths?
Verified the result after each operation?
Stayed within CLI scope — did not drift into SDK code?

Reference index

All packaged reference files (required for skill lint reachability):

Comments

Markdown supported

Details

Author: tencentcloudbase
Repository: tencentcloudbase/skills
Category: Cloud & DevOps
Installs: 238
GitHub stars: 79

Report

More skills

All skills

lark-apps

open.feishu.cn

732.0k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

571.7k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

wizard

github.com/mattpocock

571.5k

Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.

azure-ai

github.com/microsoft

571.2k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.