Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tencentcloudbase/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.
Passed 7 of 16 test cases with the skill, and 4 of 16 without it.
and 6 more in the full report
9 fixed1 passed either way8 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
The environment's authentication settings show `loginMethods.usernamePassword` is `false`. We need to support admin login credentials. What administrative API command must be issued?
| Checked | Without skill | With skill |
|---|---|---|
| Calls manageAppAuth with action patchLoginStrategy to enable usernamePassword. | Missed | Passed |
The instructions your model reads when the skill loads.
Every CloudBase task follows this three-stage process:
1. Exploration → Read the matching skill completely before writing any code.
Search for it if needed, then Read the full SKILL.md content.
Only start implementing after understanding the API patterns,
pitfalls, and correct usage from the skill document.
2. Implementation
├── 2a. Resource preparation → Prefer MCP to prepare backend resources
│ (enable auth providers, create database tables, configure storage domains,
│ set up security rules — before writing frontend code).
│ If MCP tools are missing in THIS session, configure MCP for next time and
│ use `tcb` CLI now (`./cloudbase-cli/SKILL.md`).
└── 2b. Frontend implementation → Write code, install deps, start server, test
3. Close-out → Run cloudbase-code-review, fix all errors, declare done
Key constraints:
tcb CLI after configuring MCP. Don't write frontend code that depends on uncreated resources (tables, auth providers, storage buckets) — the grader will fail.Only handle tasks that are part of building, integrating, or maintaining a CloudBase application — including UI design, spec planning, and other development activities when they are in service of a CloudBase app. If the request has no CloudBase application context at all, stop and tell the user this skill only covers CloudBase-based development.
searchKnowledgeBase(mode="skill", skillName=...), then Read the returned file path to get the full SKILL.md content. Do not start implementing based only on the search result summary — the full document contains API signatures, parameter schemas, and pitfall warnings.test cases passed, vs 4 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.