BC alipayplus-integration
Alipay+ Payment Integration Assistant. Helps Acquirers and Mobile Service Providers quickly integrate Alipay+ payments, including customer-presented mode payment and merchat-presented mode payment. This skill can help on configuration generation, signature verification testing, asynchronous notification debugging (ACQP only), and reconciliation file processing.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Secrets in code
secret-private-keyreferences/signature-guide.md:107Private key material (key header without key body; quoted — discussed, not commanded)String pem = privateKey.replace("-----BEGIN PRIVATE KEY----- …header onlyquoted -
medium Secrets in code
secret-private-keyreferences/signature-guide.md:390Private key material (key header without key body; quoted — discussed, not commanded)String pem = privateKey.replace("-----BEGIN PRIVATE KEY----- …header onlyquoted -
medium Exfiltration
exfil-webhook-urlreferences/webhook-guide.md:729Webhook / callback URL commonly used for exfiltration (verify the destination) (documentation of a security skill)# Example: https://abc1….io/alipayplus/notify
security skill -
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Bash WebFetch
-
low Secrets in code
secret-private-keyreferences/config-template.json:8Private key material (placeholder value)"privateKey": "-----BEGIN PRIVATE KEY----- …",
placeholder -
low Secrets in code
secret-private-keyscripts/generate-config.sh:133Private key material (placeholder value)"privateKey": "-----BEGIN PRIVATE KEY----- …",
placeholder
Files scanned: 16. 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 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (alipayplus-integration) differs from the folder (skill-alipayplus-integration)
- 50When it triggers. No condition that starts the skill
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 79 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 1812 tokens
- 100Running it twice. Mutating operations check current state
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -218 emoji in the instructions: noise for the model
- -32 of 5 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 363: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 79 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.