AD envelopebudget
Manage budgets, transactions, accounts, envelopes, and payees via the EnvelopeBudget.com API. Use when user asks about: (1) checking balances or budget status, (2) listing/creating/updating transactions, (3) managing envelopes (budget categories), (4) account balances or reconciliation, (5) transferring money between accounts or envelopes, (6) spending reports or category breakdowns, (7) payee management, (8) anything related to budgeting, expenses, or financial tracking in EnvelopeBudget.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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: 4. 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: Manage budgets, transactions, accounts, envelopes, and payees via … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 46/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 6 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 411 tokens
- 100Running it twice. No mutating operations
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 494: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.