Passed 22 of 22 test cases with the skill, and 5 of 22 without it.
Without skill23%
With skill100%
Checks it passed that the model alone missed
The update operation filters rows using `.eq('id', ...)`.
The query uses `.range(...)` on `db.from('notifications')`.
The query uses `.eq('status', 'active')` to filter table rows.
and 16 more in the full report
17 fixed5 passed either way0 still failing0 broke
Pass-rate lift
+77 pp
Tokens
+2%
Agent turns
0%
Response time
-51%
Model gemini-3.6-flashMeasured 8/9/2026v222 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 17
Prompt
Write a frontend code snippet to update the `status` column to `'completed'` for a task with `id = 42` in the `tasks` table using the CloudBase JS SDK.
What was checked, without and with the skill
Checked
Without skill
With skill
The code uses `db.from('tasks').update({ status: 'completed' }).eq('id', 42)`.
Missed
Passed
case-15 · gemini-3.6-flash · 8/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md137 linessingle file
Sibling skills (local only)
Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/SKILL.md.
If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context.
CloudBase Relational Database Web SDK
Activation Contract
Use this first when
A browser or Web app must access CloudBase Relational Database through @cloudbase/js-sdk.
The task is specifically about frontend initialization and browser-side query usage.
Read before writing code if
You need to distinguish browser SDK usage from MCP database management or backend Node access.
The request mentions Supabase migration, shared frontend DB client, or browser-side table queries.
Then also read
MySQL SQL management and MCP operations -> ../relational-database-mcp-cloudbase/SKILL.md
Web auth/login -> ../auth-web-cloudbase/SKILL.md
General Web app setup -> ../web-development/SKILL.md
Do NOT use for
MCP-based SQL provisioning, schema changes, or permissions management.
Backend/Node service access.
Document database operations.
Common mistakes / gotchas
Initializing SDKs in an MCP management flow.
Treating app itself as the relational database client.
Re-initializing CloudBase in every component.
Mixing frontend browser access with admin-style schema mutations.