recap
Triggered by "monthly recap", "how did I do this month", "spending summary", "financial review", "weekly recap", "quarterly review", "year in review"
What this skill does
# Financial Recap
Generate a narrative financial review for any time period.
## Workflow
1. **Determine the period.** Parse `$ARGUMENTS` for the time span:
- "this week", "last week" → weekly
- "this month", "january", "jan 2025", "2025-01" → monthly (default if no argument)
- "this quarter", "Q1", "Q1 2025" → quarterly
- "this year", "2025", "year in review" → yearly
- Any explicit date range works too
2. **Fetch summary data.** Call the `query` MCP tool with `compare: "prior_period"`:
```json
{ "period": "<detected_period>", "compare": "prior_period", "include": ["ratios", "anomalies", "accounts"] }
```
(Use `start`/`end` if a specific date range was requested.)
3. **Fetch year-ago comparison.** For anything other than year-over-year, also fetch the same period from a year ago to account for seasonality:
```json
{ "start": "<same_period_last_year_start>", "end": "<same_period_last_year_end>", "include": ["ratios"] }
```
For example, if reviewing February 2026, also fetch February 2025.
4. **Fetch recurring bills.** Call the `query` MCP tool:
```json
{ "recurring": true }
```
5. **Synthesize a narrative recap** covering:
- **Headline numbers**: total income, total expenses, net cash flow, savings rate
- **vs. prior period**: changes from the immediately preceding period (last week, last month, etc.)
- **vs. same period last year**: seasonal context — note whether changes are normal for this time of year or unusual (skip this section for year-over-year recaps)
- **Anomalies**: unusual transactions or spending spikes
- **Recurring bills**: new, changed, or cancelled subscriptions/bills
- **Key ratios**: any ratios returned in the summary (e.g. expense-to-income)
- **Account balances**: current balances and changes
6. **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.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.