Calculate crypto gains and income from exchange transaction CSVs, compare FIFO, LIFO, and HIFO cost basis methods, identify taxable events, and export Form 8949 compatible reports. The results are informational calculations, not tax advice.
Calculate cryptocurrency tax obligations with cost basis tracking, capital gains computation, and Form 8949 generation. Use when calculating crypto taxes, generating tax reports, comparing cost basis methods, or identifying taxable events. Trigger with phrases like "calculate crypto taxes", "generate tax report", "cost basis FIFO", "capital gains", "Form 8949", or "crypto taxable events".
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Calculate cryptocurrency tax obligations from transaction history. Supports FIFO, LIFO, and HIFO cost basis methods, identifies taxable events (trades, staking, airdrops), and generates Form 8949 compatible reports.
DISCLAIMER: This tool provides informational calculations only, not tax advice. Consult a qualified tax professional.
Prepare transaction data by exporting CSV from each exchange:
| Exchange | Export Location |
|---|---|
| Coinbase | Reports > Tax documents > Transaction history CSV |
| Binance | Orders > Trade History > Export |
| Kraken | History > Export |
| Generic | See references/exchange_formats.md for column mapping |
Run basic tax calculation using FIFO (IRS default):
python ${CLAUDE_SKILL_DIR}/scripts/tax_calculator.py --transactions your_trades.csv --year 2025 # 2025 = tax year
Compare cost basis methods to understand tax implications:
python ${CLAUDE_SKILL_DIR}/scripts/tax_calculator.py --transactions trades.csv --compare-methods
Methods: --method fifo (IRS default), --method lifo (Last In First Out), --method hifo (minimize gains)
Generate Form 8949 report as CSV:
python ${CLAUDE_SKILL_DIR}/scripts/tax_calculator.py --transactions trades.csv --method fifo --year 2025 --output form_8949.csv --format csv # 2025 = tax year
Handle income events (staking, airdrops, mining, DeFi yield):
python ${CLAUDE_SKILL_DIR}/scripts/tax_calculator.py --transactions all_events.csv --income-report
Consolidate multi-exchange data into a unified report:
python ${CLAUDE_SKILL_DIR}/scripts/tax_calculator.py --transactions coinbase.csv binance.csv kraken.csv --year 2025 # 2025 = tax year
Reports include short-term and long-term capital gains/losses broken down by transaction, with proceeds, cost basis, and gain/loss per disposal. Summary shows total proceeds, total cost basis, net capital gain, and short/long-term split. Income report lists staking, airdrop, and mining income with fair market values.
See references/implementation.md for detailed output format examples.
| Error | Cause | Fix |
|---|---|---|
| Missing columns | CSV format mismatch | Verify format matches exchange template |
| Unknown transaction type | Unrecognized event category | Review and manually categorize |
| Insufficient lots | Missing buy transactions | Check for missing imports or transfers |
Basic FIFO tax calculation - Standard IRS-default method for a single exchange:
python tax_calculator.py --transactions trades.csv --year 2025 # 2025 = tax year
HIFO to minimize gains - Highest-cost lots disposed first to reduce taxable gain:
python tax_calculator.py --transactions trades.csv --method hifo --year 2025 # 2025 = tax year
JSON output for processing - Machine-readable export for tax software integration:
python tax_calculator.py --transactions trades.csv --format json --output tax_data.json
Verbose with lot details - See which specific lots were matched to each disposal:
python tax_calculator.py --transactions trades.csv --verbose --show-lots
references/implementation.md - Detailed output formats, configuration, advanced usageNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a synthetic-data CI gate for customer-owned Abridge integration code. Test consent handling, note-review handoffs, redaction, and rollback behavior with mocked vendor boundaries, without connecting CI to a live Abridge or EHR tenant.
Triage Abridge recording, note review, Epic handoff, and access problems using observed symptoms and approved guidance. Identify the affected workflow stage, organize a minimal timeline, and prepare a redacted escalation record for the responsible team.
Map and review an Abridge clinical documentation workflow from consent and recording through draft review, evidence checks, edits, and final disposition. Keep clinician approval explicit, identify failure exits, and separate verified facts from tenant-specific details and pending approvals.
Audit how clinician-reviewed Abridge note sections map into Epic templates and downstream workflows. Use approved test records to document destinations, exceptions, evidence, rollback steps, and a go or no-go decision for a specific environment.
Review Abridge adoption and workflow value using local usage records, clinician feedback, and verified contract costs. Build an evidence based decision table covering adoption, quality, support burden, and options to expand, hold, or improve the rollout.
Prepare a bounded support bundle for an Abridge issue using allowlisted operational details such as versions, coarse timestamps, and correlation references. Exclude recordings, transcripts, patient identifiers, credentials, and unrestricted logs, then document redactions and review details.