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.

64

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugin/cloudbase/skills/cloudbase-platform/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 dense, highly actionable platform-routing skill with concrete tool calls and well-signaled references to sibling skills and protocols. Its main weakness is length and redundancy across overlapping routing/usage sections, with some content that could live in separate reference files.

Suggestions

Consolidate the overlapping 'Activation Contract', 'When to use this skill', and 'How to use this skill' sections to reduce redundancy and token cost.

Move the large Domain Management Tools table and Console entry-point list into a dedicated reference file, keeping only the routing summary inline.

Surface a short 'validate before deploy' checklist inline rather than only delegating to the external protocols, to make destructive-op checkpoints explicit.

DimensionReasoningScore

Conciseness

Mostly information-dense with platform-specific tool actions and parameters Claude would not know, but the body is long with some redundancy between the 'Activation Contract', 'When to use this skill', and 'How to use this skill' sections that could be tightened.

3 / 5

Actionability

Provides fully executable, copy-paste-ready tool calls with concrete parameters (e.g. manageEnv(action="create", ...), SDK init snippets) covering the common cases.

5 / 5

Workflow Clarity

Multi-step processes (error-code routing, recording results, permission configuration) are clearly sequenced with the confirm="yes" checkpoint for paid/destructive ops and externalized validation protocols, though some validation detail is delegated rather than inline.

4 / 5

Progressive Disclosure

Good structure with a clear reference index and one-level-deep pointers to sibling skills and protocol files; however a large amount of detail (domain table, console entry points) is inlined in the overview file rather than split out.

4 / 5

Total

16

/

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 clear, third-person description that states both what the skill does and when to use it, with concrete trigger phrases. It is mostly specific and distinct, with only minor gaps in keyword coverage and concrete action listing.

Suggestions

Add a few more natural user phrasings (e.g. 'which CloudBase service should I use', 'CloudBase vs ...') to broaden trigger coverage.

Consider listing one or two more concrete actions to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (CloudBase platform overview/routing) and several concrete routing tasks — 'high-level capability selection, platform concepts, console navigation, or cross-platform best practices' — but stops short of comprehensive coverage of concrete manipulation actions.

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...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('capability selection', 'console navigation', 'cross-platform best practices') that users would plausibly say, though a few common synonyms and concrete platform terms are missing.

4 / 5

Distinctiveness Conflict Risk

Scoped clearly as the overview/routing layer 'before choosing a more specific implementation skill', giving it a distinct niche, though the many sibling CloudBase skills leave minor overlap risk.

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.

Validation13 / 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

Warning

referenced_paths_exist

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

Warning

Total

13

/

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.