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.

56

Quality

65%

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

57%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 offers actionable, concrete guidance for calling CloudBase HTTP APIs and a clear sequenced workflow, but it is weakened by duplicated sections, a broken checklist.md reference, and missing validation checkpoints for destructive database operations.

Suggestions

Deduplicate the available-API-names list (it appears in both 'How to use this skill' step 4 and 'OpenAPI Swagger Documentation') and consolidate the overlapping 'Activation Contract' and 'When to use this skill' sections to tighten the body.

Add an explicit validation/verification checkpoint to the workflow (e.g., confirm the response status/schema against the swagger spec before treating a database write as succeeded), since the skill covers destructive REST operations.

Either ship the referenced checklist.md in the bundle or remove the 'Read [HTTP API Routing Checklist](checklist.md)' link, since the file is currently missing and the link is broken.

DimensionReasoningScore

Conciseness

Mostly efficient but carries notable redundancy: the available-API-names list appears twice and the 'Activation Contract' section overlaps heavily with 'When to use this skill', so it could be tightened.

3 / 5

Actionability

Provides concrete executable guidance such as `searchKnowledgeBase({ mode: "openapi", apiName: "mysqldb" })`, base URL templates with filled examples, and a concrete `Authorization: Bearer eymykey` header, with only minor gaps (full call examples live in the extended guide).

4 / 5

Workflow Clarity

The 4-step 'How to use this skill' workflow is sequenced, but it lacks explicit validation/verification checkpoints; because the skill covers database REST operations that can be destructive, workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

Structure with a signaled one-level reference to references/extended-guide.md is decent, but the body inlines content duplicated in the extended guide and references a non-existent checklist.md, leaving organization gaps.

3 / 5

Total

13

/

20

Passed

Description

73%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 clearly defines a distinct niche and provides explicit trigger guidance for when to use the skill over SDK or MCP alternatives. It is somewhat weaker on enumerating concrete capabilities, reading more as a guide label than an action list.

DimensionReasoningScore

Specificity

Names the domain ('CloudBase official HTTP API client guide') and one concrete action ('call CloudBase platform APIs over raw HTTP'), but does not enumerate multiple specific capabilities, so coverage is not comprehensive.

3 / 5

Completeness

Answers both what (HTTP API client guide for calling platform APIs) and when ('This skill should be used when backends, scripts, or non-SDK clients must call...'), with the when being explicit and specific, though the what reads more as a category label than a concrete capability list.

4 / 5

Trigger Term Quality

Includes natural developer-facing terms like 'backends', 'scripts', 'non-SDK clients', 'raw HTTP', and 'HTTP API' that users would plausibly say, though a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Explicitly carves out a clear niche ('raw HTTP instead of using a platform SDK or MCP management tool'), distinguishing it from SDK and MCP skills with minimal conflict risk.

5 / 5

Total

16

/

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.