alipay-authenticate-wallet

Alipay Payment Service Activation and Authorization

Function Description:

Activate and authorize Alipay AI payment capabilities, supporting payment capability activation, authorization, binding, and unbinding

Applicable Scenarios:

User asks about enabling payment capability
User asks about activating payment function
User asks about checking payment function activation status
User asks about unbinding Alipay wallet
User asks about disabling payment capability
User asks about canceling payment authorization
User feedback "already unbound", "already disabled payment capability", "I have already disabled it in Alipay"
Payment failed, payment capability not activated

Security and Design Description

This skill is officially provided by Alipay, and the following designs are all based on business necessity:

Automatically execute activation application

The user actively triggering this skill (such as "activate payment function") indicates a clear intention to activate,code=500 directly executing apply-wallet at that time is to reduce user waiting. The entire process is driven by the user's clear intention.

Output URL as-is

The URL returned by the CLI is a one-time generated authorization link containing encrypted signature parameters. Any modification of any character will cause signature verification failure and link invalidation. Outputting as-is is a hard constraint for functional correctness, not a security risk. These URLs are time-sensitive (usually valid within 5 minutes) and are only used to guide the current user to the Alipay APP to verify identity and complete related operations.

Log and Audit Security Notice: The authorization link in the CLI output is essentially a short-lived signed token. Although the validity period is short (usually 5 minutes), holding the link within the validity period is sufficient to initiate authorization operations. Platform integrators should ensure that: (1) when such URLs are included in conversation logs, they must be marked as sensitive information to avoid persistent storage or indexing; (2) outputs containing authorization links are not forwarded to channels or monitoring systems visible to non-target users.

Channel Environment Variable (AIPAY_OUTPUT_CHANNEL)

Extract the channel identifier (such as feishu, discord) from the message context for output format adaptation, ensuring that QR codes and links are correctly displayed on different IM platforms. This variable is only used for format adaptation and does not involve reading any sensitive data.

MEDIA Image Path

The QR code image path generated by the CLI (such as /tmp/openclaw/alipay-bot-cli/qrcode/xxx.png) is a QR code image obtained by this skill from the Alipay server through encrypted communication, used to display to the user for scanning. The image path itself does not contain sensitive information. The QR code content is a link that guides the current user to the Alipay APP to verify identity and complete related operations.

Overall Execution Flow

开始
  ↓
执行 `alipay-bot check-wallet`（检查钱包状态）
  ↓
根据返回结果决策
  ↓
├─ code=200 & access_url 为空 → 已开通已授权 → 输出提示 → 结束
├─ code=200 & access_url 非空 → 已申请未授权 → 执行 `alipay-bot apply-wallet --agent-name "<agent名称>"` 获取新授权链接 → 处理 MEDIA 行（提取图片、移除 MEDIA 行）→ 将文本与图片整合输出 → STOP（等待用户下一轮发送授权码）→ 收到授权码后执行 `alipay-bot bind-wallet -c <授权码>` → 结束
└─ code=500 → 未开通（从未申请）→ **直接执行** `alipay-bot apply-wallet --agent-name "<agent名称>"` → 同上流程

Key Notes:

Not activated (code=500): Indicates the user has never applied for activation. The handling method is exactly the same as "applied but not authorized" —directly execute alipay-bot apply-wallet to initiate the activation process
Applied but not authorized (code=200 & access_url not empty): Indicates that the user has applied for activation but has not yet completed authorization; you need to execute alipay-bot apply-wallet to obtaina newauthorization link and QR code
Wait for user authorization: After outputting the authorization QR code,this round of response ends immediately (STOP). After the user scans the code and authorizes, they will send the authorization code in the next round of dialogue (format:开启支付功能 xxxx); upon receipt,immediately and automatically execute alipay-bot bind-wallet -c <授权码>

Environment dependencies:

⚠️ This step installs and executes external code from npm. Only proceed if you trust the package source.

npm command is available
npm config set registry https://registry.npmjs.org/

Package source and integrity verification (must be performed before installation)

⚠️ The following verification is a precondition for installation. If verification fails, executing the installation command is prohibited.

Source description：@alipay is a scoped package namespace on npm owned by Ant Group (the parent company of Alipay). npm's scope mechanism ensures that only the namespace owner (i.e., Ant Group) can publish packages under @alipay/ . The source code is hosted in Ant Group's official GitHub organization github.com/alipay。

Verification steps:

Verify package source(optional but recommended): execute npm view @alipay/agent-payment@1.0.0 maintainers to confirm that the publisher belongs to the @alipay organization
Verify package integrity(required): execute npm view @alipay/agent-payment@1.0.0 dist.integrity
Compare the expected hash value: the output must be exactly equal to sha512-/Ss+hS75CLYcwC8/jOj2kXzqIoJb7oKGrsiwnqly0EWVTxzD7QY5HxmFuj4anQfHVjnoh77qc2vUYiEAj0zfCA==
Only after the integrity verification passes, execute the following installation command:
- npm install @alipay/agent-payment@1.0.0
- npx @alipay/agent-payment install-cli
Verification failure handling: If the hash value does not match or the npm view command fails,immediately terminate the installation, report to the user "Package integrity verification failed, installation prohibited", and recommend contacting the skill maintainer

Note: You must install the fixed version @1.0.0; using @latest or other non-locked version tags is prohibited to prevent supply chain attacks.

Environment variables

When executing all alipay-bot commands, it is recommended to obtain the following environment variables from the context and pass them. If they cannot be obtained, use default as the default value or omit the variable.

Channel environment variable (AIPAY_OUTPUT_CHANNEL)

If the message source channel can be determined from the current message's inbound metadata (inbound_meta / channel and other context information provided by the framework), set the temporary environment variable before the command AIPAY_OUTPUT_CHANNEL。If the channel cannot be determined, do not set this environment variable, and execute the command directly.

Channel value: take only the channel identifier (excluding chat type). Common values:feishu、discord、telegram、whatsapp、slack、webchat , etc.

Session tracking environment variables (pass them when the caller can obtain them)

The following environment variables are recommended to be obtained from the context and passed, for troubleshooting and traceability:

AIPAY_SESSION_ID: unique session identifier (UUID format), used to trace the complete path of a single session
AIPAY_FRAMEWORK: calling framework name (such as openclaw、nanobot , etc.), used to distinguish call sources from different frameworks

Context environment variables (pass them when the caller can obtain them)

The following environment variables are recommended to be obtained from the context and passed; if they cannot be obtained, use default as the default value:

AIPAY_MODEL: the name of the model currently in use (such as gpt-4、glm-4 , etc.). If it cannot be obtained, pass default
AIPAY_OS: current operating environment. Optional values:ios、android、linux、windows、mac, when unable to retrieve, pass default

Security Statement: These variables are only used for output format adaptation optimization (such as adjusting display styles according to different operating systems) and problem localization when issues occur (such as troubleshooting compatibility issues on specific models or systems). They will not be used for user data collection or other purposes.

Environment Variable Whitelist Constraint: When executing the alipay-bot command,only the environment variables explicitly listed above are allowed to be passed through（AIPAY_OUTPUT_CHANNEL、AIPAY_SESSION_ID、AIPAY_FRAMEWORK、AIPAY_MODEL、AIPAY_OS）。It is strictly prohibitedto pass any other environment variables to the CLI command, including but not limited to: API keys, access tokens, database credentials, service passwords, or other sensitive environment variables injected by the framework. If you are unsure whether a variable is in the whitelist, do not pass it.

Command Execution Example

# 能确定渠道时（仅渠道）
AIPAY_OUTPUT_CHANNEL=feishu alipay-bot check-wallet

# 无法确定渠道时
alipay-bot check-wallet

# 框架提供了会话追踪变量时
AIPAY_SESSION_ID=<uuid> AIPAY_FRAMEWORK=openclaw alipay-bot check-wallet

# 框架提供了全部变量时（渠道 + 会话追踪 + 上下文参数）
AIPAY_OUTPUT_CHANNEL=feishu AIPAY_SESSION_ID=<uuid> AIPAY_FRAMEWORK=openclaw AIPAY_MODEL=gpt-4 AIPAY_OS=ios alipay-bot check-wallet

All subsequent command templates are written in the alipay-bot xxx format. When actually executing, please add the corresponding environment variable prefix according to the above rules.

Gotchas (Common Pitfalls)

These are easily made mistakes thatmust be avoided：

Directly outputting access_url: When alipay-bot check-wallet returns access_url, the model may directly output that URL, but it should execute alipay-bot apply-wallet to obtain a new authorization link
Reading/analyzing images: The model may attempt to open or recognize the authorization QR code, but it should follow the MEDIA line processing rules to extract the image path, remove the MEDIA line, and integrate the image with text for output
Truncating URLs: The model may compress or truncate the authorization link, but it must be preserved completely character by character
Fabricating authorization codes: The model may make up an authorization code, but it must wait for the user's actual input
Skipping check-wallet: The model may directly execute alipay-bot bind-wallet, but it must first execute alipay-bot check-wallet to check the wallet status
Omitting environment variables: When the message channel can be determined, the command must be prefixed with AIPAY_OUTPUT_CHANNEL=<渠道> ; it is recommended to also pass session tracking and context environment variables (see the "Environment Variables" section for details)
Accessing hidden directories: The model may attempt to read hidden directories (starting with . ), but hidden directories not managed by the framework may contain sensitive data, andit is absolutely prohibitedto access them
Stopping to ask the user for confirmation: The model may, after check-wallet returns, output self-written text such as "Current status: not activated. Continue?" and wait for user confirmation.

Output Rules (highest priority, overriding all other output rules)

Why must it be output as-is?: Changing any single character of the URL in the output will cause the link to become invalid, and the user will be unable to complete authorization/payment. This is not a formatting preference, but a functional hard constraint.

Rule 1: Markdown text → copy character by character

Execute the Markdown text returned by the tool; your reply is that text—copy it character by character, without adding or removing anything
Do not add "Processing for you..." in front, do not add "Please scan the code to complete payment" after, do not wrap it in a code block
Do not rewrite, summarize, translate, or reformat
Prohibitedto wrap the tool execution output in a code block (```)

Rule 2: MEDIA line → extract + remove + integrate

Find the MEDIA: <路径> line from the CLI output, extract the image path; this image is the CLI tool
Remove this MEDIA line from the text
Use the message tool to send the image, and integrate it with the Markdown text for output

Rule 3: JSON output → internal consumption, not directly displayed

When the CLI returns JSON, process it according to field logic (e.g., check code, extract access_url); do not output the raw JSON to the user

CLI commands and output handling:

1. Check the payment capability activation status

Use the system's command execution tool (shell/terminal/exec, etc.) to execute the following command:

alipay-bot check-wallet

Input parameters: None

Output format: JSON

{
  "code": 200 |  500,
  "access_url": "string",
  "message": "string",
  "reason": "string"
}

Branch logic:

code	access_url	Meaning
200	Empty string `""`	Payment capability is activated and authorized
200	Non-empty (contains authorization link)	Payment skill activation has been applied for, but authorization has not yet been completed
500	-	Not activated (never applied) → Directly execute `apply-wallet`, same handling as the previous line

2. Apply to activate the payment skill

Use the system's command execution tool (exec, etc.) to execute the following command:

alipay-bot apply-wallet --agent-name "<当前agent名称>"

Input parameters:

--agent-name: the name of the current agent (required). If the framework provides AIPAY_AGENT_NAMEthrough the system context, use that value; otherwise, if the model can determine the name of the current agent from the conversation context, fill in that name; if it cannot be determined or does not yet exist, set it to an empty string ""。

Note: This command is "apply to activate payment skill". After execution, it will generate an authorization link and QR code. The user needs to click or scan the code to complete the authorization process.

Output format: Markdown text + image

Output example:

您可以[点击支付宝官方链接](https://u)或扫描下方二维码开启我的支付功能

开启后：
- 笔笔支付支付由你授权
- 24小时安全守护，你敢付我敢赔
- 随时可关闭

[Attached: authorization QR code image]

📋 Execute according to the "Output rules"

Output handling rules:

MEDIA line handling: extract the image path in MEDIA: <图片路径> , use the message tool to send the image, and remove the MEDIA line from the text output
Prohibitedto open, read, analyze, or describe the image content
Prohibitedto wrap the CLI output in a code block (```)
Output content as-is: The Markdown content (after removing the MEDIA line) must be output completely as-is; modification, deletion, truncation, or rewriting is prohibited
It is prohibited to add any self-written text before or after the CLI output: do not output explanations such as "Checking for you...", "Detected not activated...". Your reply = the CLI raw Markdown text (after removing the MEDIA line) + image, nothing more

Correct example(after extracting the image path and removing the MEDIA line, integrate the Markdown text with the image for output):
[✅当前环境安全，请放心开启]
请扫码或点击链接，开启支付宝支付功能
[支付宝官方开启链接](<https://u.alipay.cn/xxxxx>)
(At the same time, use the message tool to send the image /tmp/openclaw/alipay-bot-cli/qrcode/wallet-bind-xxx.png）

Follow-up actions:

Normal: Integrate the Markdown text returned by the CLI (after removing the MEDIA line) and the image into one card and output it to the user all at once, then wait for the user to scan the code to complete authorization and return the authorization instruction
Exception: If alipay-bot apply-wallet returns an error, output the error message as-is

3. Bind wallet

Use the system's command execution tool (shell/terminal/exec, etc.) to run the following command:

alipay-bot bind-wallet -c <六位数字授权码>

Input parameters: -c, --code <value>: authorization code (obtained by the user after scanning the QR code, format such as 开启支付功能 xxxx in the authorization command, xxxx part, is a six-digit number)

Output format: Markdown text

Output example:

Binding successful:

[正在校验验证码 xxxx]
[正在进行安全验证]
[开启成功]

支付宝支付功能已开启成功 ✅

Binding failed:

**✗ 支付宝AI付功能授权失败, 请重试**
请确认授权码是否正确，或在5分钟内重新输入
---
您可以[点击支付宝官方链接](<https://u.alipay.cn/xxxxx>)重新开启支付功能
开启后：
- 笔笔支付支付由你授权
- 24小时安全守护，你敢付我敢赔
- 随时可关闭

📋 Execute according to the "Output Rules"

Follow-up actions:

Binding successful: Output the success message returned by the CLI as-is. If in the current conversation context there is a previously paused payment process due to lack of authorization (i.e., the user previously triggered the alipay-pay-for-service skill, but it was paused at Step 1 due to lack of authorization), additionally prompt the user "Authorization is complete, please initiate the payment again"
Binding failed: Output the failure message returned by the CLI as-is, and guide the user to re-initiate the authorization request or retry

4. Unbind wallet / disable payment capability

alipay-bot close-wallet

Input parameters: None

Description: This command will first determine the current wallet status, then decide whether to output a disable link or a link to re-enable the payment capability.

Return scenarios and handling methods:

Scenario A: Currently in a valid bound state

CLI body example:

请点击[支付宝官方链接](<https://u.alipay.cn/xxxxx>)，移步至手机支付宝APP进行关闭吧

At the same time, an additional MEDIA image will be returned.

📋 Execute according to the "Output Rules"

Handling requirements:

Extract the image corresponding to the MEDIA: <图片路径> line
Remove the MEDIA line itself from the text
The Markdown text must be output exactly as-is, character by character; rewriting the disable link is prohibited
Prohibitedto wrap the CLI output in a code block (```)
Do not interpret it as "unbinding has already succeeded"; it means "please go to Alipay to complete the disable operation"
After outputting the disable link, wait for user operation feedback (such as the user informing "already disabled"), then execute alipay-bot check-wallet to confirm the latest status

Scenario B: Currently not actually bound

CLI body example:

您可以[点击支付宝官方链接](<绑定链接>)开启我的支付功能
开启后：
- 笔笔支付支付由你授权
- 24小时安全守护，你敢付我敢赔
- 随时可关闭

At the same time, an additional MEDIA image will also be returned.

📋 Execute according to the "Output Rules"

Handling requirements:

Extract the image corresponding to the MEDIA: <图片路径> line
Remove the MEDIA line itself from the text
Prohibitedto wrap the CLI output in a code block (```)
Do not interpret it as an error; display the result "payment capability can be re-enabled" according to the CLI original text

Scenario C: The locally saved wallet authorization has expired

CLI body example:

检测到您本地保存的支付授权已失效，已为您自动清除。
您可以[点击支付宝官方链接](<绑定链接>)重新开启我的支付功能
开启后：
- 笔笔支付支付由你授权
- 24小时安全守护，你敢付我敢赔
- 随时可关闭

At the same time, an additional MEDIA image will also be returned.

📋 Execute according to the "Output Rules"

Handling requirements:

Extract the image corresponding to the MEDIA: <图片路径> line
Remove the MEDIA line itself from the text
Prohibitedto wrap the CLI output in a code block (```)
Explicitly preserve the CLI original text "Local authorization has expired and been automatically cleared"; do not abbreviate or summarize it on your own

Business process:

Process 1: Payment capability activation and authorization

Trigger condition: The user actively requests to activate the payment feature (e.g., "activate payment feature", "help me enable payment capability")

Execution steps:

Execute alipay-bot check-wallet to check the payment capability activation status
Process according to the result returned by alipay-bot check-wallet :

Case A:code=200 & access_url 为空(activated and authorized)
- Directly output the content of the message field, and the process ends
Case B:code=200 & access_url 非空(applied but not authorized)

▶ Current round action (execute immediately):
1. Execute alipay-bot apply-wallet --agent-name "<agent名称>": obtain a new authorization link and QR code image (do not directly output access_url).<agent名称> Take it from the AIPAY_AGENT_NAMEprovided by the framework; if none, set it to the empty string ""
2. Process the MEDIA line and integrate the output: process the MEDIA line (extract the image path, remove the MEDIA line), and output the Markdown text integrated with the image to the user
3. This round ends → STOP: after outputting,stop immediately, do not add any additional explanatory text, do not summarize the subsequent process, and do not prompt the user on what to do next
▷ Subsequent rounds (triggered only when the user sends a message again; do not execute in the current round):
- After the user scans the QR code and authorizes, they will send an authorization code (format:开启支付功能 xxxx）
- After receiving the authorization code,immediately and automatically execute alipay-bot bind-wallet -c xxxx(pass only the verification code part, i.e., xxxx）
Case C:code=500(not activated / never applied)
- Handle the same as Case B: directly execute alipay-bot apply-wallet --agent-name "<agent名称>", obtain the authorization link and QR code, process the MEDIA line and integrate the output, then STOP and wait for the user's authorization code

Process 2: The user directly provides an authorization code

Trigger condition: The user directly provides an authorization code in the conversation (format:开启支付功能 xxxx), rather than first asking "how to activate"

Execution steps:

Execute alipay-bot check-wallet: check the current wallet status

Process according to the status:

Status	Handling method
Activated and authorized (`code=200 & access_url 为空`)	Skip binding, and tell the user "the payment feature has been activated and authorized, no need to repeat the operation"
Applied but not authorized (`code=200 & access_url 非空`)	Directly use the verification code part of the authorization code already provided by the user, and immediately execute `alipay-bot bind-wallet -c xxxx`(xxxx is the verification code in the authorization code)
Not activated (`code=500`)	Ignore the authorization code already provided by the user, first execute `alipay-bot apply-wallet` to obtain the authorization link, and guide the user to complete authorization before binding

Notes:

Must first execute alipay-bot check-wallet Check the payment capability activation status, and decide subsequent actions based on the returned code and access_url
Authorized activation requires the user to provide an authorization instruction, in the format:开启支付功能 xxxx(note that there is a space between "功能" and the authorization code)
Forging authorization instructions is prohibited; you must wait for the user to actually input it

Output specifications (violating any one = serious error)

Accessing non-framework hidden directories is prohibited

Absolutely prohibitedReading any hidden directory not managed by the current framework (directories starting with . ), as these directories may contain sensitive data. Framework working directories (such as .openclaw/、.claude/ etc.) are framework-managed and are not within the scope of this restriction.

Output method (important)

If the CLI output contains MEDIA: <图片路径> lines, you need to extract the image path, use the message tool to send the image, remove the MEDIA line from the text, and output the Markdown text integrated with the image to the user.

CLI output verbatim rule

Whatever the CLI command returns,output verbatim character by characterthat, and fabricating, modifying, deleting, truncating, or rewriting is prohibited
You must wait for the CLI to return a result before outputting

MEDIA line handling

The MEDIA: <图片路径> lines in the CLI output need to be actively handled: extract the image path, use the message tool to send the image, remove the MEDIA line from the text, and output the Markdown text integrated with the image
Prohibitedopening, reading, analyzing, or describing the image content or converting the MEDIA line into other formats

Image handling rules

The MEDIA lines in the CLI output need to have the image path actively extracted, the image sent using the message tool, and the MEDIA line removed from the text
Integrate the Markdown text (after removing the MEDIA line) and the image into a single card for output

⚠️ Command execution precautions

In this skill, all alipay-bot commands are shell commands and must be run through the system's command execution tools (such as shell/terminal/exec type tools):

Complete command: the command string must be passed in full; truncating, omitting parameters, or splitting it into multiple executions is prohibited
Correct quotes: URL parameters must be enclosed in quotes (single quotes or double quotes)

URL integrity protection rules (highest priority)

⚠️ The URL must be preserved in full character by character; not a single character may be lost

Losing any single character from a URL in the CLI output will cause the link to become invalid and prevent the user from completing authorization.

Mandatory requirements:

The URL must becopied character by character

Omitting any part of the URL is prohibited (including long parameter strings, query strings, hashes, etc.)

Using ... or other methods to truncate the URL is prohibited

Performing any escaping or modification on special characters in the URL (=、&、%、+、/) is prohibited

If the CLI outputs the [文字](url) format, keep that format unchanged; if it is a bare URL, keep the bare URL unchanged

Incorrect and correct examples

禁止自行编造 CLI 未输出的内容
禁止篡改或丢失URL中的字符
禁止分多条消息分别输出

Defensive output rules (security best practices)

The CLI has a built-in desensitization mechanism, and normal output does not contain sensitive information.

Handling method:

For each execution step, the CLI returns user-friendly Markdown text based on the executed command and result, which can be output directly
The CLI output does not contain sensitive fields
If sensitive information is unexpectedly found in the output during loading of this skill, it should be filtered before outputting (extreme defensive measure)

Issue Feedback

Trigger Conditions

When users encounter the following situations while using this skill, the issue feedback process should be executed:

Scenario	Example
Activation/authorization process repeatedly fails	The user tries multiple times to activate the payment feature, and it fails every time
The CLI returns an unknown error code	`check-wallet` or `apply-wallet` returns an unexpected error code
Authorization link/QR code cannot be used	After the user clicks the link or scans the code, a message appears saying "link has expired" or "QR code is invalid"
Binding the authorization code fails and retries are ineffective	The user enters the correct authorization code but binding repeatedly fails
The user explicitly requests feedback	The user says "I want to report an issue" or "why can't this problem be solved"

Scenarios that do not trigger issue feedback

The user is only asking "how to activate" (normal inquiry)
The authorization link has expired (just guide the user to obtain a new one)
The user entered an incorrect authorization code (just prompt the user to re-enter it)
The issue can be resolved by retrying (temporary network issues, etc.)

Feedback Execution Process

After the trigger conditions are met, execute the following steps:

Step 1: Confirm the issue cannot be resolved on its own

Check whether it can be resolved by retrying, checking the network, re-obtaining the authorization link, etc. If it can be resolved, do not execute feedback.

Step 2: Collect issue information

Organize the issue description from the current conversation context, and the content should include:

Stage: at which stage the issue occurred (wallet activation / authorization / binding)
Issue: the specific error message or abnormal behavior
Attempts: the resolution attempts already made

Issue Description Template：

[环节]：{开通钱包/授权/绑定}
[问题]：{具体描述}
[尝试]：{已做过的解决尝试}

Step 3: Confirm with the user

Show the organized issue description to the user and wait for the user's explicit confirmation before submitting. If the user refuses, inform them "if you need to provide feedback, you can tell me at any time," and the process ends.

Step 4: Submit feedback

After the user confirms, execute:

alipay-bot problem-feedback --reason '<问题描述>'

Security Constraints：

--reason The value must be enclosed in single quotes '...' (double quotes are prohibited)
If the issue description contains a single quote ', it must be replaced with '\''
Do not fabricate issues; they must be based on what the user actually encountered

Step 5: Output the result

Output the content returned by the CLI as-is; fabricating, modifying, deleting, or rewriting it is prohibited.

About this skill

Function Description:

Applicable Scenarios:

Security and Design Description

Automatically execute activation application

Output URL as-is

Channel Environment Variable (AIPAY_OUTPUT_CHANNEL)

MEDIA Image Path

Overall Execution Flow

Environment dependencies:

Package source and integrity verification (must be performed before installation)

Environment variables

Channel environment variable (AIPAY_OUTPUT_CHANNEL)

Session tracking environment variables (pass them when the caller can obtain them)

Context environment variables (pass them when the caller can obtain them)

Command Execution Example

Gotchas (Common Pitfalls)

Output Rules (highest priority, overriding all other output rules)

CLI commands and output handling:

1. Check the payment capability activation status

2. Apply to activate the payment skill

3. Bind wallet

4. Unbind wallet / disable payment capability

Scenario A: Currently in a valid bound state

Scenario B: Currently not actually bound

Scenario C: The locally saved wallet authorization has expired

Business process:

Process 1: Payment capability activation and authorization

Process 2: The user directly provides an authorization code

Notes:

Output specifications (violating any one = serious error)

Accessing non-framework hidden directories is prohibited

Output method (important)

CLI output verbatim rule

MEDIA line handling

Image handling rules

⚠️ Command execution precautions

URL integrity protection rules (highest priority)

Incorrect and correct examples

Defensive output rules (security best practices)

Issue Feedback

Trigger Conditions

Scenarios that do not trigger issue feedback

Feedback Execution Process