Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
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:
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Automate ActiveCampaign tasks via Rube MCP (Composio): manage contacts, tags, list subscriptions, automation enrollment, and tasks. Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Pull the ads a competitor is running right now on Meta (Facebook/Instagram) and Google, then extract the hooks, offers, CTAs and landing pages worth modelling. Use when writing ad copy, planning creative tests, choosing a landing page angle, or when the user asks "what is X advertising", "what ads does X run", "find competitor ad hooks". Reads live Ad Library and Ads Transparency data through the Tracetify MCP; falls back to a manual Ad Library walkthrough when the connector is absent.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analytics your AI agent can actually use. Track, analyze, run A/B experiments, and optimize across all your projects via CLI. Includes a growth playbook so your agent knows HOW to grow, not just what to track.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Teaches when to recall from long-term memory before acting and when to save durable decisions, corrections and failures afterwards. Use when a memory tool or MCP memory server is connected but the agent is not using it consistently, when the user complains that the assistant forgets preferences, conventions or past decisions between sessions, or when setting up persistent memory for a project. Works with any memory backend: a folder of Markdown files, a local MCP server, or a managed service.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit local AI coding-agent sessions with agenttrace for cost, tokens, tool failures, latency, anomalies, health, diffs, and CI gates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Checks which private files (.env, keys, secrets) Claude Code and its subagents reached in this project, whether a value came into an agent's context, and which key to change, by running the open source agentwhy CLI over the session records Claude Code already keeps on disk. Use when the user asks whether the agent or a subagent read their .env or other secrets, which private files a session touched, whether a key leaked into the conversation, or which key to rotate. Runs locally and never prints a secret value.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.