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

58%

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 ./invoice-organizer/SKILL.md

Quality

Content

50%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 concrete commands and templates, but it is markedly verbose and inlines content that should be split into reference files, and its batch workflow lacks post-execution validation.

Suggestions

Trim or move the four full examples, organization-pattern catalog, and Pro Tips into a separate references file to reduce token load and improve progressive disclosure.

Add a post-execution validation step (e.g., verify expected file count at destinations, flag mismatches, retry on failure) to satisfy the batch-operation feedback-loop requirement.

Replace the abstract extraction guidance ("Use text extraction", "Look for common patterns") with a concrete runnable snippet or a reference to one.

Dimension	Reasoning	Score
Conciseness	The ~440-line body is noticeably verbose, repeating organization patterns, four full examples, pro tips, and tangential sections that pad the skill well beyond what Claude needs.	2 / 5
Actionability	Provides concrete, executable shell commands (find, mkdir, cp, mv), a precise filename format, and a CSV schema, though the extraction step is described abstractly rather than with runnable code.	4 / 5
Workflow Clarity	A clear 7-step sequence exists with a pre-execution approval checkpoint, but this batch operation lacks a post-execution validation/feedback loop, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Section headers give some structure, but the skill is a monolithic single file with no bundle references, and content that belongs in separate files (examples, org patterns, special cases) is fully inlined.	3 / 5
	Total	12 / 20 Passed

Description

66%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 covers a clear niche with natural trigger terms, but it lacks an explicit "Use when..." clause, which caps completeness and limits its value as a trigger signal.

Suggestions

Add an explicit "Use when..." clause naming concrete trigger phrases (e.g., "Use when organizing invoices or receipts for taxes, expense reports, or bookkeeping").

Include file extensions and synonyms (invoices, receipts, .pdf, .jpg, expense documents) to broaden trigger-term coverage toward anchor 5.

Optionally mention the CSV summary output as a concrete capability to round out specificity.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders" — with only minor gaps (e.g., no mention of output/CSV generation).	4 / 5
Completeness	The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural user terms like "invoices", "receipts", "tax preparation", and "bookkeeping", but omits synonyms and file extensions (.pdf, .jpg) that anchor 5 requires.	4 / 5
Distinctiveness Conflict Risk	The invoice/receipt tax-preparation niche is mostly distinct with clear triggers, though there is minor overlap risk with general file-organizer skills.	4 / 5
	Total	15 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ComposioHQ/awesome-claude-skills
Path: invoice-organizer/SKILL.md
Commit: be2a406

Reviewed: 3 days 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.