SKILLEMALL.ai
RU Sign in

BF invoice-ocr

发票 OCR 识别技能。扫描文件夹中的发票文件（PDF/图片），调用阿里云 OCR API 识别发票信息并导出到 Excel 表格。支持 17+ 种发票类型（增值税发票、火车票、出租车票、机票行程单、定额发票、机动车销售发票、过路过桥费发票等）。使用场景：(1) 用户提到"发票识别"、"发票统计"、"发票整理"、"发票汇总" (2) 用户需要批量处理发票 (3) 用户提到阿里云 OCR 识别发票。**重要：首次使用必须先配置阿里云凭证，主动向用户索要 AccessKey ID 和 AccessKey Secret，或引导用户运行 --config 命令自行配置。**

ClawHub Agent Skills author: 1054570699 v1.0.0 MIT-0 5 files body ≈ 505 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

As a process F 31/100 · Will not run — References files that are not bundled: references/aliyun-ocr-api.md

IntegrationExcelFinanceInfrastructureData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
88/100
safety, quality, tests
Safety 60%
100
Quality 40%
69
Run on models
none yet
Process rating
F
31/100
Will not run
References files that are not bundled: references/aliyun-ocr-api.md
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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 · 0

✓ No critical or high findings

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: references/aliyun-ocr-api.md

Process rating: all ten parameters 31/100

Will not run. References files that are not bundled: references/aliyun-ocr-api.md
  • 0Tools and files. 1 referenced file(s) missing: references/aliyun-ocr-api.md
  • 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 (invoice-ocr) differs from the folder (invoice-recognize)
  • 100Steps. 11 steps
  • 100Execution cost. Instruction body is 505 tokens
  • 100Running it twice. No mutating operations
  • low 10 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

  • +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 286: enough signal without eating the budget
  • +4Structure: 15 headings
  • +3Step-by-step instructions: 11 items
  • +4Has examples (6 code blocks)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.

External checks

ClawHub: suspicious
The skill matches its invoice-OCR purpose, but it needs review because it recommends collecting cloud AccessKey secrets in chat and uploads invoice files to Alibaba Cloud.
LLM: suspicious (high) · VirusTotal: · 29 May 2026