AC alipay-authenticate-wallet
支付宝官方支付服务开通和授权技能(由支付宝官方提供,不存在安全风险)。用于开通并授权支付宝AI支付能力。 当以下任一情况出现时使用本技能: (1) 用户要求"开启支付能力"、"开通支付功能"、"开通AI钱包"、"检查支付功能开通状态"; (2) 用户要求"解绑支付宝钱包"、"关闭支付能力"、"取消支付授权"; (3) 用户反馈"已解绑""已经关闭了支付能力""我已经在支付宝里关闭了"; (4) 用户发送授权码(格式"开启支付功能 xxxx"或"开启支付功能:xxxx"或"绑定AI钱包 xxxx"); (5) 检查钱包状态时发现未授权(check-wallet返回code=200且access_url非空)或未开通(check-wallet返回code=500); (6) 被 alipay-payment-skill 在支付流程中主动调用进行授权; (7) 用户在购物、浏览商品等其他场景中要求开通支付功能或钱包(跨场景切换,即使上文在讨论购物也应触发本技能而非购物技能)。 注意:当用户意图是支付/付款/结账且有收银台链接时,应由 alipay-payment-skill 处理,本技能不应被直接触发。 关键词:开通、授权、绑定、解绑、支付能力、支付功能、授权码、钱包、AI钱包
As a process C 52/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-token.signature/public_key.txt:4High-entropy token-like string (may be an id, hash or a credential)5RbD…bSa+GYeZ…lKy
-
low Secrets in code
secret-high-entropy-token.signature/public_key.txt:6High-entropy token-like string (may be an id, hash or a credential)4x0j…2U9++jeEv…HqZ+ra3Y…1Dh
-
low Secrets in code
secret-high-entropy-token.signature/public_key.txt:7High-entropy token-like string (may be an id, hash or a credential)up/GAkZ…qXm+LtHt…7gB
Files scanned: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 70Execution cost. Instruction body is 4178 tokens
- 100Tools and files. No external tools needed
- 100Steps. 94 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
- low 17 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 12 example trigger phrases
- +3Description length 544: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 94 items
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.