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.

The body is highly actionable with executable code and concrete gotchas, and its decision/workflow guidance is strong with write-validation present. Its weaknesses are repeated gotchas that bloat the token budget and progressive-disclosure references that point to non-existent files.

Suggestions

Ship the referenced bundle files (crud-operations.md, complex-queries.md, pagination.md, aggregation.md, realtime.md, geolocation.md, security-rules.md) or remove the dead 'Quick routing' links so navigation resolves.

Dedupe the repeated gotchas — state result._id and the CMS CUSTOM rule once (e.g. in Working rules) and reference them from elsewhere instead of restating them.

Consolidate write-validation into a single explicit checkpointed write workflow so validation steps are not scattered across Common mistakes and Working rules.

DimensionReasoningScore

Conciseness

Mostly efficient and free of generic concept explanations, but the same gotchas are repeated across sections (result._id appears in Common mistakes, Working rules #5, and Quick examples; the CMS CUSTOM rule appears in both Common mistakes and Working rules #3), so it could be tightened; not a 4 due to this redundancy.

3 / 5

Actionability

Fully executable, copy-paste-ready code for init, query, create, pagination, field selection, and error handling, plus concrete patterns (e.g. the CMS rule expression 'get(\'database.user_roles.\' + auth.uid).role == \'admin\' || doc.authorId == auth.uid') covering common cases.

5 / 5

Workflow Clarity

Clear Activation Contract with sequenced 'Use this first when / Read before writing code if / Then also read' guidance, a Minimal checklist, and write-validation steps (check updated/deleted and code/message, get() round-trip after writes); not a 5 because validation is scattered across sections rather than presented as one clean linear sequence with explicit checkpoints.

4 / 5

Progressive Disclosure

Good in-file structure with a dedicated 'Quick routing' section signaling one-level-deep references (crud-operations.md, complex-queries.md, etc.), but none of the referenced files (./crud-operations.md, ./security-rules.md, and the sibling ../auth-web-cloudbase/SKILL.md etc.) actually exist in the bundle, so the navigation is broken.

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.

The description is specific, actionable, and strongly distinct from sibling skills thanks to explicit routing guidance. Its main weakness is that the 'when' framing is constraint/routing-based rather than a clean positive trigger clause, and it omits several capabilities the body covers.

Suggestions

Add a positive 'Use when...' trigger phrase listing natural user terms (e.g. 'Use when a Web app needs to read/write CloudBase NoSQL collections via @cloudbase/js-sdk').

Mention the additional capabilities covered (realtime watch, aggregation, pagination, geolocation) so the description's coverage matches the body.

DimensionReasoningScore

Specificity

Names the domain ('CloudBase document database Web SDK', 'NoSQL collection work') and lists concrete CRUD actions ('Query, create, update, and delete document data'); not a 5 because realtime/aggregation/geolocation capabilities from the body are absent.

4 / 5

Completeness

Has a clear 'what' (CRUD via Web SDK) and explicit trigger/routing guidance ('only for confirmed NoSQL collection work', route to postgresql-development); not a 5 because the 'when' is phrased as a constraint plus negative routing rather than a clean positive 'Use when...' trigger phrase.

4 / 5

Trigger Term Quality

Good keyword coverage ('document database', 'NoSQL collection', 'PostgreSQL', 'CloudBase PG', 'app.rdb()') that a developer would say; not a 5 because it leans technical and omits natural synonyms/variations.

4 / 5

Distinctiveness Conflict Risk

Clear niche (browser-side NoSQL Web SDK) with explicit conflict-avoidance routing ('if the task mentions PostgreSQL / CloudBase PG / app.rdb(), route to postgresql-development instead'), minimizing wrong-skill triggering.

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.