# Build CloudBase Relational Database Web Clients

Browser apps need a clear CloudBase relational database setup path. This skill shows the shared web SDK client and Supabase-style query flow.

## Install

```bash
npx skillstore add tencentcloudbase/relational-database-web-cloudbase
```

## Metadata

- Status: approved
- Slug: tencentcloudbase-relational-database-web-cloudbase
- Version: 2.23.8
- Author version: 2.23.8
- Skillstore revision: r1
- Version status: valid
- Tree hash: 893f7d1ffac1c79b0f1970749ce024e69f75d414f9ed3cb2ae6b7f301a48b96b
- Author: tencentcloudbase
- GitHub username: tencentcloudbase
- License: MIT
- Repository: https://github.com/tencentcloudbase/skills/tree/main/skills/relational-database-web
- Ref: 24b2fe42a456262f3fd0fb3df72e12d9ed2c32ec
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: scripts, external\_commands, network, filesystem
- Quality score: 72
- Public page: https://skillstore.pages.dev/skills/tencentcloudbase-relational-database-web-cloudbase
- Manifest: https://skillstore.pages.dev/api/skills/tencentcloudbase-relational-database-web-cloudbase/manifest

## Capabilities

- Identifies when browser apps should use the CloudBase relational database web SDK.
- Shows the package needed for @cloudbase/js-sdk setup.
- Defines one shared CloudBase app and relational database client pattern.
- Explains that authentication should be handled before table access.
- Routes schema management, MCP operations, backend access, and PostgreSQL tasks to other skills.
- Provides Supabase-style select, insert, update, and delete examples.

## Use Cases

- Create a Shared Web Client: Set up one CloudBase app and relational database client for a frontend project.
- Migrate Browser Queries: Move Supabase-style browser table queries into CloudBase relational database patterns.
- Route Database Tasks: Separate browser data access from schema management, MCP operations, backend access, and PostgreSQL work.

## Prompt Templates

### Basic Setup

```
Show me the basic CloudBase relational database setup for a browser app.
```

### Shared Client

```
Create a shared frontend database client using @cloudbase/js-sdk and explain where auth belongs.
```

### Supabase Migration

```
Plan a Supabase browser query migration to CloudBase relational database patterns.
```

### Architecture Review

```
Review my frontend data access plan and separate browser queries from MCP schema management.
```

## Limitations

- Does not provision MySQL instances or modify schemas.
- Does not cover backend Node service access.
- Does not replace CloudBase authentication setup.
- Assumes the browser app can use @cloudbase/js-sdk.

## Best Practices

- Create one shared frontend database client and reuse it across components.
- Handle authentication before relational table access.
- Keep schema changes and privileged administration outside browser code.

## Anti Patterns

- Do not initialize CloudBase inside every component.
- Do not use this skill for MCP database management.
- Do not mix PostgreSQL semantics with the CloudBase web relational flow.

## Security Audit

- Audited at: 2026-07-09T16:48:37.616\+00:00
- Summary: Most static findings are Markdown false positives from inline code, code fences, and fixed sibling references. The raw fallback URLs are a real concern because they can direct agents to mutable external instructions outside the reviewed package. No evidence of prompt injection, credential exfiltration, or automatic command execution was found.

## Stats

- Views: 0
- Downloads: 5
- Favorites: 1
- Popularity score: 0