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 ./.trae/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 general file organization or generic 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 extremely verbose and padded with information Claude already knows, explanatory fluff, and marketing-style language. While the workflow sequence is reasonable and the naming convention is clear, the skill lacks executable code for its core function (extracting data from invoices) and dumps everything into a single monolithic file. It reads more like a product feature description than an actionable skill for Claude.
Suggestions
Cut content by at least 60%: remove 'When to Use', 'Related Use Cases', 'Pro Tips', emoji, and explanations of what CSVs are useful for. Focus on the extraction and organization workflow only.
Add executable code for the core extraction task—specify a tool/library (e.g., pdfplumber, pdftotext) with actual working code to extract vendor, date, and amount from PDFs.
Split into multiple files: keep SKILL.md as a concise overview with the core workflow, and move organization patterns, special cases, and examples into separate referenced files.
Add a post-execution validation step: verify file counts match, confirm no files were lost, and check that the CSV row count matches processed files.
| 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 file formats exist). The 'When to Use This Skill' section, 'Pro Tips', 'Related Use Cases', and extensive examples are padding. The emoji-laden completion summary template is unnecessary fluff. Much of this could be condensed to under 80 lines. | 1 / 3 |
Actionability | Provides some concrete bash commands (find, mkdir, cp, mv) and a clear naming convention, but lacks executable code for the core task—actually extracting text from PDFs/images. The extraction step says 'use text extraction to read invoice content' without specifying tools or code. The skill describes what to do more than showing how to do it programmatically. | 2 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced and includes a confirmation step before executing file operations (step 5), which is good. However, there's no validation/verification step after the batch file operations—no check that files were copied correctly, no hash verification, no count confirmation. For a batch file operation that could be destructive, this gaps caps the score at 2. | 2 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. Everything is inline—common patterns, special cases, automation setup, pro tips, examples—all crammed into one massive document. Content like 'Common Organization Patterns', 'Handling Special Cases', and multiple detailed examples should be split into separate reference files. | 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
- Lingjie-chen/MT5
- Commit
3069d33
- 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.