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.

66

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 validated gotchas (rule-cache propagation, result._id shape), and it is well-structured with clear sibling/reference routing. Its main weaknesses are mild over-explanation and the fact that the many referenced .md files are not actually bundled here, which weakens progressive disclosure.

Suggestions

Either 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 Quick routing links so navigation does not point at missing files.

Tighten the duplicated guidance between 'Minimal checklist', 'Working rules', and 'Common mistakes' into a single sequenced workflow with explicit validate->fix->retry checkpoints for destructive/batch writes.

Trim explanations of concepts Claude already knows (e.g., what security rules do at a conceptual level) and keep only the CloudBase-specific behavioral notes.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (canonical init, code blocks, terse working rules), but a few passages over-explain known concepts (e.g., spelling out that security rules validate requests, or restating CRUD semantics in both the checklist and working rules) that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready executable code for init, query, create-with-ID-capture, pagination, field selection, and error handling, plus concrete validated rule patterns and method references that cover the common cases.

5 / 5

Workflow Clarity

Clear sequenced guidance (activation contract -> minimal checklist -> working rules) with explicit validation feedback for risky writes (the 2-5 minute rule-cache gotcha and 'do not treat a resolved promise as success'), but the main workflow lacks an explicit validate->fix->retry loop as a numbered checkpoint sequence.

4 / 5

Progressive Disclosure

Good one-level-deep structure with a Quick routing section pointing to crud-operations.md, complex-queries.md, pagination.md, etc., but no bundle files are present in references/scripts/assets, so those signaled reference files do not actually exist in this environment.

4 / 5

Total

17

/

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 strong: it states concrete CRUD actions, scopes the skill to confirmed NoSQL browser-side work, and adds explicit routing away from PostgreSQL to avoid sibling-skill conflicts. It could be improved by adding a positive 'Use when...' trigger clause and richer natural-language keywords.

Suggestions

Add an explicit positive 'Use when...' clause listing natural triggers (e.g., 'Use when a Web app needs NoSQL collection CRUD, realtime watch, pagination, aggregation, or geolocation queries via @cloudbase/js-sdk').

Expand trigger-term coverage with synonyms users actually say: 'NoSQL', 'collection', 'realtime listeners', '@cloudbase/js-sdk'.

Reframe the PG exclusion as a supporting detail after the positive use-when clause so 'when' reads as inclusion-first rather than exclusion-first.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Query, create, update, and delete document data") plus an explicit routing condition, but the actions stay at generic CRUD level rather than enumerating watch/aggregation/geolocation capabilities covered in the body.

4 / 5

Completeness

Both 'what' (query/create/update/delete document data) and 'when' (confirmed NoSQL collection work, plus a negative trigger for PostgreSQL) are present and explicit, but the 'when' is framed mostly as an exclusion rather than a positive 'Use when...' clause with concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes natural SDK surface terms users would say ("document database", "Web SDK", "PostgreSQL", "CloudBase PG", "app.rdb()"), but omits common synonyms like "NoSQL", file/package names, or phrasings a user might say like "collection" queries.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Web SDK document database) with an explicit conflict-avoidance routing rule to postgresql-development for PG / app.rdb() tasks, giving minimal risk of triggering the wrong skill.

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.