Extract structured data from financial documents with automatic categorization and analysis.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionfinancial-document-parserExecute the skills CLI command in your project's root directory to begin installation:
Fetches financial-document-parser from onewave-ai/claude-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate financial-document-parser. Access via /financial-document-parser in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
78
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
78
stars
Extract structured data from financial documents with automatic categorization and analysis.
Activate when the user:
Identify Document Type
Extract Core Information
For Invoices:
For Receipts:
For Bank/Credit Card Statements:
Categorize Expenses
Identify Patterns
Generate Structured Output
# Financial Document Analysis
## Document Details
- **Type**: Invoice / Receipt / Statement
- **Date**: [Date]
- **Vendor/Merchant**: [Name]
- **Document Number**: [Number]
- **Total Amount**: $X,XXX.XX
## Line Items
| Description | Quantity | Unit Price | Total |
|-------------|----------|------------|-------|
| [Item] | X | $XX.XX | $XX.XX |
## Financial Summary
- **Subtotal**: $X,XXX.XX
- **Tax**: $XXX.XX
- **Total**: $X,XXX.XX
- **Payment Method**: [Method]
## Expense Categorization
| Category | Amount | Items |
|----------|--------|-------|
| Software | $XXX | Slack, GitHub |
| Office | $XX | Supplies |
## Insights
- ✓ Tax-deductible business expenses: $X,XXX
- ⚠ Recurring charges detected: 3 subscriptions ($XXX/month)
- ℹ Foreign transaction fees: $XX
## Flagged Items
- [ ] Large expense ($X,XXX) - verify approval
- [ ] Duplicate charge detected on [date]
## Export Data (CSV Format)
```csv
Date,Vendor,Description,Category,Amount,Tax Deductible
2025-01-15,Adobe,Creative Cloud,Software,52.99,Yes
## Examples
**User**: "Extract data from this invoice PDF"
**Response**: Parse PDF → Extract vendor info, line items, totals → Categorize as business expense → Format as structured data → Generate CSV export
**User**: "Analyze my bank statement and categorize expenses"
**Response**: Extract all transactions → Categorize each (dining, software, travel) → Identify recurring charges → Calculate totals by category → Flag unusual transactions → Generate spending report
**User**: "Parse these 10 receipts and create an expense report"
**Response**: Process each receipt → Extract merchant, date, amount, items → Categorize expenses → Calculate totals → Generate consolidated report → Create CSV for expense submission
## Best Practices
- Preserve exact amounts (don't round)
- Maintain currency symbols and formats
- Note when data is unclear or illegible
- Flag suspicious or duplicate transactions
- Provide tax-relevant categorization
- Use standard expense categories
- Generate export-ready formats (CSV, JSON)
- Protect sensitive info (mask account numbers)
- Identify missing information (no date, unclear vendor)
- Calculate totals and verify against document
- Note discrepancies or calculation errors
- Include exchange rates for foreign currency
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
onewave-ai/claude-skills
onewave-ai/claude-skills
kagurananaga/official-document-writing-skill
travisjneuman/.claude
ityes22/game-design-document
sammcj/agentic-coding
financial-document-parser is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
financial-document-parser fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added financial-document-parser from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
financial-document-parser reduced setup friction for our internal harness; good balance of opinion and flexibility.
financial-document-parser fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
financial-document-parser has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: financial-document-parser is focused, and the summary matches what you get after install.
Keeps context tight: financial-document-parser is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added financial-document-parser from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for financial-document-parser matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 41