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.
68
53%
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 purposes. However, it lacks an explicit 'Use when...' clause, which is critical for Claude to know when to select this skill. The last sentence ('Turns hours of manual bookkeeping into minutes...') is marketing fluff that could be replaced with trigger guidance.
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 into minutes of automated organization') with additional trigger terms or file type mentions (e.g., '.pdf receipts', 'scanned invoices', 'expense reports').
| 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. Per rubric guidelines, missing 'Use when...' caps completeness at 2. | 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', 'organize finances', 'file sorting', or specific file types like '.pdf', '.csv'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of invoices, receipts, tax preparation, and file organization creates a clear niche. This is unlikely to conflict with generic file management or general document processing skills due to its specific financial/tax domain focus. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
39%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has a well-structured workflow with good validation checkpoints (user approval before file operations, flagging unclear files), but is severely bloated with unnecessary content. It explains concepts Claude already knows, repeats similar examples multiple times, and includes sections like 'Pro Tips' and 'Related Use Cases' that add little actionable value. The core extraction mechanism—the hardest part of the task—is left vague without specifying actual tools or libraries.
Suggestions
Cut the content by at least 60%: remove 'When to Use', 'Pro Tips', 'Related Use Cases', and reduce examples to 1-2. Move 'Common Organization Patterns' and 'Handling Special Cases' to separate reference files.
Specify actual tools for PDF text extraction and image OCR (e.g., pdfplumber, pytesseract) with executable code snippets instead of vague 'use text extraction' instructions.
Split into SKILL.md (overview + core workflow) and supporting files like PATTERNS.md (organization patterns), EXAMPLES.md (detailed examples), and SPECIAL-CASES.md.
Remove explanations of what CSV files are useful for, what file formats exist, and other concepts Claude already understands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. Extensively explains things Claude already knows (what invoice fields are, what CSV is useful for, what file formats exist, basic bash commands like mkdir and cp). The 'When to Use This Skill', 'Pro Tips', 'Related Use Cases', and 'Common Organization Patterns' sections are largely unnecessary padding. Multiple examples repeat the same concept. | 1 / 3 |
Actionability | Provides concrete bash commands and CSV format examples, but the core extraction step is vague—it says 'use text extraction to read invoice content' and 'read visible text from images' without specifying actual tools or executable code. The skill describes a process more than it provides executable implementation. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with explicit validation: it scans first, shows a plan for user approval before executing, preserves originals by default (cp not mv), flags unclear files for manual review, and provides a completion summary with items needing review. The approval checkpoint before file operations is a good feedback loop. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no bundle files or external references. Content that could be split into separate files (common organization patterns, special cases, examples, automation setup) is all inline, making the skill extremely long. No references to supporting documents. | 1 / 3 |
Total | 7 / 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
74c7031
- 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.