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

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugin/cloudbase/skills/http-api-cloudbase/SKILL.md

Quality

Content

61%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 well-structured with concrete, actionable guidance and a clean one-level reference to extended-guide.md, but it suffers from triple repetition of the API-name list and lacks validation checkpoints in a workflow that covers destructive database operations.

Suggestions

Deduplicate the available-API-names list — state it once and reference it, instead of repeating mysqldb/nosql/functions/auth/cloudrun/storage/ai_model three times across 'How to use', 'OpenAPI Swagger Documentation', and the example.

Add an explicit validation/check verification step to the 'How to use this skill' workflow (e.g., confirm a 200/2xx response and verify affected rows) since the skill covers destructive UPDATE/DELETE database calls.

Resolve the dangling `checklist.md` reference: either ship the file in the bundle or remove/fix the link in the 'Minimal checklist' section.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basic concepts, but the available-API-names list (mysqldb, nosql, functions, auth, cloudrun, storage, ai_model) is repeated three times and the 'Activation Contract' / 'When to use this skill' sections overlap heavily, so it could be tightened.	3 / 5
Actionability	Provides executable guidance — the `searchKnowledgeBase({ mode: "openapi", apiName: "mysqldb" })` call, concrete base URL examples (https://cloud1-abc.api.tcloudbasegateway.com), and a worked `Authorization: Bearer eymykey` header — with full curl examples delegated to extended-guide.md, leaving only minor gaps inline.	4 / 5
Workflow Clarity	The 4-step 'How to use this skill' sequence is clear, but because the skill drives destructive/batch database CRUD (UPDATE/DELETE) and the main workflow has no validation or verification checkpoints, the workflow-clarity cap of 3 applies.	3 / 5
Progressive Disclosure	SKILL.md is a well-structured overview pointing one level deep to references/extended-guide.md with a clear reference index, but the 'Read [HTTP API Routing Checklist](checklist.md)' link references a file that is not present in the bundle, a minor navigation gap.	4 / 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 clear, third-person, and explicitly covers both what the skill does and when to use it, with strong distinctiveness from SDK/MCP alternatives. Its only weakness is that it names a single concrete action rather than enumerating multiple capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('CloudBase official HTTP API client') and one concrete action ('call CloudBase platform APIs over raw HTTP') with the actors (backends, scripts, non-SDK clients), but does not enumerate multiple distinct actions, so it sits at the '1-2 concrete actions' anchor rather than the comprehensive level above.	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...') using third person and concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural trigger terms a user would say ('HTTP API', 'raw HTTP', 'backends, scripts') with good coverage, though phrasings like 'non-SDK clients' and 'MCP management tool' lean technical and a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (raw HTTP to official CloudBase APIs) and explicitly distinguishes itself from platform SDKs and MCP management tools, minimizing overlap with sibling skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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: plugin/cloudbase/skills/http-api-cloudbase/SKILL.md
Commit: ef9f182

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.