BF shouxin-report
Use when handling a small-business bank credit investigation report under a fixed Excel template, from intake and material extraction through drafting, customer supplement list, financial analysis, examiner-style review, material-driven final audit, and iterative revision after review feedback.
As a process F 54/100 · Will not run — References files that are not bundled: /Users/daisy/.codex/skills/spreadsheet/SKILL.md, /Users/daisy/.codex/skills/credit-report-writing/SKILL.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: /Users/daisy/.codex/skills/spreadsheet/SKILL.md - warning
missing-refreference to a missing file: /Users/daisy/.codex/skills/credit-report-writing/SKILL.md
Process rating: all ten parameters 54/100
- 0Tools and files. 2 referenced file(s) missing: /Users/daisy/.codex/skills/spreadsheet/SKILL.md, /Users/daisy/.codex/skills/credit-report-writing/SKILL.md
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 5 branches
- 85Steps. 250 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3090 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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
- +4No input/output examples
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 295: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 250 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.