CtrlK
BlogDocsLog inGet started
Tessl Logo

cloudbase-document-database-web-sdk

Use CloudBase document database Web SDK only for confirmed NoSQL collection work. Query, create, update, and delete document data; if the task mentions PostgreSQL / CloudBase PG / app.rdb(), route to postgresql-development instead.

63

Quality

75%

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/.claude/skills/cloudbase-document-database-web-sdk/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-organized, actionable skill body with executable examples and real validation guidance for destructive writes. Its main weakness is progressive disclosure: the routing section points to reference files that are absent from the bundle.

Suggestions

Ship the referenced bundle files (crud-operations.md, complex-queries.md, pagination.md, aggregation.md, realtime.md, geolocation.md, security-rules.md) under references/ so the routing links resolve.

De-duplicate the CMS permission pattern and the result._id gotcha, each currently described in both 'Common mistakes' and 'Working rules'.

Add a short inline update/delete example so all four CRUD verbs have executable coverage in SKILL.md before routing to the detail files.

DimensionReasoningScore

Conciseness

Mostly efficient, assumes Claude's competence (no basic-concept explanations), and uses lean code blocks; minor redundancy (the CMS rule pattern and the result._id gotcha each appear in two sections) keeps it just under level 5.

4 / 5

Actionability

Provides copy-paste-ready JS for init, query, create-with-ID, pagination, field selection, and error handling; update/delete and complex queries are only routed to files rather than shown inline, a minor coverage gap below level 5.

4 / 5

Workflow Clarity

A clear minimal checklist plus sequenced working rules, and it includes validation checkpoints ('do not treat a resolved promise as success', get() round-trip, rule-propagation wait-and-retry); not quite the explicit validate→fix→revalidate loop of level 5.

4 / 5

Progressive Disclosure

References are well-signaled in a dedicated 'Quick routing' section and are one level deep, but the referenced files (crud-operations.md, complex-queries.md, etc.) do not exist in any bundle directory, so navigation does not actually resolve — a structural gap beyond the minor organization issues tolerated at level 4.

3 / 5

Total

15

/

20

Passed

Description

78%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, distinctive description that pairs concrete CRUD actions with explicit positive and negative routing triggers. It cleanly separates this skill from sibling CloudBase skills and would rarely fire for the wrong task.

Suggestions

Add a 'Use when...' clause enumerating positive Web-frontend triggers (e.g., 'when the user mentions app.database(), db.collection(), .where(), or .watch() in a browser app') to lift completeness and trigger coverage to level 5.

Include natural synonyms/extensions (e.g., 'CloudBase Web SDK', '@cloudbase/js-sdk', 'CloudBase DB') to broaden trigger-term matching.

Mention realtime/aggregation/geolocation alongside CRUD so the capability list is comprehensive rather than CRUD-only.

DimensionReasoningScore

Specificity

Names four concrete CRUD actions ('Query, create, update, and delete document data') on a specific SDK surface, but omits other capabilities the skill covers (realtime, aggregation, geolocation), so it falls just below the comprehensive level-5 anchor.

4 / 5

Completeness

Explicitly answers 'what' (CRUD on the Web SDK) and 'when' ('only for confirmed NoSQL collection work', plus routing away from PG), satisfying both halves; the 'when' is partly exclusion-based rather than a rich positive trigger list, keeping it just under level 5.

4 / 5

Trigger Term Quality

Strong, natural trigger tokens a user would actually say — 'CloudBase document database Web SDK', 'NoSQL collection', and code-level signals like 'app.rdb()' — but lacks synonyms or explicit extensions that would push it to level 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (browser-side NoSQL via @cloudbase/js-sdk) and actively disambiguates from postgresql-development, Mini Program, and server-side access, giving minimal conflict risk as the level-5 anchor requires.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

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.