CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

71

Quality

87%

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-wechat-integration in TencentCloudBase/CloudBase-AI-Toolkit

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 routing skill: concise, with a clear routing table, sequenced workflow, and a self-check checklist. The main gap is an inconsistent reference index that drops virtual-payment.md despite routing to it.

Suggestions

Add references/virtual-payment.md to the bottom 'Reference index' list so the declared index matches the Routing table.

Tighten the Activation Contract and Sibling-skills sections by collapsing the repeated 'if unavailable, use ...' clauses into a single fallback note.

Make the Quick Workflow's verification step an explicit fail→retry loop (e.g., 'If logs/callbacks show a mismatch, return to step 3 and re-confirm the function name and env ID') to strengthen the feedback loop for payment-state-affecting work.

DimensionReasoningScore

Conciseness

The body is a lean routing/index skill that assumes Claude's competence and does not explain WeChat Pay concepts, but the Activation Contract and Sibling-skills sections carry some repetition ('if unavailable...' clauses, overlapping term lists) that could be trimmed.

4 / 5

Actionability

Concrete guidance throughout — a task→reference→why routing table, a 6-step Quick Workflow, and specific Operating Rules ('preserve credential environment variables', 'ask for or inspect the actual function name') — though as an instruction-only routing skill it provides no executable code, which the rubric permits.

4 / 5

Workflow Clarity

The Quick Workflow gives a clear 6-step sequence and the Minimum Self-Check section plus step 6 ('Verify through function logs, callback logs, and an end-to-end payment sandbox') provide validation checkpoints, though explicit fail→retry feedback loops are only implied rather than spelled out.

4 / 5

Progressive Disclosure

Clear overview with a well-signaled one-level-deep routing table mapping tasks to reference files, but references/virtual-payment.md is referenced in the Routing table yet omitted from the bottom 'Reference index' list, a minor organization gap.

4 / 5

Total

16

/

20

Passed

Description

100%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, comprehensive, and bilingual, with concrete trigger terms and an explicit 'use when' clause. Voice is appropriately third person with no first/second-person drift.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — '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 'Integration Center generated functions' — giving comprehensive coverage rather than vague domain naming.

5 / 5

Completeness

Explicitly answers both 'what' (integration guide for the enumerated WeChat payment/official-account flows) and 'when' ('This skill should be used when users ask to add, debug, or extend WeChat payment, virtual payment, or official-account flows on CloudBase'), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including bilingual synonyms ('虚拟支付', 'WeChat Pay'), specific API names ('wx.requestVirtualPayment', 'openid'), and flow names users would say, matching the 'synonyms and file extensions' anchor.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (CloudBase + WeChat payment/official-account integration) with distinct, specific triggers that would not collide with generic CloudBase or general payment skills.

5 / 5

Total

20

/

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.