AC organizze
Runs Organizze personal finance API operations via Node.js CLI scripts: accounts, categories, transactions (filters, tag grouping), credit cards (invoices, payments), and transfers. Use when the user works with Organizze, budgets, expenses, income, categories, bank accounts, credit card bills, transfers, or asks to query or change their Organizze data through the terminal.
As a process C 62/100 · Has gaps — weak spots: result and completion, consistency
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
read-dotenvREADME.md:18Reads a .env filecp .env.example .env
-
low Exfiltration
read-dotenvsrc/credentials.js:11Reads a .env file (detector / deny-list definition)'Copy .env.example to .env and fill in your credentials.'
detector
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "credentials" - note
frontmatter-keyunknown frontmatter key "env"
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (organizze) differs from the folder (organizze-skill)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 13 steps
- 100Execution cost. Instruction body is 1587 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (14 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
- +1No license
- +2Single-language instructions
- +3Description length 375: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.