invoice

A printable invoice page — sender + recipient block, line items table, tax breakdown, totals, and payment instructions. Use when the brief mentions "invoice", "bill", "billing statement", or "发票".

Quality

98%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, actionable spec with a clear workflow and a ready-to-use output contract, scoring well across all dimensions. The only gap is the dangling DESIGN.md reference with no matching bundle file.

Suggestions

Either add a DESIGN.md bundle file or remove the 'Read DESIGN.md' step so no reference points to a missing file.

Consider noting which design-system sections (color, typography, layout, components) the invoice must reflect, since the frontmatter declares design_system.requires: true.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — a one-line goal, a tight workflow, a copy-paste output contract, and a single print note — with no concept over-explanation or padding.	5 / 5
Actionability	Concrete layout spec (column names 'description / qty / unit / amount', right-aligned totals block, payment instructions) plus a complete artifact output contract make the guidance copy-paste ready.	5 / 5
Workflow Clarity	A clear 3-step sequence (read design, layout, print stylesheet) for a simple single-purpose generation skill with no destructive/batch operation; the simple-skill exception permits 5 for an unambiguous single action.	5 / 5
Progressive Disclosure	Well-organized into Workflow and Output-contract sections and under 50 lines with no bundle files, but the body references DESIGN.md with no accompanying file present, a minor unresolved navigation gap that keeps it below a clean 5.	4 / 5
	Total	19 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is lean, concrete, and fully answers both what the skill produces and when to invoke it, with natural multilingual trigger terms. It is written in third person with no padding or over-claims.

Dimension	Reasoning	Score
Specificity	Names five concrete structural components (sender/recipient block, line items table, tax breakdown, totals, payment instructions), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly answers both 'what' (a printable invoice page with named components) and 'when' ('Use when the brief mentions...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger terms 'invoice', 'bill', 'billing statement' plus the Chinese synonyms '发票'/'账单' give comprehensive coverage including localized synonyms users would actually say.	5 / 5
Distinctiveness Conflict Risk	A printable-invoice niche with distinct, multilingual triggers has minimal overlap risk with other skills, matching the clear-niche anchor.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/invoice/SKILL.md
Commit: 1a7a23d

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.