cloudbase-all-in-one

Unified CloudBase execution guide for all-in-one skill installs. Use this first for CloudBase app tasks, especially existing apps with TODOs, fixed pages, or active handlers. Routes PostgreSQL / CloudBase PG / app.rdb() / queryPgDatabase / managePgDatabase work away from legacy NoSQL and old auth patterns.

Quality

81%

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

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable routing skill with concrete API calls, a clear three-stage workflow, and explicit validation/retry guardrails. It loses conciseness points to redundant restatements across sections and progressive-disclosure points because referenced files are external to an empty bundle and substantial detail is kept inline.

Suggestions

Consolidate the duplicated "prepare backend resources before frontend code" rule and the Legacy API STOP card with working rule 3 into a single authoritative statement to remove redundancy.

Move the inline per-task API recipe detail (e.g. the auth usernamePassword flow) into the referenced sibling skills, keeping the router to routing decisions and triggers.

If the referenced ./<skill>/SKILL.md and cloudbase-platform/references/protocols/*.md paths are part of this skill's bundle, add a references/ directory entry or verify they resolve so the one-level-deep structure is confirmable.

Dimension	Reasoning	Score
Conciseness	Assumes Claude's competence and avoids explaining basic concepts, but restates the same constraints across sections (the "prepare backend resources before frontend code" rule appears in both the Workflow key constraints and High-yield guardrails, and the Legacy API STOP card duplicates working rule 3), so it could be tightened.	2 / 3
Actionability	Provides copy-paste-ready, concrete guidance with exact tool calls and parameters such as queryAppAuth(action="getLoginConfig"), manageAppAuth(action="patchLoginStrategy", patch={ usernamePassword: true }), auth.signInWithPassword({ username, password }), and envQuery(action="domains"), matching the anchor for fully executable, specific examples.	3 / 3
Workflow Clarity	A clearly sequenced three-stage process (Exploration -> Implementation 2a/2b -> Close-out) with explicit validation and feedback loops: the cloudbase-code-review close-out, the change-safety protocol (declare -> confirm -> verify -> escalate after 3 repeats), and the "fails 2-3 times, stop and reroute" retry cap.	3 / 3
Progressive Disclosure	Uses a well-signaled routing table to point one level deep into sibling skills (./postgresql-development/SKILL.md, ./auth-web/SKILL.md, etc.), but this skill ships no bundle directory so those referenced paths are external and unverifiable, and a fair amount of detail that could live in the referenced skills is kept inline in the router.	2 / 3
	Total	10 / 12 Passed

Description

85%

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 description that gives explicit what/when guidance and concrete API routing for the CloudBase all-in-one entry skill. It is slightly technical in its trigger vocabulary, but otherwise clear, third-person, and actionable.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete API surfaces to route toward and away from ("Routes PostgreSQL / CloudBase PG / app.rdb() / queryPgDatabase / managePgDatabase work away from legacy NoSQL and old auth patterns"), matching the anchor for listing multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ("Unified CloudBase execution guide for all-in-one skill installs") and when ("Use this first for CloudBase app tasks, especially existing apps with TODOs, fixed pages, or active handlers"), matching the anchor for clearly answering both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Includes some naturally occurring terms ("CloudBase app tasks", "TODOs, fixed pages, or active handlers", "PostgreSQL") but leans technical/jargon-heavy with API names like app.rdb() that users would not naturally say, missing common variations — matching the anchor for some relevant keywords but missing variations.	2 / 3
Distinctiveness Conflict Risk	Carves a clear niche as the all-in-one CloudBase routing skill with a distinctive API vocabulary and an explicit "Use this first" trigger, making it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: TencentCloudBase/CloudBase-AI-Toolkit
Path: config/source/skills/SKILL.md
Commit: d329622

Reviewed: about 3 hours 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.