AC yoooclaw-expense-tracker-en
Extract personal consumption transactions (takeaway, express delivery, payment, shopping, taxi, gas, credit card repayment, transfer, etc.) from mobile phone notifications, summarize them by category and time, and give the total amount. Trigger: How much you spent/expense/consumption/bill/expense/expenditure/this week/this month/last month/recently/today + spend/money/consumption/how much you spent on takeout/how much you spent on a taxi/how much gas you paid/how much you paid.
Extract personal consumption transactions (takeaway, express delivery, payment, shopping, taxi, gas, credit card repayment, transfer, etc.) from mobile phone…
As a process C 60/100 · Has gaps — weak spots: when it triggers, running it twice, progress reporting
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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Extract personal consumption transactions (takeaway, express deliv… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 60/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 11 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Steps. 43 steps, 4 vague phrases
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2360 tokens
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)
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 482: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 43 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.