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 keep using @cloudbase/js-sdk against an environment that already has CloudBase MySQL.
• Do not choose this skill for a new relational app. New relational Web work uses postgresql-development-cloudbase and app.rdb().

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 management, schema changes, or permissions management (provisioning is not offered through MCP).
• 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.

Minimal checklist