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.

63

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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

77%

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

The body is highly actionable with concrete code and tool calls, and its workflows carry explicit validation checkpoints. It loses points for verbosity from repetition and for keeping dense reference material inline rather than splitting it into bundled files.

Suggestions

De-duplicate the security-domain vs custom-domain guidance so it lives in one place rather than both 'Common mistakes' and the dedicated table section.

Move the long Console Management entry-point catalog and Database Permissions detail into reference files, leaving SKILL.md as a concise overview that links to them.

Collapse the per-sibling-skill standalone fallback URLs into a single fallback convention note to reduce repeated boilerplate.

DimensionReasoningScore

Conciseness

Mostly efficient and dense with CloudBase-specific knowledge Claude would not know, but it is verbose: the security-vs-custom-domain distinction is repeated in both 'Common mistakes' and a full table section, and the standalone fallback URLs are restated inline for every sibling skill.

2 / 3

Actionability

Provides copy-paste-ready executable guidance throughout: concrete SDK init code ('import cloudbase from "@cloudbase/js-sdk"; const app = cloudbase.init({ env: "your-full-env-id" })') and specific MCP calls with parameters ('manageEnv(action="create", alias="my-env", packageId="baas_personal", ...)').

3 / 3

Workflow Clarity

Sequences are explicit with validation checkpoints: the configuration workflow ('Create collection -> Configure security rules -> Write code -> Test'), the 'confirm="yes"' gates on paid operations, and the mandated Change Safety Protocol / Deployment Gate checks before code changes and deployments.

3 / 3

Progressive Disclosure

It routes one level deep to sibling skills and signals two real protocol reference files (both present on disk), but the body itself is a large monolithic wall of inline reference content (13 console entry points, permission tables, auth details) that could live in separate reference files.

2 / 3

Total

10

/

12

Passed

Description

75%

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

The description answers both what and when with an explicit use-trigger and a distinct routing niche. It is held back from a top score by jargon-leaning trigger terms and a lack of multiple concrete, named actions.

Suggestions

Replace abstract phrasing like 'platform concepts' and 'cross-platform best practices' with natural user terms such as 'which CloudBase service or tool to use'.

Add a few concrete capability words (hosting, storage, auth, cloud functions, databases) so the action list reads as specific actions rather than 'overview and routing guide'.

DimensionReasoningScore

Specificity

Names the domain ('CloudBase platform overview and routing guide') and some actions ('capability selection', 'console navigation') but stops short of listing multiple concrete actions; 'overview and routing guide' is abstract rather than enumerating specific capabilities.

2 / 3

Completeness

Clearly answers both 'what' ('CloudBase platform overview and routing guide') and 'when' with an explicit trigger clause ('This skill should be used when users need high-level capability selection... before choosing a more specific implementation skill').

3 / 3

Trigger Term Quality

Includes some relevant terms a user might say ('capability selection', 'console navigation') but leans on jargon ('platform concepts', 'cross-platform best practices') and misses common natural variations like 'which CloudBase service to use' or specific service names.

2 / 3

Distinctiveness Conflict Risk

The 'before choosing a more specific implementation skill' framing carves out a clear routing/overview niche that is unlikely to conflict with the implementation skills it hands off to.

3 / 3

Total

10

/

12

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: 2 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 2 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.