CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

relational-database-web-cloudbase

[Deprecated] Existing CloudBase MySQL Web SDK only. Do not recommend MySQL for new relational apps — use postgresql-development and app.rdb(). Read this only when a browser app must keep using @cloudbase/js-sdk against an environment that already has MySQL.

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./config/source/skills/relational-database-web-cloudbase/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

61%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 lean, mostly executable skill with clear routing and good structure. Its weaknesses are duplicated routing/init content that bloats token cost, and CRUD examples that show destructive database operations without error-handling or validation checkpoints.

Suggestions

Merge the near-identical 'Canonical initialization' and 'Example: shared frontend DB client' code blocks into one, and collapse the three separate PostgreSQL-routing passages (Activation Contract, Minimal checklist, Quick routing) into a single routing section.

Add error handling to the insert/update/delete examples (e.g. destructuring { data, error } and checking error) to model validation for destructive database operations, matching the select example.

State what the browser auth step concretely requires, or inline the one-line pointer to ../auth-web-cloudbase/SKILL.md at the point where 'Handle login separately' appears.

DimensionReasoningScore

Conciseness

No over-explanation of concepts Claude already knows, but there is real duplication: the 'Canonical initialization' and 'Example: shared frontend DB client' code blocks are near-identical, and PostgreSQL routing ('the task says PostgreSQL, CloudBase PG, PG mode, app.rdb()...') appears three times across the Activation Contract, Minimal checklist, and Quick routing sections. Anchor 3 ('mostly efficient but could be tightened') fits better than 4, where trimming would be minor.

3 / 5

Actionability

Concrete and executable throughout — install command, canonical init snippet, and CRUD examples with Supabase-style chaining, plus error handling shown on the select example. Not anchor 5 because the update/delete examples lack error handling and auth wiring is deferred to a sibling skill with no inline pointer detail.

4 / 5

Workflow Clarity

The single core action (shared browser db client initialization) is unambiguous, but the skill demonstrates destructive database operations (db.from('posts').update(...).eq('id', 1) and .delete()) with no validation or error-recovery steps. Per the rubric, missing feedback loops for database operations caps workflow clarity at 3, taking precedence over the simple-skill exception.

3 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references to sibling skills via relative paths (../relational-database-mcp-cloudbase/SKILL.md, ../auth-web-cloudbase/SKILL.md, ../web-development/SKILL.md); no bundle files of its own are needed at this size. Not anchor 5 because at ~130 lines the duplicated routing and init content could be consolidated into one place.

4 / 5

Total

14

/

20

Passed

Description

73%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 well-gated deprecation description with an unusually explicit and tight 'when' clause and strong distinctiveness. Its main weakness is that the 'what' is a scope declaration rather than a list of the skill's concrete capabilities, and some natural trigger phrasings users would say are absent.

Suggestions

State 1-2 concrete actions the skill performs, e.g. 'Standardizes browser-side initialization of the CloudBase relational DB client (@cloudbase/js-sdk) with Supabase-style table queries' instead of the scope-only 'Existing CloudBase MySQL Web SDK only.'

Add natural trigger variations users would say, such as 'relational database', 'frontend database client', or 'Supabase migration', which the body already routes on but the description omits.

DimensionReasoningScore

Specificity

Names the domain ('CloudBase MySQL Web SDK', '@cloudbase/js-sdk') and a routing action ('use postgresql-development and app.rdb()'), but never states what the skill itself does — browser-side initialization, shared db client, Supabase-style queries are all absent. Anchor 3 fits: domain plus 1-2 concrete actions, not the several specific actions anchor 4 requires.

3 / 5

Completeness

An explicit 'when' clause is present ('Read this only when a browser app must keep using @cloudbase/js-sdk against an environment that already has MySQL'), and the 'what' is scoped ('Existing CloudBase MySQL Web SDK only'), but that 'what' is a scope label rather than a statement of actions, so it does not clearly match the anchor-5 example of both what and when with concrete actions.

4 / 5

Trigger Term Quality

Good natural keywords — 'browser app', 'MySQL', '@cloudbase/js-sdk', 'CloudBase' — that a user needing this skill would plausibly say. A few natural variations are missing ('relational database', 'frontend', 'Supabase migration'), keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The '[Deprecated]' marker plus 'Do not recommend MySQL for new relational apps' and the tightly gated read condition carve a clear, distinct niche with minimal conflict risk. Although it embeds the sibling skill's triggers ('postgresql-development', 'app.rdb()'), they appear only as redirect guidance, which strengthens rather than weakens distinctiveness.

5 / 5

Total

16

/

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.

Validation — 14 / 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

Path

config/source/skills/relational-database-web-cloudbase/SKILL.md

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.