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

35%

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

The skill body is well-sectioned and gives concrete shell commands plus an approval checkpoint, but it suffers from heavy repetition, lacks executable extraction code, and provides no post-execution validation for a batch operation. It would benefit substantially from trimming redundancy and adding a verification step.

Suggestions

Consolidate the repeated folder-tree structures and filename-format definitions into a single canonical section; remove the near-duplicate trees in "Examples" and "Common Organization Patterns."

Replace the descriptive extraction steps with executable guidance, e.g. a `pdftotext`/`pdfplumber` command or an OCR invocation, so the core task is copy-paste ready.

Add a post-execution verification step (confirm file counts match the plan, re-run on failures) to turn the approval gate into a true validate→fix→retry feedback loop.

Dimension	Reasoning	Score
Conciseness	The ~440-line body is heavily padded: identical folder-tree structures and the filename format are restated across "Instructions," "Examples," and "Common Organization Patterns," and it explains extraction concepts Claude already knows, well beyond "some" unnecessary content.	1 / 3
Actionability	Provides concrete, executable shell commands (find, mkdir, cp) and a defined CSV schema, but the core extraction step lacks executable code — "Use text extraction" and "Read visible text from images" are descriptive with no library or OCR command.	2 / 3
Workflow Clarity	The 7-step sequence is clear with a pre-execution approval gate, but this batch file operation has no post-execution validation or validate→fix→retry feedback loop, capping workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	The single 440-line SKILL.md is monolithic with no bundle files or external references, and content that could be split out (example trees, common patterns) is inline; section headers provide some structure but no file-level disclosure.	2 / 3
	Total	7 / 12 Passed

Description

82%

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, distinctive, and uses natural trigger terms, but omits an explicit "when to use" clause, leaving the triggering context implied rather than stated. Adding a "Use when..." sentence would lift completeness to a top score.

Suggestions

Add an explicit trigger clause such as "Use when preparing for tax season, organizing receipts, or filing business expenses" to satisfy the completeness "when" requirement.

Consider including common natural variants like "expense reports" or "receipts" near the trigger clause to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Enumerates multiple concrete actions — "reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders" — rather than vague domain-level claims.	3 / 3
Completeness	Clearly states what the skill does but lacks an explicit "Use when..." trigger clause; the "when" is only implied by the tax-preparation context, capping completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Uses natural terms a user would actually say — "invoices and receipts," "tax preparation," "bookkeeping" — giving good coverage rather than technical jargon.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche (invoice/receipt organization for taxes) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: b79ed72

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