invoice-generator
Invoice Generator - Auto-activating skill for Business Automation. Triggers on: invoice generator, invoice generator Part of the Business Automation skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/19-business-automation/invoice-generator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is extremely thin and template-like, providing almost no useful information beyond the skill's name. It lacks concrete actions, meaningful trigger terms, and explicit guidance on when Claude should activate it. It reads like auto-generated boilerplate rather than a crafted description.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates professional invoices with line items, tax calculations, totals, and payment terms.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create an invoice, generate a bill, make a billing document, or needs invoice templates.'
Include natural keyword variations users would say: 'invoice', 'bill', 'billing', 'receipt', 'create invoice', 'invoice PDF', 'payment document'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Invoice Generator', 'Business Automation') but provides no concrete actions. It does not describe what the skill actually does—no mention of creating invoices, calculating totals, formatting, exporting, etc. | 1 / 3 |
Completeness | The 'what' is essentially absent beyond the name, and the 'when' is not explicitly addressed. There is no 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'invoice generator' repeated twice. It misses natural variations users would say like 'create an invoice', 'billing', 'generate invoice', 'invoice template', or 'send invoice'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'invoice generator' is somewhat specific to a niche (invoicing), which reduces conflict with unrelated skills. However, the lack of detail means it could overlap with other business/document generation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty placeholder with no substantive content. It contains only generic boilerplate descriptions and trigger examples but provides absolutely no actionable guidance on invoice generation—no code, no templates, no workflows, no tool usage, and no references to supporting materials. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable code for generating invoices (e.g., a Python script using a library like reportlab or weasyprint to produce a PDF invoice from structured data).
Define a clear workflow with steps: gather invoice data → validate required fields → generate invoice document → verify output, including validation checkpoints.
Include a specific invoice template or schema (JSON/dict structure) showing required fields like line items, tax calculations, totals, and payment terms.
Remove all boilerplate sections (Purpose, When to Use, Capabilities, Example Triggers) and replace with actionable content that teaches Claude how to actually generate invoices.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, provides no specific information about invoice generation, and wastes tokens on vague capability descriptions and trigger examples that add no value. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no templates, no invoice format specifications, no library recommendations. Every section describes rather than instructs, offering only abstract promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps for generating an invoice, no validation checkpoints, no sequence of operations. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of placeholder text with no references to supporting files, no structured navigation, and no bundle files to support it. There is no meaningful content to organize in the first place. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.