> Find recurring expenses and subscriptions to cut or reduce.
npx skills add https://github.com/openaccountant/skills --skill expense-optimizer
Analyze your transaction history to identify recurring expenses, unused subscriptions, duplicate services, and optimization opportunities. Surfaces actionable savings by detecting charges you may have forgotten about or services you could downgrade.
transaction_search — detect recurring charges by pattern and frequencyanomaly_detect — flag subscriptions with price increases or irregular chargesspending_summary — identify highest-spend recurring categoriestransaction_search to find all transactions from the last 6 months.| Service | Monthly Cost | Frequency | Last Charged | Category |
|---------|-------------|-----------|--------------|----------|
anomaly_detect to flag:| Category | Description | Examples |
|----------|-------------|---------|
| Cancel | Services you likely don't use | Gym memberships with no related spending nearby, streaming services you haven't watched |
| Downgrade | Premium tiers you could reduce | Phone plan with unused data, cloud storage over 50% empty |
| Negotiate | Services with competitive alternatives | Internet, insurance, cell phone |
| Consolidate | Overlapping services | Multiple streaming, multiple cloud storage, multiple music services |
| Switch | Cheaper alternatives exist | Bank fees (switch to no-fee), high-interest debt (refinance) |
| Keep | Good value, actively used | No action needed |
To find recurring expenses manually:
SUBSCRIPTION, RECURRING, MONTHLY, ANNUAL, RENEWAL =SUMIFS(Amount, Description, "*NETFLIX*", Date, ">="&TODAY()-180) / 6
This gives the average monthly cost for Netflix over the last 6 months.
Current: =INDEX(Amount, MATCH(1, (Description="*NETFLIX*")*(Date=MAX(IF(Description="*NETFLIX*",Date))), 0))
Original: =INDEX(Amount, MATCH(1, (Description="*NETFLIX*")*(Date=MIN(IF(Description="*NETFLIX*",Date))), 0))
=MonthlyCost * 12Use when you have a written implementation plan to execute in a separate session with review checkpoints
Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take openaccountant/expense-optimizer from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.