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

86%

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

85%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 highly actionable, well-structured router skill with concrete MCP/CLI guidance, an explicit three-stage workflow with validation checkpoints, and clean progressive disclosure via a routing table. The main weakness is repetition of the resource-prep and legacy-API guardrails across multiple sections, which hurts token efficiency.

Suggestions

Consolidate the "prepare backend resources before frontend code" guidance into one section and cross-reference it from the others instead of restating it in Workflow, Activation Contract, and Working rules.

Merge the duplicated legacy-API STOP-card content (Working rules item 4 vs. the standalone STOP card) into a single canonical block to remove redundancy.

Trim the repeated "Use this first / read the relevant skill before writing code" framing to one authoritative statement to tighten token usage.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and dense with CloudBase-specific knowledge Claude does not have, but the "prepare backend resources before frontend code" guardrail and legacy-API STOP-card concept recur across Workflow, Activation Contract, and Working rules, so it could be tightened; not a 4 due to this notable repetition.	3 / 5
Actionability	Fully executable guidance with specific MCP calls (queryEnv(action=list, alias=...), manageAppAuth(action="patchLoginStrategy", patch={usernamePassword: true}), auth.signInWithPassword({username, password})), file paths (src/lib/backend.*), env vars (TCB_SITE=intl), and endpoint URLs covering the common cases.	5 / 5
Workflow Clarity	A clear three-stage sequence (Exploration -> 2a/2b Implementation -> Close-out) with explicit validation and feedback loops (Stage 3 close-out, Change Safety Protocol verify-after-change, Deployment Gate, stop-retry-after-2-3-failures); destructive/batch ops have validation so no cap applies.	5 / 5
Progressive Disclosure	Clear router overview with a well-signaled one-level-deep reference table ("Route quickly to the minimum needed skills") pointing to sibling SKILL.md files and protocol files, with content appropriately split and easy to navigate.	5 / 5
	Total	18 / 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 what the skill does and when to use it, with concrete CloudBase/PostgreSQL trigger terms in third-person voice. Minor gaps in trigger synonym coverage and action phrasing keep it just below perfect on specificity and trigger quality.

Dimension	Reasoning	Score
Specificity	Names concrete routing actions against specific tools ("Routes PostgreSQL / CloudBase PG / app.rdb() / queryPgDatabase / managePgDatabase work away from legacy NoSQL and old auth patterns"), with minor coverage gaps; not a 5 because the actions are framed as routing-away rather than a comprehensive action list.	4 / 5
Completeness	Clearly answers both what ("Unified CloudBase execution guide for all-in-one skill installs") and when with concrete trigger phrases ("Use this first for CloudBase app tasks, especially existing apps with TODOs, fixed pages, or active handlers"), in third person.	5 / 5
Trigger Term Quality	Good keyword coverage (CloudBase, PostgreSQL, CloudBase PG, TODOs, auth, NoSQL) with some natural user phrases; not a 5 because common synonyms and file extensions are missing.	4 / 5
Distinctiveness Conflict Risk	Clear CloudBase all-in-one router niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 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: 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.