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.
64
47%
Does it follow best practices?
Impact
94%
1.23xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/invoice-organizer/SKILL.mdQuality
Discovery
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 does a good job of listing specific concrete actions and carving out a distinct niche around invoice/receipt organization for tax preparation. However, it lacks an explicit 'Use when...' clause, which limits Claude's ability to reliably select this skill. The last sentence ('Turns hours of manual bookkeeping into minutes of automated organization') is marketing fluff that adds no selection value.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to organize invoices, receipts, expense documents, or prepare files for tax filing.'
Replace the marketing sentence ('Turns hours of manual bookkeeping...') with additional trigger terms like 'expense reports', 'tax documents', '.pdf receipts', or 'categorize expenses'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied through the domain context of tax preparation and bookkeeping. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'invoices', 'receipts', 'tax preparation', 'bookkeeping', 'renaming', and 'folders', but misses common variations users might say such as 'expense reports', 'tax documents', 'file organization', '.pdf', '.csv', or 'categorize expenses'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of invoices/receipts, tax preparation, file renaming, and folder sorting creates a clear niche that is unlikely to conflict with generic file organization or document processing skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is excessively verbose, spending many tokens on descriptions of what invoices are, lists of use cases, and general bookkeeping advice that Claude doesn't need. The most critical technical challenge—actually extracting text from PDFs and images—is left vague with no executable code. While the workflow sequence is reasonable and includes a user confirmation step, the overall document would benefit enormously from being cut to ~25% of its current size and adding actual extraction code.
Suggestions
Cut the content by 60-70%: remove 'When to Use', 'What This Skill Does', 'Pro Tips', 'Related Use Cases', and most of 'Common Organization Patterns'—these describe rather than instruct.
Add executable code for the core extraction task: provide actual Python code using pdfplumber or similar for PDF text extraction, and describe how Claude should use its vision capabilities for image receipts.
Split detailed examples, organization patterns, and special cases into separate referenced files (e.g., PATTERNS.md, EXAMPLES.md) to improve progressive disclosure.
Add a post-organization validation step: verify file counts match expectations, confirm CSV row count equals processed files, and check for any failed copy operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Explains obvious concepts Claude already knows (what invoice fields are, what CSV is useful for, what PDF/JPG formats are). Extensive 'When to Use' and 'What This Skill Does' sections describe rather than instruct. Pro tips like 'Keep receipts 7 years' and 'Scan emails to PDF' are general advice, not actionable skill content. The emoji-laden completion summary template and multiple organization pattern examples add significant bloat. | 1 / 3 |
Actionability | Provides some concrete guidance like the find command, mkdir/cp/mv commands, CSV format, and filename patterns. However, the core task—extracting information from PDFs and images—lacks any executable code. 'Use text extraction to read invoice content' and 'Read visible text from images' are vague hand-waves over the hardest part of the skill. No actual PDF parsing library usage or image OCR code is provided. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced and includes a user approval checkpoint before executing file operations (step 5). However, there's no validation step after the organization is complete (e.g., verifying file counts match, checking for failed copies, validating the CSV). The feedback loop for error recovery is minimal—'flag for manual review' is mentioned but no concrete retry/fix mechanism exists. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Everything is inline in one massive document—the common organization patterns, special cases, automation setup, pro tips, and multiple examples could all be split into separate reference files. No bundle files exist to support progressive disclosure, and the content doesn't attempt any structural separation. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
d065ead
- Reviewed
Table of Contents
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.