CtrlK
CommunityDocumentationLog inGet started
Tessl Logo

invoice-generator

Install with Tessl CLI

npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill invoice-generator
What are skills?

Invoice Generator - Auto-activating skill for Business Automation. Triggers on: invoice generator, invoice generator Part of the Business Automation skill category.

Overall
score

19%

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Activation

7%

This description is essentially a placeholder that provides almost no useful information for skill selection. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The redundant trigger term and reliance on category labels instead of actual capability descriptions make this ineffective for Claude to choose appropriately among multiple skills.

Suggestions

Add specific actions the skill performs, e.g., 'Creates professional invoices with line items, calculates totals and taxes, exports to PDF format'

Include a 'Use when...' clause with natural trigger scenarios, e.g., 'Use when the user needs to create invoices, generate bills, or produce billing documents for clients'

Expand trigger terms to include natural variations: 'invoice', 'bill', 'billing', 'create invoice', 'generate bill', 'client billing', 'payment request'

DimensionReasoningScore

Specificity

The description only names the skill ('Invoice Generator') without describing any concrete actions. There are no specific capabilities listed like 'create invoices', 'calculate totals', 'add line items', or 'export to PDF'.

1 / 3

Completeness

The description fails to answer 'what does this do' beyond the name, and the 'when' guidance is just a category label ('Business Automation') rather than explicit trigger scenarios. No 'Use when...' clause is present.

1 / 3

Trigger Term Quality

The trigger terms listed are redundant ('invoice generator, invoice generator') and miss natural variations users would say like 'create invoice', 'billing', 'generate bill', 'make an invoice', or 'invoicing'.

1 / 3

Distinctiveness Conflict Risk

While 'invoice' is somewhat specific, the lack of detail about what kind of invoices or what actions are supported means it could overlap with other billing, accounting, or document generation skills.

2 / 3

Total

5

/

12

Passed

Implementation

0%

This skill content is essentially a placeholder template with no actual instructional value. It contains only meta-descriptions of what an invoice generator skill might do, without any concrete implementation details, code examples, or actionable guidance. The content fails on all dimensions by being verbose yet empty of substance.

Suggestions

Add executable code examples showing how to generate invoices (e.g., using Python with libraries like reportlab, weasyprint, or invoice generation APIs)

Define a clear workflow: gather invoice data → validate required fields → generate PDF/document → save/send, with validation checkpoints

Include concrete input/output examples showing invoice data structure and the resulting invoice format

Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with specific, actionable instructions

DimensionReasoningScore

Conciseness

The content is padded with generic boilerplate that provides no actionable information. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that waste tokens without teaching Claude anything specific.

1 / 3

Actionability

There is zero concrete guidance - no code, no commands, no specific steps, no examples of actual invoice generation. The content describes what the skill supposedly does rather than instructing how to do it.

1 / 3

Workflow Clarity

No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none.

1 / 3

Progressive Disclosure

The content is a monolithic block of vague descriptions with no references to detailed materials, no code examples to link to, and no structured navigation to additional resources.

1 / 3

Total

4

/

12

Passed

Validation

69%

Validation11 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

description_trigger_hint

Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata' field is not a dictionary

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

body_steps

No step-by-step structure detected (no ordered list); consider adding a simple workflow

Warning

Total

11

/

16

Passed

Reviewed

Table of Contents

ActivationImplementationValidation

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.