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.
SkillScore96Maintained
Automatic
◆Coding pack
Last verified 8/9/2026
What it changes
Passed 24 of 25 test cases with the skill, and 11 of 25 without it.
Without skill44%
With skill96%
Checks it passed that the model alone missed
Point to references/overview.md.
Point to references/native-qr-pay.md.
Point to references/troubleshooting.md.
and 12 more in the full report
13 fixed11 passed either way1 still failing0 broke
Pass-rate lift
+52 pp
Tokens
+29%
Agent turns
0%
Response time
-37%
Model gemini-3.6-flashMeasured 8/9/2026v224 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 13
Prompt
Which reference file should be consulted to understand the Integration Center architecture model, capability selection, and general safety boundaries?
What was checked, without and with the skill
Checked
Without skill
With skill
Point to references/overview.md.
Missed
Passed
case-21 · gemini-3.6-flash · 8/9/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md84 lines7 files
CloudBase WeChat Integration
This skill routes WeChat payment and official-account work through CloudBase Integration Center. It gives the agent the stable execution contract and points to official index.md docs for console details that may change.
Sibling skills (local only)
Sibling CloudBase skills ship beside this skill. Use local relative paths such as ../auth-tool-cloudbase/SKILL.md.
If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do not HTTP-fetch remote skill or protocol markdown into the agent context.
Official CloudBase Integration Center docs (human reference — do not treat as skill markdown to fetch into agent context as a sibling skill substitute):
CloudBase Integration Center overview: https://docs.cloudbase.net/integration/introduce/index.md
CloudBase Integration Center usage: https://docs.cloudbase.net/integration/usage/index.md
When cloud function deployment or log operations are needed and no sibling skill is available, use the current platform's CloudBase MCP tools or CloudBase console instead of guessing unsupported APIs.
Activation Contract
Use this first when
The user asks about WeChat Pay, 小程序支付, 微信支付, JSAPI 支付, 公众号支付, Native 扫码支付, 二维码支付, refund callbacks, payment callbacks, wx.requestPayment, WeixinJSBridge, openid, or Official Account OAuth in a CloudBase app.
The task mentions CloudBase Integration Center, 集成中心, generated payment functions, pay-common, offiaccount-common, or callback routing for WeChat payment.
The user needs to extend a CloudBase Integration Center generated function with order persistence, idempotency, fulfillment, or payment-status sync.
Then also read
Mini Program structure and preview work -> ../miniprogram-development/SKILL.md (if unavailable, use the current mini program platform docs and the mini-program payment reference in this skill)
Web frontend work -> ../web-development/SKILL.md (if unavailable, use the JSAPI or Native references in this skill)
Cloud function runtime, logs, deployment, or gateway work -> ../cloud-functions/SKILL.md (if unavailable, use CloudBase console/MCP function tools and the generated-function guidance in this skill)
Do NOT use for
Generic CloudBase Web Auth or Mini Program native identity work that does not involve WeChat payment or official-account OAuth.
General CloudBase cloud function development unrelated to Integration Center generated functions.
Creating or managing Integration Center instances through guessed MCP tools, guessed Manager SDK methods, or undocumented Cloud API actions.
Storing merchant secrets, private keys, APIv3 keys, AppSecret values, or certificates in app source code, generated examples, README files, commits, or prompts.
Operating Rules
Treat Integration Center creation as a console-first workflow unless a public Manager SDK or Cloud API contract is confirmed in official docs.
Use official index.md docs for console UI steps and credential fields; do not copy stale console screenshots or invent field names.