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.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill invoice-organizer60
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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', 'financial paperwork'
Include common file type variations users might mention: '.pdf invoices', 'scanned receipts', 'expense reports'
Remove the marketing fluff sentence and replace with actionable trigger guidance
| 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', 'tax documents', 'financial records', or file extensions like '.pdf'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche focused specifically on invoices/receipts for tax preparation with distinct domain (financial documents, bookkeeping). Unlikely to conflict with general file organization or document processing skills. | 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 excellent workflow structure with clear steps and validation checkpoints, but is severely bloated with unnecessary content. It explains concepts Claude already knows, repeats similar examples multiple times, and includes inline content that should be in separate reference files. The core actionability is weakened by describing extraction approaches rather than providing executable code.
Suggestions
Cut 'When to Use This Skill' and 'What This Skill Does' sections entirely - these are obvious from context and waste tokens
Add executable Python code for PDF text extraction (e.g., using pdfplumber) and image text extraction instead of describing what to look for
Move 'Common Organization Patterns', 'Handling Special Cases', and 'Pro Tips' to separate reference files (PATTERNS.md, EDGE-CASES.md) with brief links from main skill
Reduce examples from 4 to 1-2, as they all demonstrate the same core pattern
| 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 | Clear 7-step workflow with explicit validation checkpoint (showing plan before execution, requiring user approval). Includes feedback loops for unclear files ('Flag for manual review') and handles edge cases systematically. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Content that should be separate (common organization patterns, automation setup, handling special cases) is all inline. The skill would benefit from splitting examples, patterns, and edge cases into separate reference files. | 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 | |
- 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.