Parse and deduplicate bank CSV files into the OptimalOS transactions table.
npx skills add https://github.com/clenisa/optimal-cli --skill ingest-transactions
Please help me install this Agent Skill. Skill: ingest-transactions Source: https://github.com/clenisa/optimal-cli/tree/main/skills/ingest-transactions Command: npx skills add https://github.com/clenisa/optimal-cli --skill ingest-transactions
This Skill automates the tedious process of parsing varied bank-export CSV formats, normalizing transaction data, and preventing duplicate inserts into the OptimalOS transactions table so financial imports are accurate and auditable.
Run ingest-transactions with the CSV file path and the Supabase user UUID to import transactions into OptimalOS.
High-intent search queries and answers about installing and using this skill.
To import bank CSV files into Supabase without duplicates, parse the data, normalize dates and amounts, and compute a SHA-256 dedup hash for each transaction. The Skill skips existing transactions and batch-inserts new records into the OptimalOS transactions table.
The best way to normalize Chase Checking or Discover CSV exports is to auto-detect the file headers and apply format-specific parsing rules. This standardizes transaction dates, amounts, and descriptions for accurate database insertion.
Yes, you can use a generic CSV export format to import transactions into OptimalOS. The process auto-detects generic CSV headers alongside Chase and Discover formats, applying the appropriate parsing rules to normalize and insert the transactional data.
Yes, you need the OPTIMAL_SUPABASE_URL and OPTIMAL_SUPABASE_SERVICE_KEY environment variables configured. These Supabase credentials are required to access the database, resolve categories, and batch-insert transactional records securely.
SHA-256 deduplication works by computing a unique hash for each normalized transaction row during the CSV import. If a transaction with the same hash already exists in the Supabase transactions table, the insertion is skipped to prevent duplicate records.
A key limitation is that parsing varied bank-export CSV formats requires format-specific rules for Chase Checking, Chase Credit, Discover, or generic exports. Unsupported custom bank formats may not parse correctly without header auto-detection and manual normalization adjustments.
ictcentervnMigrate local Padlet-style app storage to Supabase cloud database.
arunrlvermaLog expense transactions and generate monthly category summaries from JSONL data.
payrocQuery and retrieve authorization records from the Payroc Reporting API.
PaneriVatsalExtract transactions from bank statement PDFs and analyze spending with pandas.
