CtrlK
BlogDocsLog inGet started
Tessl Logo

api-contract-review

Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, actionable review workflow with clear sequencing, validation checkpoints, and appropriate progressive disclosure. The main defect is a verbatim-duplicated 'Internal parameters' subsection that wastes tokens and should be removed.

Suggestions

Remove the duplicate '### Internal parameters' section (the second copy, lines 75-87) — it is identical to the first and wastes context tokens.

Add a short example of the expected review-report format (e.g., one labeled finding entry) so the output shape is unambiguous.

Tighten the repeated documentation URLs (they appear in both Phase 2 and references/review-checklist.md); reference the checklist once instead of restating the entry points.

DimensionReasoningScore

Conciseness

Mostly efficient with lean lists and phases, but the '### Internal parameters' section is duplicated verbatim (lines 61-87 and 75-87), which is pure token waste that should be tightened.

3 / 5

Actionability

Provides concrete, executable guidance — specific file paths (mcp/src/tools/*), specific documentation URLs, enumerated finding labels, and explicit escalation rules; minor gaps in that no example report format is given.

4 / 5

Workflow Clarity

A clearly sequenced four-phase workflow with explicit validation checkpoints (documentation-first verification in Phase 2, cross-check in Phase 3, test-required escalation in Phase 4) plus a minimum self-check checklist and feedback loop ('if docs do not clearly support... stop short of guessing').

5 / 5

Progressive Disclosure

SKILL.md is a concise overview pointing to a single one-level-deep reference (references/review-checklist.md) that is clearly signaled in both the workflow and the routing table, and the referenced file exists and is well-organized.

5 / 5

Total

17

/

20

Passed

Description

87%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 strong, specific description that clearly states both the capability and the trigger conditions for a well-scoped niche. It avoids fluff and over-claims; the only minor gap is that the capability is expressed through one primary verb rather than a list of distinct actions.

DimensionReasoningScore

Specificity

Names the domain (CloudBase API wrappers, MCP tools, generated action metadata, docs) and lists concrete review dimensions (action names, parameters, casing, request shapes, missing contract tests), but frames them under a single primary verb ('auditing') rather than multiple distinct actions.

4 / 5

Completeness

Explicitly answers both what ('auditing CloudBase cloud API wrappers... for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests') and when ('Use when auditing... especially during periodic quality review or before preparing corrective PRs') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('auditing', 'CloudBase cloud API wrappers', 'MCP tools', 'contract tests', 'periodic quality review', 'corrective PRs') with good coverage, though a few common synonyms are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (CloudBase cloud API contract correctness review) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

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.