CtrlK
BlogDocsLog inGet started
Tessl Logo

cloudbase-wechat-integration

CloudBase WeChat integration guide for Mini Program WeChat Pay, 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 or official-account flows on CloudBase.

69

Quality

85%

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

85%

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: concrete routing table, explicit operating rules, a sequenced workflow with verification, and clean one-level reference disclosure. The only weakness is token weight from repetitive standalone-distribution fallback URLs that could be consolidated.

Suggestions

Consolidate the standalone-distribution fallback URLs into a single canonical fallback note instead of repeating a chained 'standalone fallback: <url>; if unavailable, use…' clause on each 'Then also read' line.

Move the five raw-source URLs out of the inline 'Standalone Install Note' bullets into one referenced entry (or the overview reference) to reduce repeated token cost in the main body.

DimensionReasoningScore

Conciseness

The body is free of concept-explanation fluff and assumes Claude's competence, but the 'Standalone Install Note' URL list and the three chained per-line fallback URLs in 'Then also read' add repetitive token weight that could be tightened; this matches 'mostly efficient but could be tightened' rather than the lean 3-anchor.

2 / 3

Actionability

Provides a concrete routing table mapping each task to a specific reference file, names the generated functions (pay-common, offiaccount-common) with a warning not to assume them, and gives explicit operating rules plus a sequenced quick workflow; not a 2 because the guidance is concrete and copy-ready rather than abstract.

3 / 3

Workflow Clarity

The Quick Workflow is sequenced with an explicit verification step (function logs, callback logs, end-to-end sandbox or low-value production test) and a Minimum Self-Check checklist, with the troubleshooting reference covering error recovery; not a 2 because validation checkpoints are explicit rather than implicit.

3 / 3

Progressive Disclosure

SKILL.md is a clean overview with a routing table and reference index, and all six referenced files (overview, mini-program-pay, official-account-jsapi-pay, native-qr-pay, official-account-oauth, troubleshooting) exist in references/ as one-level-deep, clearly signaled navigation; not a 2 because the split is appropriate and well-organized.

3 / 3

Total

11

/

12

Passed

Description

85%

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, specific description that clearly states capabilities and an explicit use-when trigger in third-person voice. Its main gap is trigger-term breadth: it omits the Chinese variations that are natural for WeChat work and only appear in the body.

Suggestions

Add the common Chinese trigger terms (微信支付, 小程序支付, 公众号支付, 扫码支付) to the description itself, not just the body, so the description matches how users actually phrase WeChat payment requests.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities ('Mini Program WeChat Pay, Official Account JSAPI Pay, Native QR-code Pay, Official Account OAuth, openid handling, payment callbacks') and names actions ('add, debug, or extend'), matching the multiple-specific-actions anchor; not a 2 because the coverage is comprehensive rather than partial.

3 / 3

Completeness

Explicitly answers both what ('CloudBase WeChat integration guide for…') and when ('This skill should be used when users ask to add, debug, or extend WeChat payment or official-account flows on CloudBase'); not a 2 because the trigger clause is explicit rather than implied.

3 / 3

Trigger Term Quality

Good English keyword coverage (WeChat Pay, JSAPI, openid, OAuth, payment callbacks) but missing common natural variations users would say in this domain — notably the Chinese terms (微信支付, 小程序, 公众号) that appear only in the body, not the description — so it sits at 'some relevant keywords but missing common variations' rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

Tightly scoped to CloudBase + WeChat payment/official-account flows with distinct triggers, making it unlikely to fire for the wrong skill; not a 2 because the niche is clearly delineated rather than overlapping.

3 / 3

Total

11

/

12

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.