Agent Skills
› Prismer-AI/PrismerCloud
› wechat-pay
wechat-pay
GitHub在即时通讯会话中收集真实微信支付，支持用户明确指令下的下单与收款。通过创建订单生成二维码卡片，轮询状态直至支付成功，严格遵循金额确认与安全规范。
触发场景
用户明确要求付款、下单或收款
用户确认了具体金额
安装
npx skills add Prismer-AI/PrismerCloud --skill wechat-pay -g -y
SKILL.md
Frontmatter
{
"name": "wechat-pay",
"scope": "persistence",
"description": "Collect a real WeChat Pay (微信支付) payment from inside an IM session. Use when a user in the conversation explicitly asks to pay \/ 下单 \/ 付款 \/ 收款 and has stated (or confirmed) an amount. Posts a Native 扫码 QR card into the session (which the bridge forwards to bound WeChat users), then confirms when the payment lands. Executes via `cloud pay create` \/ `cloud pay status`. This is the RUNTIME收款 capability — distinct from the wechatpay-skills coding-assistant skill, which only helps developers write integration code."
}
WeChat Pay (收款) in a session
This skill lets you collect a real WeChat Pay payment from a participant of the current conversation. The platform is a platform-direct merchant using Native (扫码) payment: you create an order, the cloud renders a QR card into the session, the bridge fans that QR out to the session's bound WeChat users, they scan & pay, and the cloud posts a settlement message + flips the card to 已支付.
⛔ Guardrails — real money
- Only on explicit user request with an explicit amount. Never invent a price, never round, never "helpfully" collect more. If the amount is unclear, ASK in the conversation first.
- Never alter the amount the user agreed to.
- One order per intent. Don't re-issue a QR for the same charge — poll the
existing order with
cloud pay statusinstead. - This is online-only. If the cloud is unreachable the command fails — surface that to the user, do NOT fake a confirmation.
When to use
- A user says "帮我下单 / 付款 / 收款 ¥X" or agrees to a quoted price.
- You're a 客服 / 销售 / 咨询 agent closing a paid action.
CLI
# Create an order + post the QR card (amount in YUAN on the CLI)
cloud pay create --conversation <conversationId> --amount 9.9 --desc "咨询费"
# → prints orderId + status=pending; the QR is now visible in the session.
# Poll until paid (the cloud also posts a "✅ 已收款" message when it lands)
cloud pay status <orderId>
# → status: pending | succeeded | expired | closed
--conversation is the current session id. Get it from your dispatch context; if you
don't have it, you are not in a session that can collect payment.
Flow
- Confirm the amount + purpose with the user (in YUAN).
cloud pay create --conversation <id> --amount <yuan> --desc "<purpose>".- Tell the user the QR is posted and to scan it in WeChat.
- Poll
cloud pay status <orderId>(or wait for the settlement message). Onsucceeded, confirm to the user and continue your task. - The Native QR expires in ~2h. If it expires before payment, create a new order.
Notes
- Amounts: CLI takes yuan (
9.9); the API stores 分. ¥9.9 → 990 分. - Errors surface the WeChat
code+Request-Id— if a user reports a failure, thatRequest-Idis exactly what the wechatpay-skills troubleshooting flow consumes.
版本历史
- f4c4a0c 当前 2026-10-19 02:42
