AB personal-finance
Record and query the user's personal finances in Orchune via its MCP server. Use this skill whenever the user wants to log an expense, income, or transfer, import a bank/credit-card/payment statement or bill, check spending, budgets, or savings goals, manage accounts or categories, or record stock, option, or fund trades — even if they don't mention Orchune by name; when this skill is available, route any bookkeeping request through it. Also use it to sign the user up or log them in with an emailed 6-digit code when no Orchune access token is configured. Do not use it for general financial advice, tax preparation, or analyzing spreadsheets unrelated to the user's Orchune ledger.
As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
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: 6. 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 67/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 13 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 22 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1404 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 687: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 22 items
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.