CtrlK
BlogDocsLog inGet started
Tessl Logo

cloudbase-platform

CloudBase platform overview and routing guide. This skill should be used when users need high-level capability selection, platform concepts, console navigation, or cross-platform best practices before choosing a more specific implementation skill.

56

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./config/.claude/skills/cloudbase-platform/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 comprehensive, highly actionable CloudBase platform router/reference with concrete commands, clear routing, and verified external references. Its main weakness is length and redundancy — the domain-management distinction is covered twice and the inline console-URL catalog is large — which constrains conciseness.

Suggestions

De-duplicate the security-domain vs custom-domain guidance: keep the decision table in 'Domain Management Tools' and reduce the 'Common mistakes' bullet to a one-line pointer.

Move the exhaustive console URL catalog (entries 1–13) into a separate references/console-urls.md file and summarize the base pattern inline.

Convert remaining conceptual auth bullets into concrete minimal snippets (e.g. show the auth.getSession() proof call) to push actionability to the top band.

DimensionReasoningScore

Conciseness

Mostly domain-specific and useful, but the ~500-line body has notable redundancy (domain management covered in both 'Common mistakes' and the 'Domain Management Tools' table) and an exhaustive inline console-URL catalog that could be tightened.

3 / 5

Actionability

Abundant concrete, copy-paste-ready commands and code (manageEnv/manageGateway actions, SDK init snippets, full console URLs); a few sections stay conceptual ('Use SDK built-in authentication') without full executable detail, keeping it just below the top anchor.

4 / 5

Workflow Clarity

Clear sequencing via the numbered 'How to use this skill' list, the Activation Contract routing flow, and a domain-management decision table with key indicators; validation is signaled through referenced protocols and a permissions retry feedback loop rather than fully inline checkpoints.

4 / 5

Progressive Disclosure

Good structure with well-signaled one-level-deep references (the three protocols in references/protocols/ are real and indexed), plus routing to sibling skills; some inline reference material (console URL catalog, permission tables) could be split into separate files.

4 / 5

Total

15

/

20

Passed

Description

67%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 solid, third-person description that clearly states what the skill does and when to use it, with explicit trigger guidance. It is held back from the top band by an abstract 'what' clause and trigger terms that favor developer jargon over natural user phrasing.

Suggestions

Enumerate concrete actions in the 'what' clause (e.g. 'routes users to the right CloudBase capability, explains platform concepts, navigates console pages') instead of the abstract 'overview and routing guide'.

Add natural user-voiced trigger terms and synonyms (e.g. 'CloudBase', 'hosting', 'storage', 'auth', 'cloud functions', 'database options') alongside the technical phrasing.

Reinforce distinctiveness by explicitly contrasting with the sibling implementation skills it routes to.

DimensionReasoningScore

Specificity

Names the domain ('CloudBase platform overview and routing guide') plus several concrete capabilities — 'high-level capability selection, platform concepts, console navigation, cross-platform best practices'; gaps remain versus a fully comprehensive action list, so it sits just below the top anchor.

4 / 5

Completeness

Explicitly answers both what ('CloudBase platform overview and routing guide') and when ('This skill should be used when users need...'); the 'what' is somewhat abstract rather than action-enumerated, keeping it just below the top anchor.

4 / 5

Trigger Term Quality

Relevant phrases like 'capability selection', 'platform concepts', 'console navigation' appear, but these lean technical and miss common natural synonyms a user would voice; coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

Niched to CloudBase platform-level routing and explicitly framed as the step 'before choosing a more specific implementation skill', minimizing conflict; minor overlap remains with sibling CloudBase implementation skills.

4 / 5

Total

15

/

20

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (504 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 3 deeper-than-1-level

Warning

referenced_paths_exist

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

Warning

Total

12

/

16

Passed

Repository
TencentCloudBase/CloudBase-AI-Toolkit
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.