Prompts · Python · v0.1.0
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
#anthropic#awesome-list#awesome-lists
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.
by Prat011 · updated 2mo ago · imported from GitHub
This skill transforms chaotic folders of invoices, receipts, and financial documents into a clean, tax-ready filing system without manual effort.
Reads Invoice Content: Extracts information from PDFs, images, and documents:
Renames Files Consistently: Creates standardized filenames:
YYYY-MM-DD Vendor - Invoice - ProductOrService.pdf2024-03-15 Adobe - Invoice - Creative Cloud.pdfOrganizes by Category: Sorts into logical folders:
Handles Multiple Formats: Works with:
Maintains Originals: Preserves original files while organizing copies
Navigate to your messy invoice folder:
cd ~/Desktop/receipts-to-sort
Then ask Claude Code:
Organize these invoices for taxes
Or more specifically:
Read all invoices in this folder, rename them to
"YYYY-MM-DD Vendor - Invoice - Product.pdf" format,
and organize them by vendor
Organize these invoices:
1. Extract date, vendor, and description from each file
2. Rename to standard format
3. Sort into folders by expense category (Software, Office, Travel, etc.)
4. Create a CSV spreadsheet with all invoice details for my accountant
When a user requests invoice organization:
Scan the Folder
Identify all invoice files:
# Find all invoice-related files
find . -type f \( -name "*.pdf" -o -name "*.jpg" -o -name "*.png" \) -print
Report findings:
Extract Information from Each File
For each invoice, extract:
From PDF invoices:
From image receipts:
Fallback for unclear files:
Determine Organization Strategy
Ask user preference if not specified:
I found [X] invoices from [date range].
How would you like them organized?
1. **By Vendor** (Adobe/, Amazon/, Stripe/, etc.)
2. **By Category** (Software/, Office Supplies/, Travel/, etc.)
3. **By Date** (2024/Q1/, 2024/Q2/, etc.)
4. **By Tax Category** (Deductible/, Personal/, etc.)
5. **Custom** (describe your structure)
Or I can use a default structure: Year/Category/Vendor
Create Standardized Filename
For each invoice, create a filename following this pattern:
YYYY-MM-DD Vendor - Invoice - Description.ext
Examples:
2024-03-15 Adobe - Invoice - Creative Cloud.pdf2024-01-10 Amazon - Receipt - Office Supplies.pdf2023-12-01 Stripe - Invoice - Monthly Payment Processing.pdfFilename Best Practices:
Execute Organization
Before moving files, show the plan:
# Organization Plan
## Proposed Structure
Invoices/ ├── 2023/ │ ├── Software/ │ │ ├── Adobe/ │ │ └── Microsoft/ │ ├── Services/ │ └── Office/ └── 2024/ ├── Software/ ├── Services/ └── Office/
## Sample Changes
Before: `invoice_adobe_march.pdf`
After: `2024-03-15 Adobe - Invoice - Creative Cloud.pdf`
Location: `Invoices/2024/Software/Adobe/`
Before: `IMG_2847.jpg`
After: `2024-02-10 Staples - Receipt - Office Supplies.jpg`
Location: `Invoices/2024/Office/Staples/`
Process [X] files? (yes/no)
After approval:
# Create folder structure
mkdir -p "Invoices/2024/Software/Adobe"
# Copy (don't move) to preserve originals
cp "original.pdf" "Invoices/2024/Software/Adobe/2024-03-15 Adobe - Invoice - Creative Cloud.pdf"
# Or move if user prefers
mv "original.pdf" "new/path/standardized-name.pdf"
Generate Summary Report
Create a CSV file with all invoice details:
Date,Vendor,Invoice Number,Description,Amount,Category,File Path
2024-03-15,Adobe,INV-12345,Creative Cloud,52.99,Software,Invoices/2024/Software/Adobe/2024-03-15 Adobe - Invoice - Creative Cloud.pdf
2024-03-10,Amazon,123-4567890-1234567,Office Supplies,127.45,Office,Invoices/2024/Office/Amazon/2024-03-10 Amazon - Receipt - Office Supplies.pdf
...
This CSV is useful for:
Provide Completion Summary
# Organization Complete! 📊
## Summary
- **Processed**: [X] invoices
- **Date range**: [earliest] to [latest]
- **Total amount**: $[sum] (if amounts extracted)
- **Vendors**: [Y] unique vendors
## New Structure
Invoices/ ├── 2024/ (45 files) │ ├── Software/ (23 files) │ ├── Services/ (12 files) │ └── Office/ (10 files) └── 2023/ (12 files)
## Files Created
- `/Invoices/` - Organized invoices
- `/Invoices/invoice-summary.csv` - Spreadsheet for accounting
- `/Invoices/originals/` - Original files (if copied)
## Files Needing Review
[List any files where information couldn't be extracted completely]
## Next Steps
1. Review the `invoice-summary.csv` file
2. Check files in "Needs Review" folder
3. Import CSV into your accounting software
4. Set up auto-organization for future invoices
Ready for tax season! 🎉
User: "I have a messy folder of invoices for taxes. Sort them and rename properly."
Process:
YYYY-MM-DD Vendor - Invoice - Product.pdf2024/Software/, 2024/Travel/, etc.invoice-summary.csv for accountantUser: "Organize my business receipts from last month by category."
Output:
# March 2024 Receipts Organized
## By Category
- Software & Tools: $847.32 (12 invoices)
- Office Supplies: $234.18 (8 receipts)
- Travel & Meals: $1,456.90 (15 receipts)
- Professional Services: $2,500.00 (3 invoices)
Total: $5,038.40
All receipts renamed and filed in:
`Business-Receipts/2024/03-March/[Category]/`
CSV export: `march-2024-expenses.csv`
User: "I have 3 years of random invoices. Organize them by year, then by vendor."
Output: Creates structure:
Invoices/
├── 2022/
│ ├── Adobe/
│ ├── Amazon/
│ └── ...
├── 2023/
│ ├── Adobe/
│ ├── Amazon/
│ └── ...
└── 2024/
├── Adobe/
├── Amazon/
└── ...
Each file properly renamed with date and description.
User: "I download invoices from Gmail. They're all named 'invoice.pdf', 'invoice(1).pdf', etc. Fix this mess."
Output:
Found 89 files all named "invoice*.pdf"
Reading each file to extract real information...
Renamed examples:
- invoice.pdf → 2024-03-15 Shopify - Invoice - Monthly Subscription.pdf
- invoice(1).pdf → 2024-03-14 Google - Invoice - Workspace.pdf
- invoice(2).pdf → 2024-03-10 Netlify - Invoice - Pro Plan.pdf
All files renamed and organized by vendor.
Invoices/
├── Adobe/
├── Amazon/
├── Google/
└── Microsoft/
Invoices/
├── 2023/
│ ├── Software/
│ ├── Hardware/
│ ├── Services/
│ └── Travel/
└── 2024/
└── ...
Invoices/
├── 2024/
│ ├── Q1/
│ │ ├── Software/
│ │ ├── Office/
│ │ └── Travel/
│ └── Q2/
│ └── ...
Invoices/
├── Deductible/
│ ├── Software/
│ ├── Office/
│ └── Professional-Services/
├── Partially-Deductible/
│ └── Meals-Travel/
└── Personal/
For ongoing organization:
Create a script that watches my ~/Downloads/invoices folder
and auto-organizes any new invoice files using our standard
naming and folder structure.
This creates a persistent solution that organizes invoices as they arrive.
If date/vendor can't be extracted:
If same invoice appears multiple times:
For invoices split across files:
For unusual receipt formats:
No comments yet — start the thread.
Sign in to join the discussion.
Prompts · Python · v0.1.0
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
#anthropic#awesome-list#awesome-lists
Prompts · Python · v0.1.0
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
#anthropic#awesome-list#awesome-lists
Prompts · Python · v0.1.0
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
#anthropic#awesome-list#awesome-lists
Prompts · Python · v0.1.0
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
#anthropic#awesome-list#awesome-lists