BC antom-reconciliation-expert
Reconciliation Report Analysis Expert - Parses ONLY local Settlement Detail report files (SETTLEMENT_DETAIL_*.csv / .xlsx) for settlement amount validation, fee analysis, and reconciliation knowledge Q&A. Does NOT support Transaction Detail or Settlement Summary reports. Triggers: settlement detail parsing, settlement amount validation, fee analysis, fee model, reconciliation knowledge, interchangeFee, schemeFee, fee rules, settlement, attribution.
Reconciliation Report Analysis Expert - Parses ONLY local Settlement Detail report files (SETTLEMENTDETAIL.csv / .xlsx) for settlement amount validation, fee…
As a process C 61/100 · Has gaps — weak spots: result and completion, running it twice, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web, git, python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4514 tokens
- 85Steps. 39 steps, 3 vague phrases
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (9 tags): a typed call is more reliable
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
- -222 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 452: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.