AC infoxmed-qr-generator
Use when the user asks to generate infoxmed VIP membership activation QR codes, batch QR codes, or mentions infoxmed membership cards. Triggers on keywords like infoxmed, VIP QR, membership activation QR, member card QR code generation.
As a process C 64/100 · Has gaps — weak spots: result and completion, inputs and preconditions
How to improve
For the model run — optional
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Exfiltration
exfil-secret-in-urlSKILL.md:122Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)"https://api.infox-med.com/system/batchGenerateVipQr?password=…&agent=…&count=1&cardName=…&vipCarType=…×=…" \
placeholder -
low Exfiltration
exfil-secret-in-urlSKILL.md:129Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)Invoke-WebRequest -Uri "https://api.infox-med.com/system/batchGenerateVipQr?password=…&agent=…&count=1&cardName=…&vipCarType=…
vendor-hostquoted -
low Exfiltration
net-credential-useSKILL.md:129Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host)Invoke-WebRequest -Uri "https://api.infox-med.com/system/batchGenerateVipQr?password=…&agent=…&count=1&cardName=…&vipCarType=…
vendor-host -
low Exfiltration
exfil-secret-in-urlSKILL.md:164Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)GET https://api.infox-med.com/system/batchGenerateVipQr?password=…&agent=…&count=1&cardName=半年卡&vipCarType=2×=1000
placeholder
Files scanned: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 64/100
- 0Result and completion. Does not say what the result is
- 30Inputs and preconditions. Does not say what the process needs to start
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1285 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +1No license
- +2Single-language instructions
- +3Description length 236: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.
External checks
ClawHub: suspicious
This QR-code generator does its advertised job, but it asks for an API password and stores it persistently in unsafe local places.
LLM: suspicious (high) · 28 May 2026