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 essentially a boilerplate label with no substantive content. It repeats the skill name as its only trigger term, provides no concrete actions or capabilities, and lacks any explicit guidance on when Claude should select it. It would be nearly indistinguishable from any other business automation skill in a large skill library.
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, prepare billing documents, or needs an invoice template.'
Remove the duplicate trigger term and expand with natural variations users would say: 'invoice', 'bill', 'billing', 'create invoice', 'invoice template', 'payment request'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Invoice Generator', 'Business Automation') but does not describe any concrete actions. There is no mention of what the skill actually does—e.g., creating invoices, calculating totals, formatting line items, exporting to PDF. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it.' There is no explicit 'Use when...' clause and no meaningful explanation of capabilities beyond the skill name itself. | 1 / 3 |
Trigger Term Quality | The only trigger term listed is 'invoice generator' repeated twice. It misses natural variations users would say such as 'create an invoice', 'billing', 'generate a bill', 'invoice template', 'send invoice', etc. | 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 about what it does versus other business/document skills means overlap is still possible. | 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 a hollow placeholder that contains no actionable content whatsoever. It describes what an invoice generator skill would do in abstract terms but provides no code, no concrete steps, no examples, and no real guidance. 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 create a PDF invoice from structured data).
Define a clear multi-step workflow: gather invoice data → validate required fields → generate invoice document → verify output, with explicit validation checkpoints.
Include at least one complete input/output example showing sample invoice data and the resulting generated invoice.
Remove all meta-description sections ('When to Use', 'Capabilities', 'Example Triggers') that describe the skill rather than teaching how to perform the task.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual instructions, code, or actionable content. Every section restates the same vague information. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific steps, no examples of invoice generation. Phrases like 'Provides step-by-step guidance' and 'Generates production-ready code' describe capabilities without demonstrating any of them. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill merely claims it provides 'step-by-step guidance' without actually containing any steps. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed files, no structured navigation, and no separation of concerns. There is nothing to progressively disclose because there is no substantive content. | 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
3e83543
- 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.