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 ./plugins/all-skills/skills/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 delivers a genuinely actionable, well-sequenced procedure with concrete commands, templates, and approval checkpoints. Its weaknesses are bloat from repeated sections and the absence of both post-batch validation and any reference-file split for examples and folder patterns.

Suggestions

Add a post-execution validation step (e.g., compare file counts before/after, spot-check renamed copies) to lift workflow clarity above the batch-operation cap.

Move the "Examples" and "Common Organization Patterns" sections into references/ files and keep a concise pointer in SKILL.md.

Merge "What This Skill Does" into "Instructions" and trim "Related Use Cases" to eliminate duplicated content.

Name concrete extraction tooling (e.g., pdftotext or a Python library) instead of the vague "use text extraction".

Dimension	Reasoning	Score
Conciseness	The ~440-line body is noticeably verbose with several padded/duplicated sections: "What This Skill Does" restates the "Instructions" section, "Common Organization Patterns" repeats folder trees already shown in step 5, and "Related Use Cases"/"Pro Tips" add little actionable value. It avoids the score-1 territory of explaining concepts Claude already knows, but the redundancy is extensive rather than incidental.	2 / 5
Actionability	Mostly executable guidance: concrete commands (`find . -type f \( -name "*.pdf" ... \)`, `mkdir -p "Invoices/2024/Software/Adobe"`, `cp`/`mv`), an exact filename spec (`YYYY-MM-DD Vendor - Invoice - Description.ext`), and a concrete CSV header. It falls short of 5 because steps like "Use text extraction to read invoice content" and "Read visible text from images" name no tool or command.	4 / 5
Workflow Clarity	The 7-step sequence is clearly ordered with a pre-execution approval checkpoint ("Process [X] files? (yes/no)") and fallback flagging for unclear files. However, this is a batch file operation with no post-execution validation (e.g., verifying copy counts or file integrity), so the batch-operation cap of 3 applies.	3 / 5
Progressive Disclosure	No bundle files exist (no references/, scripts/, or assets/), so everything lives in one well-headered ~440-line SKILL.md. Section structure is good, but content that clearly belongs in separate files — four full "Examples" scenarios, "Common Organization Patterns", "Handling Special Cases" — is inlined, matching the anchor-3 pattern rather than a 4 with appropriately split content.	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 communicates a clear niche with several concrete, verifiable actions and natural vocabulary, but it omits any explicit "Use when..." trigger guidance, capping its completeness. Trimming the promotional closing sentence in favor of trigger phrases would lift it substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user mentions invoices, receipts, tax preparation, expense organization, or sorting financial documents."

Replace the marketing sentence "Turns hours of manual bookkeeping into minutes of automated organization" with capability facts such as CSV/summary generation.

Add common synonyms and formats ("expenses", "PDF", "scanned receipts") to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The description lists four concrete actions — "reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders" — matching the several-specific-actions-with-minor-gaps anchor. It falls short of 5 because capabilities like CSV/summary generation are absent and "key information" is generic, with the closing sentence being marketing fluff rather than capability.	4 / 5
Completeness	The "what" is clearly answered, but there is no "Use when..." clause or equivalent explicit trigger guidance — only "for tax preparation" weakly implies when. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Natural user terms are present: "invoices", "receipts", "tax preparation", "bookkeeping". Good keyword coverage but a few natural terms are missing ("expenses", "PDF", file extensions), fitting the anchor 4 rather than the comprehensive synonym-and-extension coverage of 5.	4 / 5
Distinctiveness Conflict Risk	"organizes invoices and receipts for tax preparation" carves a clear niche with only minor overlap risk against general document-organization skills. It is not a 5 because no explicit trigger phrases further sharpen the distinction from adjacent filing/bookkeeping skills.	4 / 5
	Total	15 / 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: c9856ea

Reviewed: 6 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.