AF invoice-generator
Generate professional PDF invoices from command-line input or templates. Use when the user wants to: create an invoice, generate a bill, send a payment request, create a receipt for services/products, or manage invoice templates. Triggers on "create invoice", "generate bill", "invoice for", "make a receipt", "payment request", "bill template".
As a process F 42/100 · Will not run — References files that are not bundled: scripts/invoice_template.html, assets/logo.png
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 3. 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: Generate professional PDF invoices from command-line input or temp… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
missing-refreference to a missing file: scripts/invoice_template.html - warning
missing-refreference to a missing file: assets/logo.png
Process rating: all ten parameters 42/100
- 0Tools and files. 2 referenced file(s) missing: scripts/invoice_template.html, assets/logo.png
- 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
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (invoice-generator) differs from the folder (eternal-invoice-generator)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 11 steps
- 100Execution cost. Instruction body is 472 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
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 345: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 11 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.