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.
53
Quality
47%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./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 effectively communicates specific capabilities for organizing financial documents with concrete actions. However, it lacks an explicit 'Use when...' clause which limits Claude's ability to know exactly when to select this skill. The marketing-style closing sentence ('Turns hours of manual bookkeeping into minutes') adds fluff without improving skill selection.
Suggestions
Add an explicit 'Use when...' clause with trigger terms like 'organize receipts', 'tax documents', 'expense files', 'sort invoices'
Replace the marketing sentence with additional trigger terms or file type mentions (e.g., 'scanned receipts', '.pdf 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 context (tax preparation, bookkeeping). | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'invoices', 'receipts', 'tax preparation', 'bookkeeping', but missing common variations users might say like 'expense tracking', 'financial documents', 'tax documents', or file extensions like '.pdf'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on invoices/receipts for tax preparation with distinct file organization workflow. Unlikely to conflict with general document or PDF skills due to the specific financial/tax context. | 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 well-intentioned but severely bloated, explaining concepts Claude already knows and repeating similar examples multiple times. While the workflow structure is reasonable, it lacks executable code for core operations (PDF/image text extraction) and validation checkpoints for data accuracy. The content would be more effective at 25% of its current length with actual implementation code.
Suggestions
Reduce content by 75%: Remove 'When to Use', 'What This Skill Does', and redundant examples. Claude doesn't need explanations of what invoices are or why organization helps.
Add executable code for PDF text extraction (e.g., pdfplumber) and image OCR instead of describing what patterns to look for.
Split into multiple files: Move organization patterns to PATTERNS.md, examples to EXAMPLES.md, and special cases to EDGE-CASES.md with clear references.
Add validation checkpoint after extraction: verify extracted data with user before proceeding to rename/move operations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~400 lines. Explains obvious concepts Claude knows (what invoices are, common file formats, basic bash commands). The 'When to Use This Skill' and 'What This Skill Does' sections are redundant with the actual instructions. Multiple examples repeat the same patterns unnecessarily. | 1 / 3 |
Actionability | Provides some concrete bash commands and filename patterns, but lacks executable code for the core task (PDF text extraction, image OCR). The 'Extract Information from Each File' section describes what to look for but doesn't provide actual implementation code for reading PDFs or images. | 2 / 3 |
Workflow Clarity | Steps are clearly numbered and sequenced with a confirmation checkpoint before file operations. However, lacks validation steps for verifying extracted data accuracy, no error recovery for failed extractions, and no verification that renamed files are correct before proceeding. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Content that could be split (organization patterns, examples, special cases, pro tips) is all inline. The skill would benefit from separating examples, patterns, and edge cases into referenced files. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- Repository
- ComposioHQ/awesome-claude-skills
- Commit
362d354
- 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.