CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

69%

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/source/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 provides concrete, mostly executable guidance with a well-structured one-level reference split, but suffers from duplicated swagger/trigger sections, missing validation checkpoints, and a broken checklist.md reference. Tightening the redundancy and fixing the dead reference would raise it substantially.

Suggestions

Remove the duplicated OpenAPI Swagger section: the apiName list and searchKnowledgeBase instructions appear twice nearly verbatim; keep one authoritative copy.

Fix or inline the broken checklist.md reference — the "Minimal checklist" section requires reading it before implementation, but the file is absent from the bundle and from the Reference index.

Add an explicit validation checkpoint to the workflow, e.g., verify authentication with a low-risk GET before making bulk or destructive database write calls.

DimensionReasoningScore

Conciseness

The body is information-dense with no explanations of known concepts, but the full apiName list and searchKnowledgeBase instructions appear twice nearly verbatim ("How to use" step 4 and the "OpenAPI Swagger Documentation" section), and "When to use this skill" duplicates the Activation Contract triggers.

3 / 5

Actionability

Concrete, executable guidance throughout: exact base URL patterns with worked examples ("https://cloud1-abc.api.tcloudbasegateway.com"), an exact tool call ("searchKnowledgeBase({ mode: \"openapi\", apiName: \"mysqldb\" })"), and a filled Authorization header example. Complete request examples are deferred to the reference file, keeping it below copy-paste-comprehensive.

4 / 5

Workflow Clarity

A clear 4-step sequence exists (clarify scenario, determine base URL, set up auth, reference swagger), but there are no explicit validation checkpoints, and the "Minimal checklist" gate links to checklist.md, which is missing from the bundle — the required pre-implementation step is broken.

3 / 5

Progressive Disclosure

The split is genuinely good — overview in the body with a clearly signaled, real one-level-deep references/extended-guide.md — but the body references a nonexistent checklist.md and the "Reference index" section omits it, which is more than a minor organization gap.

3 / 5

Total

13

/

20

Passed

Description

70%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 description with an explicit and well-scoped use-when clause and clear differentiation from SDK/MCP alternatives. Its main weakness is a generic what-statement and limited natural-term coverage.

Suggestions

Enumerate 2-3 concrete capabilities in the what-statement (e.g., database REST operations, cloud function invocation, storage) instead of the generic "client guide".

Add natural trigger synonyms users would actually say, such as "REST API", "curl", or backend language names (Go, Python, Java).

DimensionReasoningScore

Specificity

Names the domain ("CloudBase official HTTP API") with one concrete action ("call CloudBase platform APIs over raw HTTP") but does not enumerate several specific capabilities (database, functions, storage, auth), matching the 1-2-concrete-actions anchor rather than the several-actions anchor.

3 / 5

Completeness

Both what and when are present, with an explicit trigger clause ("This skill should be used when backends, scripts, or non-SDK clients must call..."); the what-side ("HTTP API client guide") is generic, keeping it below the fully-concrete anchor 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage including "HTTP API", "backends", "scripts", "non-SDK clients", "raw HTTP", "SDK", and "MCP", though common user phrasings like "REST API", "curl", or specific languages (Go/Python/Java) are absent.

4 / 5

Distinctiveness Conflict Risk

The explicit contrast "instead of using a platform SDK or MCP management tool" carves a clear niche, but there is minor overlap risk with closely related CloudBase sibling skills (e.g., auth-specific HTTP endpoints).

4 / 5

Total

15

/

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.

Validation — 14 / 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

Path

config/source/skills/http-api-cloudbase/SKILL.md

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.