CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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). Also covers tcb login and site switching (国内站/国际站 via --intl or config isIntl), environment lifecycle (env create/modify/renew/delete/apikey/login/domain), tcb config and cloudbaserc.json sync, log search (logs search, CLS), metric monitoring (monitor), data model and PostgreSQL migrations (db model, db pg migration), sandbox/agent/integration management — do not default to tcb deploy.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is cloudbase-cli in TencentCloudBase/CloudBase-AI-Toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong overview-style SKILL.md: safety-first core principles, a crisp routing table over a real 19-file reference bundle, a validated quick workflow with error-recovery and a self-check checklist, and disciplined progressive disclosure. The two deductions are modest: some repetition of the MCP-fallback/routing message across sections (conciseness) and a body that defers all domain command syntax to references, leaving the top-level text slightly less copy-paste ready on its own (actionability).

Suggestions

Consolidate the MCP-fallback guidance into one section — it currently appears in the intro, Core Principle 8, and 'When to use' — and trim Principle 1's version-specific help-quirk enumeration (the unlisted-command list) into references/core.md to cut repeated and time-sensitive tokens.

Add one or two copy-paste-ready example commands for the most common tasks (e.g., listing functions or uploading a hosting file) directly in the Routing or Quick workflow section, so the body alone can execute a first concrete step before a reference is loaded.

Reduce routing redundancy: 'Route, do not improvise', 'Do NOT use for', 'How to use this skill' step 5, and the self-check's scope item all restate the same routing rules — fold them into the Routing table and one exclusion list.

DimensionReasoningScore

Conciseness

The body is dense and assumes CLI competence — no space is wasted explaining what CloudBase or CLI concepts are — but the MCP-fallback message repeats across the intro, Principle 8, and 'When to use', routing guidance appears in four places ('Route, do not improvise', the Routing table, 'Do NOT use for', and the self-check), and Principle 1's long enumeration of help quirks ("init, pull, new, open, rollback, self-update, monitor...") is time-sensitive detail that could be trimmed or moved to references/core.md. This matches 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place anchor.

4 / 5

Actionability

Core actions are concrete and executable ("tcb login --intl true|false", "tcb config set isIntl true|false", "tcb env use <envId>", "tcb docs search \"<keyword>\"", "--dry-run"), and the Quick workflow is runnable as written. It falls short of the copy-paste-ready anchor because per-domain command syntax (the common cases like listing functions or uploading files) lives entirely in the reference files, so the body alone has minor gaps a user's first concrete command depends on loading a reference.

4 / 5

Workflow Clarity

The Quick workflow is a clear five-step sequence with an explicit verification step ("Verify the result with the corresponding list/detail command") and reporting step; Principle 7 defines an error-recovery feedback loop (check exit code, read error, consult tcb docs, try a different approach); Principle 5 mandates dry-run plus explicit user confirmation before destructive ops; and the 'Minimum self-check' checklist closes the loop. This matches the anchor with explicit validation, feedback loops, and checklists — the destructive/batch validation cap does not apply since validation is present.

5 / 5

Progressive Disclosure

The bundle structure matches the routing design: all 19 files in the Reference index exist in references/, are one level deep, and the Routing table maps each task to exactly one file, with a mandatory first stop (references/core.md), an explicit 'load only what matches the task' instruction, and a 'stop loading more context' stopping rule. The body is a genuine overview with details correctly split out; the sibling-skill pointers (../cloudbase-platform, ../postgresql-development-cloudbase) are cross-skill handoffs with a stated fallback if missing, not buried or nested references — fitting the 'clear overview with well-signaled one-level-deep references' anchor over the score-4 'minor organization gaps' anchor.

5 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A dense, well-crafted description: it states the tool and its full capability surface, gives explicit and varied 'use when' triggers (including a thoughtful MCP-fallback condition), includes bilingual synonyms and command-level keywords, and marks boundaries. Its only weakness is length — the capability enumeration runs long — but every clause carries information rather than fluff.

DimensionReasoningScore

Specificity

"deploying cloud functions, CloudRun, storage, NoSQL/MySQL, static hosting, permissions, CORS/domains" plus "environment lifecycle (env create/modify/renew/delete/apikey/login/domain)", "log search", "metric monitoring", "data model and PostgreSQL migrations", and "sandbox/agent/integration management" lists many concrete, comprehensive actions — matching the 'multiple specific concrete actions; comprehensive coverage' anchor, not the score-4 anchor with coverage gaps.

5 / 5

Completeness

It explicitly answers 'what' ("CloudBase CLI resource management skill" with an enumerated capability list) and 'when' with a concrete "Use when..." clause covering deployment tasks, CI/CD/batch ops, CLI preference, and the first-session MCP fallback condition. Both are explicit with concrete triggers, matching the score-5 anchor rather than the score-4 anchor where 'when' could be more specific.

5 / 5

Trigger Term Quality

Natural user phrasings are covered with synonyms in two languages ("tcb", "CloudBase CLI", "云开发CLI", "Tencent CloudBase命令行", "国内站/国际站") and command-level terms ("logs search, CLS", "monitor", "db model, db pg migration"), alongside everyday phrases like "CI/CD and batch ops" and "when the user prefers CLI". This fits the comprehensive-with-synonyms anchor; the score-4 anchor's 'a few natural terms missing' understates the bilingual synonym coverage present.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (managing CloudBase resources specifically via the tcb CLI), and triggers are distinct — "when the user prefers CLI" and "first-session fallback when CloudBase MCP tools are not loaded" explicitly separate it from MCP and SDK alternatives, ending with a boundary note ("do not default to tcb deploy"). Minor overlap exists with sibling CloudBase SDK skills on generic phrases like 'deploy cloud functions', but the via-tcb scoping keeps conflict risk minimal, fitting the score-5 anchor over the score-4 'minor overlap' anchor.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

TencentCloudBase/CloudBase-AI-Toolkit

Path

config/.claude/skills/cloudbase-cli/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.