Turn financial data for a chosen period into a plain-language review of income, expenses, savings, and balances. Compare previous periods, highlight unusual transactions, and summarize changes in recurring bills without judging spending choices.
Triggered by "monthly recap", "how did I do this month", "spending summary", "financial review", "weekly recap", "quarterly review", "year in review"
Review the instructions the agent will receive before you install.
Generate a narrative financial review for any time period.
Determine the period. Parse $ARGUMENTS for the time span:
Fetch summary data. Call the query MCP tool with compare: "prior_period":
{ "period": "<detected_period>", "compare": "prior_period", "include": ["ratios", "anomalies", "accounts"] }
(Use start/end if a specific date range was requested.)
Fetch year-ago comparison. For anything other than year-over-year, also fetch the same period from a year ago to account for seasonality:
{ "start": "<same_period_last_year_start>", "end": "<same_period_last_year_end>", "include": ["ratios"] }
For example, if reviewing February 2026, also fetch February 2025.
Fetch recurring bills. Call the query MCP tool:
{ "recurring": true }
Synthesize a narrative recap covering:
Tone: Stick to the facts. Report what happened without judgement — no "great job" or "you need to cut back." Just clear, plain-language observations. Skip categories with trivial amounts.
No 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.
Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.
Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.
Add website or app tracking, then use command-line tools to review traffic, signups, drop-off, and returning users across projects. Run A/B tests, which compare alternative headlines or buttons, and inspect results to guide changes.
Establish rules for when an AI agent should recall past context and save lasting decisions, corrections, preferences, and failures. Works with Markdown files or memory services, preserving decision history and surfacing conflicting records.
Audit local AI coding-agent sessions with agenttrace to identify spending, token use, tool failures, and operational problems. Produce readable or structured reports and define pass-or-fail thresholds for automated continuous integration checks.
Audit saved agent sessions for access to private files and evidence that secret values entered an agent's context. Get findings without displaying secrets, identify keys needing rotation, and inspect Claude Code or Codex sessions in a local report.