CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudbase-platform

CloudBase platform overview and routing guide. This skill should be used when users need high-level capability selection, platform concepts, console navigation, realtime (broadcast / presence / live database changes), or cross-platform best practices before choosing a more specific implementation skill.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable, well-structured routing skill with genuinely non-obvious platform knowledge, exact MCP invocations, and workflows that include validation checkpoints and error-recovery loops. Its main weakness is token efficiency: for an overview skill it inlines a lot of deep operational detail that belongs in reference files, which also slightly undercuts its progressive disclosure.

Suggestions

Move the manageEnv environment-creation deep detail (externalStorage, region handling, package family exclusions) out of SKILL.md into a reference file under references/, keeping only a one-line action summary plus the confirm="yes" rule inline.

Consolidate the repeated pointers to ../minimal-web-baas-demo/SKILL.md (appears in the routing list, best practices, and cross-collection sections) into a single routing entry to trim redundant tokens.

Move the console entry-point URL catalog to a reference file and keep only the URL pattern plus 2-3 most-used paths inline, preserving the live-console-over-docs rule.

DimensionReasoningScore

Conciseness

Mostly efficient and dense with CloudBase-specific knowledge Claude does not have (MCP tool actions, error-code semantics, shared-bucket behavior, plan names), but noticeably padded for an overview/routing skill: the manageEnv creation details (externalStorage, region, package family exclusions), the domain-management table's footnote-level detail, and repeated pointers to ../minimal-web-baas-demo/SKILL.md could be tightened or moved to references. Not 2 (no explanations of concepts Claude already knows; most tokens earn their place); not 4 (several sections carry over-explanation and repetition that could be trimmed).

3 / 5

Actionability

Fully executable guidance throughout: exact MCP calls with parameters (e.g. manageEnv(action="create", alias="my-env", packageId="baas_personal", resources=[...], confirm="yes")), copy-paste SDK init code, step-by-step public URL construction from EnvInfo.Storages[0].CdnDomain, a requirement-to-tool decision table, and concrete remediation commands (manageGateway(action="disableRoute", ...)). Matches the 5 anchor: copy-paste ready commands covering the common cases.

5 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with explicit validation checkpoints and feedback loops: the 4-step error-code routing procedure (extract code → searchDocs → fallback pages → never assert from memory), the diagnose-before-act InsufficientBalance flow (run manageEnv(action="usage"), read account balance, four-cause decision table), confirm="yes" gates on all paid operations with warnings to repeat region/externalStorage on the confirming call, and permission-change retry guidance (retry after ~30s, re-check rule shape on failure). Matches the 5 anchor.

5 / 5

Progressive Disclosure

The four protocol references (change-safety-protocol.md, deployment-gate.md, deployment-share.md, sensitive-runtime-data-protection.md) are real files in references/protocols/, one level deep, clearly signaled at first mention, and consolidated in a closing "Reference index"; the body is well-sectioned with headers and a clear activation contract. Not 5: substantial deep detail (the domain-management table, environment creation recipes, the full console URL catalog) is inlined in SKILL.md where a router skill would move bulk detail into reference files, and some referenced sibling paths live outside this skill's bundle.

4 / 5

Total

17

/

20

Passed

Description

83%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 strong router-skill description: third-person, explicit about both what it does and when to use it, with concrete trigger areas covering platform concepts, console navigation, realtime, and cross-platform best practices. Its only weaknesses are the slightly abstract "overview and routing guide" framing and minor trigger-synonym gaps, plus inherent overlap with the sibling skills it routes to.

DimensionReasoningScore

Specificity

Lists several concrete capability areas ("high-level capability selection, platform concepts, console navigation, realtime (broadcast / presence / live database changes), or cross-platform best practices") rather than vague claims, but "overview and routing guide" is abstract and the action list is scope-level rather than a comprehensive inventory of concrete actions. Above the 3 anchor (more than 1-2 concrete actions), below the 5 anchor (minor gaps in coverage and comprehensiveness).

4 / 5

Completeness

Explicitly answers both: what ("CloudBase platform overview and routing guide") and when ("This skill should be used when users need high-level capability selection, platform concepts, console navigation, realtime..., or cross-platform best practices before choosing a more specific implementation skill"). The when-clause contains concrete trigger phrases in third-person voice, matching the 5 anchor exactly; not 4 because the when is both explicit and specific.

5 / 5

Trigger Term Quality

Good natural keyword coverage — "CloudBase", "platform", "console navigation", "realtime", "broadcast / presence / live database changes", "cross-platform best practices" — terms users would plausibly say. A few natural phrasings or synonyms (e.g., "which CloudBase service", "WeChat mini program", "hosting vs storage") are missing, so it sits between the 4 and 5 anchors, closer to 4.

4 / 5

Distinctiveness Conflict Risk

Clear niche as the pre-implementation router, explicitly scoped "before choosing a more specific implementation skill", with distinct triggers (capability selection, console navigation, realtime). Minor overlap risk remains because, as an umbrella skill, it can be invoked for tasks the sibling implementation skills handle better. Not 5: the overlap with closely related CloudBase sibling skills is real; not 3: the scoping language keeps it mostly distinct.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 4 deeper-than-1-level, 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 9 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository

TencentCloudBase/CloudBase-AI-Toolkit

Path

config/.claude/skills/cloudbase-platform/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.