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.

71

Quality

88%

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 cloudbase-document-database-web-sdk in TencentCloudBase/CloudBase-AI-Toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, actionable skill body with executable examples and genuinely useful validation feedback loops for database writes. Its only real weaknesses are mild cross-section repetition of the result._id and CMS-rule material, and companion reference files that are cited but not present in the bundle.

Suggestions

Consolidate the result._id return-shape guidance into one location (e.g., 'Working rules #5' or 'Common mistakes') and reference it from the other instead of restating it in three places.

Ship the referenced companion files (crud-operations.md, complex-queries.md, pagination.md, aggregation.md, realtime.md, geolocation.md, security-rules.md) in the references/ bundle, or add a fallback note like the one used for sibling skills so missing references do not break navigation.

DimensionReasoningScore

Conciseness

The body is dense with high-value, non-obvious domain knowledge (2-5 minute rule-evaluator caching, result._id return shape) rather than basics Claude already knows, but the result._id gotcha and the CMS CUSTOM-rule pattern are each restated across 'Common mistakes', 'Working rules', and 'Quick examples', which is minor over-explanation that could be trimmed — fitting the 'efficient; minor instances of over-explanation' anchor rather than the lean 5.

4 / 5

Actionability

Provides copy-paste-ready, executable JavaScript for initialization, query, create-with-ID-capture, ordered pagination, field selection, and error handling, plus a concrete CUSTOM rule expression, covering the common cases as required by the top anchor.

5 / 5

Workflow Clarity

A numbered 'Working rules' sequence and 'Minimal checklist' are paired with explicit validation feedback loops for the risky write path — 'do not treat a resolved promise as success', check 'result.code/result.message', get()-round-trip the just-written _id, and wait 2-5 minutes then retry after a rule change — satisfying the 'explicit validation steps; feedback loops for error recovery; checklists' anchor and avoiding the destructive/batch cap.

5 / 5

Progressive Disclosure

A 'Quick routing' section gives well-signaled one-level-deep references to crud-operations.md, complex-queries.md, pagination.md, aggregation.md, realtime.md, geolocation.md, and security-rules.md, mirroring the good anchor, but none of these companion files exist in the bundle (references/ is empty) and some inline content overlaps the referenced files, leaving minor organization gaps that hold it below the clean-navigation 5.

4 / 5

Total

18

/

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 tight, well-targeted description that states both capability and explicit activation/routing guidance, with strong distinctiveness. It is slightly under-comprehensive on action breadth and natural-term variants, keeping specificity and trigger_term_quality at 4 rather than 5.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Query, create, update, and delete document data') with a clear domain, but stops short of comprehensive coverage — pagination, aggregation, realtime, and geolocation (covered in the body) are absent from the description, so the 'minor gaps' anchor fits better than the 'comprehensive coverage' anchor at 5.

4 / 5

Completeness

Explicitly answers both what ('Query, create, update, and delete document data' via the Web SDK) and when ('only for confirmed NoSQL collection work' plus a concrete exclusion trigger to route to postgresql-development), matching the 'clearly and explicitly answers both what AND when with concrete trigger phrases' anchor.

5 / 5

Trigger Term Quality

Good keyword coverage of natural platform terms a CloudBase user would say ('CloudBase document database', 'NoSQL collection', 'PostgreSQL', 'CloudBase PG', 'app.rdb()'), with only a few natural variations missing; it is above the 'some relevant keywords but missing common variations' anchor at 3 but does not reach the fully comprehensive synonym/extension coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The skill carves a clear niche (browser-side NoSQL via @cloudbase/js-sdk) and adds an explicit routing rule away from PostgreSQL/Mini Program/SQL surfaces, giving minimal conflict risk as described by the top anchor.

5 / 5

Total

18

/

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.