CtrlK
BlogDocsLog inGet started
Tessl Logo

cloudbase-document-database-in-wechat-miniprogram

Use CloudBase document database WeChat MiniProgram SDK to query, create, update, and delete data. Supports complex queries, pagination, aggregation, and geolocation queries.

58

Quality

68%

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-in-wechat-miniprogram/SKILL.md

The canonical home for this skill is cloudbase-document-database-in-wechat-miniprogram 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.

The body is well-structured with good routing and lean sections, but it leans on reference files that are missing from the bundle and lacks the validation/feedback loop that database operations require. Adding an inline error-handling/retry loop and at least minimal inline examples for the routed operations would lift the score.

Suggestions

Add an explicit validation/feedback loop for database writes, e.g. 'After .add()/.update(), handle permission errors by re-checking the collection rule's auth.openid/_openid conditions before retrying.'

Provide at least one minimal executable inline example for each routed category (pagination .limit/.skip, aggregation .aggregate(), geolocation .geometry) so the skill is useful even when the companion files are missing.

Remove the Overview use-case list that duplicates the Activation Contract to tighten conciseness, or merge the two sections.

DimensionReasoningScore

Conciseness

Mostly lean lists, code, and routing with no padding of concepts Claude already knows, but the Overview section restates the use-case list already present in the Activation Contract and the init pattern appears twice.

4 / 5

Actionability

Provides executable code for initialization and basic read/query/doc access, but the five remaining routed operation categories (create/update/delete, pagination, aggregation, geolocation, security rules) have no inline executable examples — only pointers to absent files.

3 / 5

Workflow Clarity

A clear Minimal checklist and Working rules sequence exist, but database operations require a validate→fix→retry feedback loop and none is present, which caps workflow clarity at 3 per the feedback-loops scoring note.

3 / 5

Progressive Disclosure

Well-signaled one-level-deep structure with a Quick routing section and clear headers, but the six referenced companion files and sibling skills are absent from the bundle, so navigation is not actually functional here.

4 / 5

Total

14

/

20

Passed

Description

75%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 and well-differentiated with comprehensive action coverage, but it omits any explicit 'when to use' trigger guidance, capping its completeness. Adding a 'Use when...' clause naming the natural trigger terms would raise the score.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a WeChat Mini Program needs CloudBase document database access via wx.cloud.database() for CRUD, pagination, aggregation, or geolocation queries.'

Include the API surface terms users actually say ('wx.cloud.database()', 'collection', 'wxContext.OPENID') alongside the conceptual keywords to broaden trigger coverage.

Mention the negative boundary briefly (e.g. 'Not for Web @cloudbase/js-sdk or server-side access') to further reduce overlap with sibling skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'query, create, update, and delete data' plus 'complex queries, pagination, aggregation, and geolocation queries' — giving comprehensive coverage of the domain's operation types.

5 / 5

Completeness

Clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural ecosystem terms a developer would say (CloudBase, document database, WeChat MiniProgram, pagination, aggregation, geolocation) but misses common synonyms and the API surface terms users actually say (wx.cloud, collection, .database()).

4 / 5

Distinctiveness Conflict Risk

The tightly scoped 'CloudBase document database WeChat MiniProgram SDK' niche is clearly distinct from Web SDK, cloud functions, and SQL work, with minimal conflict risk.

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.