CtrlK
BlogDocsLog inGet started
Tessl Logo

http-api-cloudbase

CloudBase official HTTP API client guide. This skill should be used when backends, scripts, or non-SDK clients must call CloudBase platform APIs over raw HTTP instead of using a platform SDK or MCP management tool.

61

Quality

73%

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 ./config/.claude/skills/http-api-cloudbase/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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.

The body is actionable and reasonably well-sequenced, giving Claude concrete URL templates, auth header formats, and tool-call examples. It loses points for duplicated content across sections and a dangling reference to a checklist.md file that does not exist in the bundle.

Suggestions

Add the missing checklist.md to the bundle (or remove/fix the 'Read [HTTP API Routing Checklist](checklist.md)' link) so the referenced navigation target actually exists.

De-duplicate the apiName list and the use-when guidance, which currently appear in both the 'Activation Contract'/'How to use' sections and the 'OpenAPI Swagger Documentation'/'When to use' sections.

Add an explicit validation/feedback step to the workflow (e.g., check the HTTP response status and error body, retry on auth failures) for the API-calling and database operations.

DimensionReasoningScore

Conciseness

The body is mostly efficient but duplicates material: the apiName list appears in both 'How to use this skill' and 'OpenAPI Swagger Documentation', and the 'When to use' guidance overlaps the 'Activation Contract' section, so it could be tightened.

3 / 5

Actionability

Provides concrete, executable elements — region-specific base-URL templates, an Authorization header format, and copy-paste searchKnowledgeBase({mode:"openapi",apiName:"..."}) calls with named APIs — with only minor gaps (no full end-to-end request example).

4 / 5

Workflow Clarity

A clear 4-step sequence (clarify scenario, determine base URL, set up auth, reference OpenAPI) is present with guardrails ('Do NOT use for', 'Common mistakes'), but an explicit response-validation/retry checkpoint is missing, keeping it just below a 5.

4 / 5

Progressive Disclosure

Sectioning is reasonable and the extended-guide reference is one level deep, but the body references 'checklist.md' ('Read [HTTP API Routing Checklist](checklist.md)') which is not present in the bundle, breaking navigation; significant overview content is also inlined.

3 / 5

Total

14

/

20

Passed

Description

82%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.

The description is well-constructed: it states a clear niche, gives an explicit use-when clause, and distinguishes itself from SDK and MCP alternatives. Its main limitation is that it names only one concrete action rather than enumerating several specific capabilities.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("call CloudBase platform APIs over raw HTTP") plus consumers (backends, scripts, non-SDK clients), but does not enumerate multiple distinct capabilities, so it matches the 'domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

Explicitly answers both what ("CloudBase official HTTP API client guide") and when ("This skill should be used when backends, scripts, or non-SDK clients must call CloudBase platform APIs over raw HTTP..."), with concrete trigger phrases in third-person voice.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ("HTTP API", "raw HTTP", "backends", "scripts", "non-SDK clients", "MCP management tool") with good coverage; a few synonyms or file-extension-style triggers are missing, fitting the 'good coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (official CloudBase platform APIs over raw HTTP) and explicitly contrasts it with platform SDKs and MCP management tools, minimizing conflict risk with sibling skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation14 / 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: 1 missing

Warning

Total

14

/

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.