invoice-organizer

Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.

Quality

63%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/invoice-organizer/SKILL.md

Quality

Content

56%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 actionable with a clear, validated workflow, but it is verbose and monolithic: redundant sections inflate token cost and no content is split into reference files despite the length.

Suggestions

Remove redundant sections — merge 'What This Skill Does' into 'Instructions' and drop 'Common Organization Patterns' (already shown in the organization plan) to cut significant tokens.

Move the four long Examples and the pattern catalogs into separate reference files (e.g. examples.md) and link them one level deep from SKILL.md.

Add an explicit post-execution validation step (e.g., verify file count and that every renamed file landed in the expected folder) to lift workflow clarity from 4 to 5.

Dimension	Reasoning	Score
Conciseness	The ~440-line body has several padded/redundant sections — 'What This Skill Does' duplicates 'Instructions', 'Common Organization Patterns' repeats folder trees already shown in the plan, 'Pro Tips' and 'Related Use Cases' are filler — making it noticeably verbose.	2 / 5
Actionability	Provides concrete, mostly executable guidance — `find`, `mkdir -p`, `cp`/`mv` commands, a CSV schema, filename patterns, and extraction patterns ('Invoice Date:', 'Amount Due:') — with only the text-extraction step left abstract rather than coded.	4 / 5
Workflow Clarity	The 7-step Instructions are clearly sequenced with a pre-execution approval checkpoint ('Process [X] files? (yes/no)') and a flag-for-review feedback loop; the only gap is a lack of explicit post-execution output validation.	4 / 5
Progressive Disclosure	The skill is a single monolithic file with clear section headers but no external references, and substantial content (four long examples, pattern catalogs) that would fit better in separate files is inlined.	3 / 5
	Total	13 / 20 Passed

Description

71%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 specific and action-oriented with a clear functional niche, but it lacks an explicit 'Use when...' trigger clause, which limits completeness and slightly weakens trigger quality.

Suggestions

Add an explicit 'Use when...' trigger clause naming common user phrases (e.g., 'Use when preparing taxes, sorting receipts, or organizing invoices and bills').

Include a few natural synonyms and file extensions (bills, expenses, .pdf, scanned receipts) to broaden trigger coverage.

Tighten the closing marketing line ('Turns hours of manual bookkeeping into minutes of automated organization') which is promotional fluff rather than capability information.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders' — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms like 'invoices', 'receipts', 'tax preparation', and 'bookkeeping', but omits common synonyms (bills, expenses) and file extensions (.pdf), so a few natural terms are missing.	4 / 5
Distinctiveness Conflict Risk	The invoice/receipt/tax-preparation niche is mostly distinct with only minor overlap risk against generic document or expense skills, though the lack of explicit triggers slightly weakens separation.	4 / 5
	Total	16 / 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: davepoon/buildwithclaude
Path: plugins/all-skills/skills/invoice-organizer/SKILL.md
Commit: a9fa86d

Reviewed: about 19 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.