CtrlK
BlogDocsLog inGet started
Tessl Logo

relational-database-web-cloudbase

[Deprecated] Use when building frontend Web apps that talk to CloudBase Relational Database via @cloudbase/js-sdk – provides the canonical init pattern so you can then use Supabase-style queries from the browser. New environments should use PostgreSQL with app.rdb() — see postgresql-development skill instead.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is relational-database-web-cloudbase in TencentCloudBase/CloudBase-AI-Toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 concise, highly actionable skill with clear routing logic and executable examples, structured well as a standalone file. Its main weakness is the absence of validation/error-handling feedback loops around the destructive database operations it documents.

Suggestions

Add a validation or error-handling checkpoint for the insert/update/delete examples (e.g., check the returned `error` and retry/rollback) so destructive DB operations have a feedback loop and workflow_clarity can rise above the cap.

De-duplicate the PostgreSQL/`app.rdb()` routing guidance, which currently appears in both the 'Minimal checklist' and the 'Quick routing' sections — consolidate into one place to tighten conciseness.

Make the single shared `db` client lifecycle explicit (where to instantiate and export it in a real app) so the 'one shared db client' rule is actionable rather than only stated.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence with executable examples and no over-explanation of basic concepts, but routing guidance (the `app.rdb()`/PostgreSQL routing) is repeated across the Minimal checklist and Quick routing sections, leaving minor redundancy to trim.

4 / 5

Actionability

Fully executable copy-paste-ready code: install command, canonical init, and select/insert/update/delete examples, plus concrete routing rules keyed to specific trigger keywords that cover the common cases.

5 / 5

Workflow Clarity

The Activation Contract gives a clear use/read/avoid/mistakes/checklist sequence, but the skill includes destructive DB operations (insert/update/delete) with no validation or verification checkpoints; the database-operation cap holds workflow_clarity at 3.

3 / 5

Progressive Disclosure

Single self-contained SKILL.md (no bundle files exist in references/scripts/assets) with well-organized, clearly navigable sections; the simple-skill exception for a short skill with no external-reference need applies.

5 / 5

Total

17

/

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 defines a distinct niche and gives concrete trigger terms and a 'Use when' clause, while usefully flagging deprecation and the replacement skill. Minor tightening of action coverage would push specificity to a perfect score.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('building frontend Web apps that talk to CloudBase Relational Database', 'provides the canonical init pattern', 'use Supabase-style queries'), with minor coverage gaps since it is init-focused rather than comprehensive.

4 / 5

Completeness

Explicitly answers both 'what' ('provides the canonical init pattern so you can then use Supabase-style queries from the browser') and 'when' ('Use when building frontend Web apps that talk to CloudBase Relational Database via @cloudbase/js-sdk') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a user would say ('frontend Web apps', 'CloudBase Relational Database', 'Supabase-style queries', 'PostgreSQL', 'app.rdb()') with synonyms, though a few common phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (CloudBase browser SDK init with Supabase-style queries) and explicit routing away from PostgreSQL/`app.rdb()`, giving minimal conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
TencentCloudBase/CloudBase-AI-Toolkit
Reviewed

Table of Contents

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.