CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

72%

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 ./connectors/cloudbase-intl/skills/references/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

57%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-structured, actionable routing skill with concrete initialization code and a useful pre-flight checklist, held back by cross-section redundancy, a missing validation/feedback loop for destructive database writes, and companion reference files that are absent from the bundle entirely. The SKILL.md layer is solid; the disclosure layer it depends on does not resolve.

Suggestions

Ship the six routed reference files (crud-operations.md, complex-queries.md, pagination.md, aggregation.md, geolocation.md, security-rules.md) in the bundle, or inline minimal add/update/delete snippets while the files are unavailable.

Merge the duplicated guidance — combine "Common mistakes / gotchas" with "Working rules" and drop the Overview's restatement of the description — to remove roughly a quarter of the body's redundancy.

Add an explicit post-write validation step and error-recovery loop for update/delete operations (e.g., re-read the document after write, and on permission failure re-check the security rule/query shape before retrying).

DimensionReasoningScore

Conciseness

The body is mostly efficient and SDK-specific, but contains several redundant passages: the Overview's "Use it for" list repeats the frontmatter description verbatim, and "Common mistakes / gotchas" restates Working rules 2–4 (manual `_openid` writes, security-rule enforcement, admin routing) a second time. Not 4 because this repetition spans multiple sections rather than being minor trimmable instances; not 2 because nothing explains concepts Claude already knows and each section is individually tight.

3 / 5

Actionability

Concrete, executable guidance dominates: canonical `wx.cloud.database()` initialization (with env targeting), runnable get/doc examples, and a specific prohibition ("Never set or override `_openid` manually in `.add()`, `.set()`, or `.update()` payloads"). Not 5 because the common cases (add/update/delete) are delegated to companion reference files that are not present in the bundle, and no inline snippet covers them.

4 / 5

Workflow Clarity

The "Minimal checklist" gives a coherent pre-flight sequence (confirm Mini Program caller, initialize `wx.cloud`, verify `auth.openid`/`_openid` rules, read the companion reference), but there is no post-write validation or validate-fix-retry feedback loop — and the rubric caps database skills with destructive operations (update/delete) lacking validation at 3. Not 4 because the only error guidance is a diagnostic hint ("Permission errors usually mean the rule/query relationship is wrong"), not an explicit checkpoint.

3 / 5

Progressive Disclosure

The SKILL.md itself is well organized with a clearly signaled one-level-deep routing table ("CRUD -> ./crud-operations.md" etc.), but none of the six referenced files (crud-operations.md, complex-queries.md, pagination.md, aggregation.md, geolocation.md, security-rules.md) exist in the bundle — verified against the actual file listing — so navigation dead-ends. Not 4 because dangling references to the skill's entire detail layer is more than a minor organization gap; not 2 because the structure and signaling within SKILL.md are genuinely good and nothing is improperly inlined.

3 / 5

Total

13

/

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.

A specific, well-scoped description with concrete capabilities and a clearly distinguished niche, undermined only by the complete absence of explicit "when to use" trigger guidance. Adding a use-when clause with natural trigger phrases would lift it into the top tier.

Suggestions

Append a trigger clause such as "Use when a WeChat Mini Program needs to read or write CloudBase collections via wx.cloud.database(), or when the request mentions Mini Program collection CRUD, pagination, aggregation, or geolocation queries."

Include the natural API phrase "wx.cloud.database()" and the term "collection" so the description matches how users actually phrase these requests.

Consider the standard two-word spelling "Mini Program" alongside "MiniProgram" to match likely user phrasing.

DimensionReasoningScore

Specificity

"query, create, update, and delete data. Supports complex queries, pagination, aggregation, and geolocation queries" lists multiple concrete actions that comprehensively cover this database SDK's surface — the four CRUD verbs plus the four advanced capabilities the skill actually routes to. Not 4 because coverage matches the skill's full operation set with no meaningful gaps.

5 / 5

Completeness

The "what" is clear and concrete ("query, create, update, and delete data... pagination, aggregation, and geolocation queries"), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps this dimension at 3 per the rubric guidelines. Not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural domain keywords are present ("CloudBase", "document database", "WeChat MiniProgram", "query", "pagination", "aggregation", "geolocation") — terms users would plausibly say. Not 5 because common synonyms are missing: the actual API entry point "wx.cloud.database()", "collection(s)", and the two-word "Mini Program" spelling users typically type.

4 / 5

Distinctiveness Conflict Risk

"CloudBase document database WeChat MiniProgram SDK" carves out a precise niche that distinguishes it from the sibling Web SDK, cloud-function, and PostgreSQL variants. Not 4 because the platform + SDK + datastore triple leaves minimal overlap risk with any other skill's triggers.

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.

Validation — 15 / 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

Path

connectors/cloudbase-intl/skills/references/cloudbase-document-database-in-wechat-miniprogram/SKILL.md

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.