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

72%

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

77%

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

The content is highly actionable with a well-sequenced, checkpointed workflow and concrete commands, but it is monolithic and verbose — redundant examples and ancillary sections inflate the body without external reference files. Splitting examples and patterns into reference files would improve both conciseness and progressive disclosure.

Suggestions

Move the four worked Examples and the Common Organization Patterns into a separate references file (e.g. EXAMPLES.md) linked from the body to reduce the main SKILL.md footprint.

Trim or remove the Pro Tips, Related Use Cases, and Automation Setup sections, which mostly restate guidance already covered in the Instructions.

Consolidate the repeated folder-tree diagrams into a single canonical structure illustration to cut redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable but padded with redundant material — four full worked examples, repeated folder-tree diagrams, a Pro Tips list, and Related Use Cases — that could be trimmed; not level 1 because it avoids explaining basic concepts Claude already knows, and not level 3 because the redundancy means not every token earns its place.	2 / 3
Actionability	Provides executable commands (`find`, `mkdir -p`, `cp`, `mv`), a concrete filename pattern (`YYYY-MM-DD Vendor - Invoice - Description.ext`), and a copy-paste CSV schema with sample rows; fully actionable and specific, matching the highest anchor.	3 / 3
Workflow Clarity	A clear 7-step sequence includes an explicit approval checkpoint ('Process [X] files? (yes/no)') before file moves and fallback/flag-for-review handling, satisfying the validation-checkpoint requirement for batch file operations; not level 2 because checkpoints are explicit rather than implicit.	3 / 3
Progressive Disclosure	No bundle files exist and the skill is a monolithic ~440-line document with content (four examples, common patterns, pro tips) that could live in separate reference files; section structure is present, so not level 1, but it is not level 3 because nothing is split out with one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 third-person with a clear niche, but it omits an explicit 'Use when' trigger clause and leans on marketing-style phrasing instead of comprehensive natural keywords. Adding explicit trigger guidance and trimming the benefit claim would raise completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause listing natural triggers such as 'Use when organizing invoices or receipts, preparing taxes, or sorting expense files.'

Replace the marketing line 'Turns hours of manual bookkeeping into minutes of automated organization' with concrete trigger keywords like 'expenses', 'taxes', and 'receipts'.

Cover common user phrasings ('expense reports', 'reimbursement receipts', 'filing receipts') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions in third person ('reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders'), matching the multi-action anchor; not the level below which only names a domain and some actions.	3 / 3
Completeness	Clearly states what the skill does but lacks an explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 2; not level 1 because the 'what' is strong.	2 / 3
Trigger Term Quality	Includes some natural terms ('invoices and receipts', 'tax preparation', 'bookkeeping') but pads with marketing fluff ('Turns hours of manual bookkeeping into minutes of automated organization') and misses common variations like 'expenses' and 'taxes'; not level 3 which requires good coverage of natural phrasings.	2 / 3
Distinctiveness Conflict Risk	The invoice/receipt-for-tax-preparation niche is clearly distinct with specific triggers unlikely to fire for unrelated skills; not level 2 because it is not merely 'somewhat specific' — it has a clear dedicated niche.	3 / 3
	Total	10 / 12 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: Prat011/awesome-llm-skills
Path: invoice-organizer/SKILL.md
Commit: 35e1ea2

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