cloudbase-wechat-integration — Claude Code skill
cloudbase-wechat-integration — a skill for Claude Code guides WeChat Pay, virtual payment, and Official Account OAuth setups in CloudBase. Activates when handling callbacks, generated cloud functions, or openid routing.
MIT 125 installs ★ 82 updated 2026-11-15
npx skills add TencentCloudBase/skills --skill cloudbase-wechat-integration -a claude-codeWhat cloudbase-wechat-integration does
This skill guides WeChat payment setups through the CloudBase Integration Center. It covers Mini Program WeChat Pay (wx.requestPayment), virtual goods payment (wx.requestVirtualPayment), Official Account JSAPI checkout, Native QR-code generation, and OAuth identity flows.
Setting up the Integration Center is strictly console-first. The skill forbids placing APIv3 keys, merchant certificates, or AppSecret values into source code or chat prompts. Client-side payment confirmation is treated as UI feedback only. The actual payment status requires server-side queries or verified incoming callbacks.
In standalone installs, relative paths pointing to sibling skill files cannot be resolved. The skill prohibits fetching remote markdown documentation via HTTP directly into the agent context.
What it helps with
- configure Mini Program WeChat Pay and
wx.requestPaymentroutines - integrate virtual goods purchases using
wx.requestVirtualPaymentandxpay_*callbacks - implement Official Account JSAPI payments and OAuth user verification
- add idempotency checks and order storage to generated CloudBase payment functions
Example prompts for the agent
- Configure WeChat Pay for my Mini Program using CloudBase Integration Center
- Implement virtual payment with wx.requestVirtualPayment and process xpay callbacks
- Set up Official Account OAuth and server-side payment verification
How to install cloudbase-wechat-integration
1Skills CLI (Vercel)
npx skills add TencentCloudBase/skills --skill cloudbase-wechat-integration -a claude-code2Manually: put the files in place
~/.claude/skills/cloudbase-wechat-integration/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cloudbase-wechat-integration/
1Skills CLI (Vercel)
npx skills add TencentCloudBase/skills --skill cloudbase-wechat-integration -a codex2Manually: put the files in place
.agents/skills/cloudbase-wechat-integration/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add TencentCloudBase/skills --skill cloudbase-wechat-integration -a cursor2Manually: put the files in place
.cursor/skills/cloudbase-wechat-integration/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install TencentCloudBase/skills skills/cloudbase-wechat-integration2Manually: put the files in place
.github/skills/cloudbase-wechat-integration/SKILL.md1Skills CLI (Vercel)
npx skills add TencentCloudBase/skills --skill cloudbase-wechat-integration -a gemini-cli2Platform CLI
gemini skills install https://github.com/TencentCloudBase/skills --path skills/cloudbase-wechat-integrationManually: put the files in place
.devin/skills/cloudbase-wechat-integration/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add TencentCloudBase/skills --skill cloudbase-wechat-integration -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cloudbase-wechat-integration
How to install cloudbase-wechat-integration in Claude Code?
Run npx skills add TencentCloudBase/skills --skill cloudbase-wechat-integration -a claude-code. The skill file is placed at ~/.claude/skills/cloudbase-wechat-integration/SKILL.md.
What does cloudbase-wechat-integration do?
It provides safe execution patterns for WeChat payments and OAuth in CloudBase. It prevents secret leaks and enforces verified server-side callback handling.
What is required to run cloudbase-wechat-integration?
You need an active CloudBase Integration Center setup. All merchant keys and account credentials must be configured directly inside the CloudBase console form.
Source text
SKILL.md · MIT
--- name: cloudbase-wechat-integration description: 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. version: 2.37.6 license: MIT alwaysApply: false --- # 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 the official Markdown docs for console details that may change. ## Sibling skills (local only) The full CloudBase plugin installs sibling skills beside this one, so local relative paths such as `../auth-tool-cloudbase/SKILL.md` resolve there. A standalone install from a skill marketplace packages only this skill; those paths do not exist, and any "Then also read" link starting with `../` cannot be opened. When a sibling file is missing, or the task needs CloudBase backend capabilities, give the user this prompt to paste into their AI IDE: ```text 帮我把 CloudBase 接好,按下面做: 1. 打开 https://docs.cloudbase.net/skill.md,按说明完成接入。 2. 接入完成后告诉我,并建议最相关的下一步。 ``` 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.md` - CloudBase Integration Center usage: `https://docs.cloudbase.net/integration/usage.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 user asks about 虚拟支付 (virtual payment) for virtual goods: 道具直购, 代币充值, `wx.requestVirtualPayment`, OfferID, AppKey 签名, `xpay_*` callbacks (发货推送/查单/退款), or MP 后台虚拟支付开通与配置. - 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 In a standalone install, use the setup prompt above instead of these `../` paths. - 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 1. Treat Integration Center creation as a console-first workflow unless a public Manager SDK or Cloud API contract is confirmed in official docs. 2. Use official `index.md` docs for console UI steps and credential fields; do not copy stale console screenshots or invent field names. 3. Never ask the user to paste secrets into chat. Tell them to configure merchant and official-account credentials in the CloudBase console Integration Center form. 4. Do not assume generated function names are fixed. `pay-common` and `offiaccount-common` are examples; ask for or inspect the actual function name before writing calls. 5. Treat frontend payment success as UI feedback only. The authoritative payment state must come from server-side query results or payment callbacks. 6. When extending generated functions, preserve credential environment variables and generated callback verification/decryption logic. Add business logic around order checks, persistence, idempotency, and fulfillment. 7. Before changing payment or callback code, identify the target scenario and load only the matching reference file. 8. For 虚拟支付 inbound callbacks, do not reuse outbound `pay_sig` as the notify authenticator. Cloud function and Integration Center deliveries are already verified. A self-hosted HTTP receiver follows mini program message-push verification in `references/virtual-payment.md`. Match the ack to the configured XML or JSON push format. `refund_order` success only means the refund task was accepted. A refund notify counts as success only when its `RetCode` is `0` and the refund id matches; do not invent unpublished idempotency or query-parameter mappings. ## Routing | Task | Read | Why | | --- | --- | --- | | Capability selection, console-first boundaries, independent distribution | `references/overview.md` | Establishes the Integration Center model and safety rules | | Mini Program WeChat Pay, `wx.cloud.callHTTPFunction`, `wx.requestPayment` | `references/mini-program-pay.md` | Covers Mini Program openid injection, order creation, and callback expectations | | Mini Program 虚拟支付, virtual goods, `wx.requestVirtualPayment`, `xpay_*` callbacks | `references/virtual-payment.md` | Covers OfferID/AppKey signing, sandbox vs 现网, delivery callbacks, `query_order` status, refund acceptance vs completion, and self-hosted message-push verification versus gateway-verified callbacks | | Official Account JSAPI pay, H5 inside WeChat, `WeixinJSBridge.invoke` | `references/official-account-jsapi-pay.md` | Covers official-account openid and JSAPI invocation | | Native QR-code pay for PC/Web checkout | `references/native-qr-pay.md` | Covers `code_url`, QR rendering, and polling/query flow | | Official Account OAuth, openid/userinfo retrieval | `references/official-account-oauth.md` | Covers OAuth routes generated by the official-account integration | | 404, missing credentials, openid mismatch, callback failures, logs | `references/troubleshooting.md` | Provides diagnosis steps before changing code | ## Quick Workflow 1. Classify the scenario: Mini Program Pay, Virtual Payment (虚拟支付), JSAPI Pay, Native Pay, Official Account OAuth, generated-function extension, or troubleshooting. 2. Load the matching reference and the official `index.md` docs linked there. 3. Confirm the actual CloudBase environment ID and generated function name. 4. Generate or modify only the required client/backend code; keep merchant credentials in Integration Center configuration. 5. Add order-status query, callback idempotency, and amount/order validation when payment state affects business data. 6. Verify through function logs, callback logs, and an end-to-end payment sandbox or low-value production test as appropriate. ## Minimum Self-Check - Did I avoid guessing undocumented Integration Center management APIs? - Did I use the actual generated function name instead of assuming `pay-common`? - Did I keep all merchant secrets and certificates out of source code and chat? - Did the payment flow rely on callback/query state rather than only frontend success? - Did I load only the scenario reference needed for the user's task? ## Reference index All packaged reference files (required for skill lint reachability): - [mini-program-pay.md](references/mini-program-pay.md) - [native-qr-pay.md](references/native-qr-pay.md) - [official-account-jsapi-pay.md](references/official-account-jsapi-pay.md) - [official-account-oauth.md](references/official-account-oauth.md) - [overview.md](references/overview.md) - [troubleshooting.md](references/troubleshooting.md)
© TencentCloudBase · MIT · TencentCloudBase/skills