AC openclaw-finance-voucher
Generate import-ready Chinese finance workbooks from monthly input VAT invoice exports or bank statement exports. Use when OpenClaw or Codex must turn Excel invoice exports containing sheets such as 信息汇总表, 发票基础信息, 进项税, 进项税（有数量的）, 凭证/凭证转出, and 科目编码, or bank detail exports containing 账户明细, into complete financial workbooks with source tables, voucher rows, account-code mapping, bank-fee aggregation, special-ticket handling, and audit notes.
Generate import-ready Chinese finance workbooks from monthly input VAT invoice exports or bank statement exports.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 55/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
- 40Consistency. Frontmatter name (openclaw-finance-voucher) differs from the folder (china-finance-voucher)
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 34 steps
- 100Execution cost. Instruction body is 866 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
- +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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 442: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 34 items
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.