BD mobile_pay_bill_ocr
仅在用户明确提及“支付宝账单”、“微信支付记录”、“交易截图”、“支付明细”、“移动支付账单”等特定词汇时触发,用于识别并结构化提取移动支付交易截图中的时间、商户、金额、收支类型等信息。不适用于通用OCR或非支付类票据识别。
仅在用户明确提及“支付宝账单”、“微信支付记录”、“交易截图”、“支付明细”、“移动支付账单”等特定词汇时触发,用于识别并结构化提取移动支付交易截图中的时间、商户、金额、收支类型等信息。不适用于通用OCR或非支付类票据识别。
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
IntegrationAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenreferences/api-docs.md:47High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"merchantNo": "0035…PeM",
quoted
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "required_env_vars" - note
frontmatter-keyunknown frontmatter key "optional_env_vars" - note
frontmatter-keyunknown frontmatter key "primary_credential" - note
frontmatter-keyunknown frontmatter key "dependencies" - note
frontmatter-keyunknown frontmatter key "permissions" - note
frontmatter-keyunknown frontmatter key "input" - note
frontmatter-keyunknown frontmatter key "output"
Process rating: all ten parameters 41/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
- 40Consistency. Frontmatter name (mobile_pay_bill_ocr) differs from the folder (mobile-pay-bill-ocr)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 14 steps
- 100Execution cost. Instruction body is 780 tokens
- 100Running it twice. No mutating operations
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)
- +3Description length 112: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Structure: 16 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (3 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.
External checks
ClawHub: clean
This skill does what it says: it sends user-selected mobile payment screenshots to Scnet's OCR API and returns structured transaction data, with prominent privacy warnings.
LLM: benign (high) · VirusTotal: · 12 Aug 2026