Cloudbase Cli

OrganizationPopular

TencentCloudBase

cloudbase-cli

CloudBase CLI (tcb, 云开发CLI, Tencent CloudBase命令行) resource management skill. Use when deploying cloud functions, CloudRun, storage, NoSQL/MySQL, static hosting, permissions, CORS/domains via tcb; for CI/CD and batch ops; when the user prefers CLI; or as the first-session fallback when CloudBase MCP tools are not loaded yet (after install/config, before IDE restart). Covers tcb login (device code for Tencent Cloud accounts; --cloudbase-api-key -e for environment API Key without an account; --apiKeyId/--apiKey for CI) and domain commands (fn/hosting/cloudrun/…) as MCP auth/manage parity — do not default to tcb deploy.

Overview

Publisher	TencentCloudBase
Repository	`CloudBase-AI-Toolkit`
Skill name	`cloudbase-cli`
Stars	1.1K
Forks	141
Bundled files	10
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
10 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by TencentCloudBase on GitHub. Read the source before you install it.

Installation

Install the Cloudbase Cli AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/config/source/skills/cloudbase-cli

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/TencentCloudBase/CloudBase-AI-Toolkit.git /tmp/CloudBase-AI-Toolkit
mkdir -p .claude/skills
cp -r /tmp/CloudBase-AI-Toolkit/config/source/skills/cloudbase-cli .claude/skills/cloudbase-cli

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cloudbase Cli in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cloudbase Cli on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cloudbase Cli is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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)

Core Principles

--help first — never guess commands. tcb CLI changes between versions. Before using any command for the first time, run tcb <command> --help to check parameters and discover official doc links.
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)
Configure permissions, CORS, domains, routing
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.
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, environment switching, tcb docs queries, and error diagnosis.
Route to the correct domain reference using the Routing table below.
Load only the one reference file that matches the user's task. Do not preload all references.
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, switch to the appropriate SDK skill (e.g., cloud-functions, cloudbase-document-database-web-sdk) instead.

Routing

User Task	Read
Login, env switching, tcb docs, error diagnosis	`references/core.md`
Deploy/debug cloud functions	`references/functions.md`
Deploy static site / SPA (preferred CLI web path)	`references/hosting.md`
Deploy CloudRun service	`references/cloudrun.md`
Experimental all-in-one web shorthand (`tcb deploy`) — avoid unless user explicitly asks	`references/app.md`
Upload/download files, ACL rules	`references/storage.md`
NoSQL (MongoDB) database operations	`references/nosql.md`
MySQL database operations	`references/mysql.md`
Roles, policies, access control	`references/permission.md`
CORS, custom domains, routing rules	`references/access.md`

Quick workflow

tcb login → confirm envId with user → tcb env use <envId>
tcb <command> --help to verify syntax
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 target envId with the user?
Used --help for unfamiliar commands?
Used --dry-run before destructive operations?
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):

access.md
app.md
cloudrun.md
core.md
functions.md
hosting.md
mysql.md
nosql.md
permission.md
storage.md

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cloudbase Cli AI skill do?

Why use Cloudbase Cli on TypingMind?

Because you install it once and use it with any model. Cloudbase Cli is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cloudbase Cli in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/TencentCloudBase/CloudBase-AI-Toolkit/tree/main/config/source/skills/cloudbase-cli. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cloudbase Cli?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cloudbase Cli?

As many as you like. As long as a model supports skills, you can use Cloudbase Cli with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cloudbase Cli AI skill free?

Yes. It is published on GitHub by TencentCloudBase under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Diagnosing Bugs

mattpocock

CommunityPopular

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

Implement

Implement a piece of work based on a spec or set of tickets.

Improve Codebase Architecture

mattpocock

CommunityPopular

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

Prototype

Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

CloudBase CLI

Sibling skills (local only)

Core Principles

When to use this skill

Do NOT use for

How to use this skill (for a coding agent)

Routing

Quick workflow

Minimum self-check

Reference index

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now