CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudbase-wechat-integration

CloudBase WeChat integration guide for Mini Program WeChat Pay, Mini Program virtual payment (虚拟支付, wx.requestVirtualPayment), Official Account JSAPI Pay, Native QR-code Pay, Official Account OAuth, openid handling, payment callbacks, and CloudBase Integration Center generated functions. This skill should be used when users ask to add, debug, or extend WeChat payment, virtual payment, or official-account flows on CloudBase.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

The canonical home for this skill is cloudbase-wechat-integration 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 well-engineered orchestration skill: lean rule-based body, a precise routing table to real one-level-deep reference files, an explicit workflow with verification checkpoints, and a self-check checklist. The two deductions are small: a redundant triple-statement of the secrets rule, and a Reference index that omits virtual-payment.md despite claiming to list all packaged files.

Suggestions

Add references/virtual-payment.md to the 'Reference index' section — it is referenced in the Routing table and Operating Rule 8 but missing from the index that claims to list all packaged reference files.

Consolidate the merchant-secrets guidance into one canonical rule (currently stated in 'Do NOT use for', Operating Rule 3, and Minimum Self-Check) to save tokens without losing the safety signal.

Trim the sibling-skills section: the per-path 'if unavailable' fallbacks in 'Then also read' already cover the missing-sibling guidance, so the local-only caveats can be shortened.

DimensionReasoningScore

Conciseness

The body is dense and rule-based, assumes Claude's competence (no explanations of what openid, WeChat Pay, or callbacks are), and every section carries operational weight. Minor trimmable redundancy keeps it below the 5 anchor: merchant-secrets guidance appears three times ("Do NOT use for" bullet, Operating Rule 3, Minimum Self-Check), and the sibling-skills section repeats 'if unavailable' fallback caveats already covered in "Then also read".

4 / 5

Actionability

As an instruction/routing skill, the guidance is maximally concrete: a routing table mapping exact trigger terms to exact reference file paths, API-level specifics ("A refund notify counts as success only when its RetCode is 0", "do not reuse outbound pay_sig as the notify authenticator"), and explicit verification channels (function logs, callback logs, sandbox test). Per the rubric's code_vs_instruction note, absence of code blocks is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

The 6-step Quick Workflow is clearly sequenced with explicit checkpoints (step 3: confirm actual environment ID and generated function name; step 6: verify via function logs, callback logs, and end-to-end sandbox/low-value test) and is backed by a Minimum Self-Check checklist. Error recovery is routed explicitly (callback failures/logs -> references/troubleshooting.md 'before changing code'). Not the 4 anchor because validation checkpoints and the recovery path are explicit, not implicit.

5 / 5

Progressive Disclosure

Good structure overall: the body is an ~88-line overview, the routing table clearly signals one-level-deep references, and all 7 bundled reference files exist and contain no further nesting (only external official-doc URLs). However, the 'Reference index' claims to list 'All packaged reference files (required for skill lint reachability)' yet omits references/virtual-payment.md — the largest reference (19KB), which is referenced in both the Routing table and Operating Rule 8. That omission is a minor organization gap, matching the 4 anchor rather than the 5 anchor.

4 / 5

Total

18

/

20

Passed

Description

95%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 strong description: it explicitly states both what the skill covers and when to use it, with rich bilingual (English/中文) trigger terms and concrete API names. The only weakness is that the capability sentence reads as a topic enumeration ('guide for X, Y, Z') rather than leading with action verbs, which slightly blunts the specificity of the 'what'.

DimensionReasoningScore

Specificity

The description enumerates many specific, concrete capabilities with real API names ("Mini Program virtual payment (虚拟支付, wx.requestVirtualPayment)", "Official Account JSAPI Pay", "Native QR-code Pay", "openid handling"), but the 'what' is phrased as a topic list ('integration guide for...') rather than concrete action verbs; the actions ('add, debug, or extend') appear only in the when-clause. This sits between the 4 anchor ('several specific actions; minor gaps') and the 5 anchor (comprehensive concrete actions).

4 / 5

Completeness

Both questions are answered explicitly: the 'what' is a full capability list, and the 'when' is an explicit trigger clause with concrete phrases — "This skill should be used when users ask to add, debug, or extend WeChat payment, virtual payment, or official-account flows on CloudBase". Matches the 5 anchor; it is not the 4 anchor because the when-clause is explicit and specific rather than generic.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including English/Chinese synonyms and concrete API identifiers: "WeChat Pay", "虚拟支付", "wx.requestVirtualPayment", "Official Account", "JSAPI Pay", "Native QR-code Pay", "OAuth", "openid", "payment callbacks", "CloudBase". A user needing this skill would naturally say these terms.

5 / 5

Distinctiveness Conflict Risk

Clear niche at the intersection of CloudBase and WeChat payment/official-account flows with distinct triggers (wx.requestVirtualPayment, JSAPI Pay, openid, Integration Center generated functions). Minimal overlap risk with generic CloudBase or general payment skills.

5 / 5

Total

19

/

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

plugin/cloudbase/skills/cloudbase-wechat-integration/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.