aigroup-workflow 1.0.0

package/skills/jarvis/engineering-team/eval-workspace/iteration-1/product-manager-toolkit/with_skill/outputs/response.md

@@ -0,0 +1,148 @@
+# Automated Invoice Processing — MVP User Stories
+
+## Epic: Invoice Processing Automation
+
+**Epic Goal:** Enable users to upload PDF invoices, extract key fields automatically, and export structured data to accounting software.
+
+**Primary Persona:** Accounts Payable Clerk — processes 50-200 invoices/month, needs speed and accuracy, uses QuickBooks/Xero/NetSuite.
+
+---
+
+### US-001: Upload PDF Invoices
+
+**Priority:** Critical | **Points:** 5
+
+```
+As an Accounts Payable Clerk,
+I want to upload one or more PDF invoices,
+So that I can begin automated data extraction without manual data entry.
+```
+
+**Acceptance Criteria:**
+
+1. **Given** the user is on the invoice processing dashboard, **When** they click "Upload Invoices," **Then** a file picker opens accepting `.pdf` files only.
+
+2. **Given** the user selects up to 20 PDF files (max 10MB each), **When** they confirm the upload, **Then** all files upload with a progress indicator and each appears in the processing queue within 5 seconds.
+
+3. **Given** the user drags PDF files onto the upload zone, **When** they drop the files, **Then** the system accepts them identically to the file picker flow.
+
+4. **Given** the user uploads a non-PDF file (e.g., .jpg, .docx), **When** the upload is attempted, **Then** the system rejects it with the message "Only PDF files are supported" and does not add it to the queue.
+
+5. **Given** the user uploads a PDF exceeding 10MB, **When** the upload is attempted, **Then** the system rejects it with the message "File exceeds 10MB limit" and suggests compressing the file.
+
+6. **Given** a network interruption during upload, **When** connectivity resumes, **Then** the system retries the failed upload automatically or surfaces a "Retry" button.
+
+---
+
+### US-002: Extract Key Invoice Fields
+
+**Priority:** Critical | **Points:** 8
+
+```
+As an Accounts Payable Clerk,
+I want the system to automatically extract vendor name, invoice number, date, due date, total amount, tax, and line items from uploaded invoices,
+So that I can eliminate manual data entry and reduce errors.
+```
+
+**Acceptance Criteria:**
+
+1. **Given** a PDF invoice is uploaded and queued, **When** extraction completes, **Then** the system populates: vendor name, invoice number, invoice date, due date, subtotal, tax amount, total amount, and currency — each with a confidence score (0-100%).
+
+2. **Given** the invoice contains line items, **When** extraction completes, **Then** each line item includes: description, quantity, unit price, and line total.
+
+3. **Given** extraction completes, **When** any field has a confidence score below 80%, **Then** that field is highlighted in amber and flagged "Needs Review."
+
+4. **Given** extraction completes, **When** the user views the results, **Then** the original PDF is displayed side-by-side with extracted fields for visual verification.
+
+5. **Given** a scanned (image-based) PDF is uploaded, **When** extraction runs, **Then** the system applies OCR and extracts fields with the same structure as text-based PDFs.
+
+6. **Given** a corrupted or password-protected PDF is uploaded, **When** extraction is attempted, **Then** the system marks it as "Extraction Failed" with a reason and prompts the user to re-upload.
+
+7. **Given** a batch of 20 invoices, **When** extraction runs, **Then** all invoices complete processing within 60 seconds total.
+
+---
+
+### US-003: Review and Correct Extracted Data
+
+**Priority:** High | **Points:** 5
+
+```
+As an Accounts Payable Clerk,
+I want to review extracted invoice data and correct any errors before exporting,
+So that I can ensure data accuracy without re-entering the entire invoice.
+```
+
+**Acceptance Criteria:**
+
+1. **Given** extraction is complete, **When** the user opens the review screen, **Then** all extracted fields are displayed in editable form fields alongside the source PDF.
+
+2. **Given** a field is flagged "Needs Review," **When** the user clicks on it, **Then** the corresponding region on the PDF is highlighted so the user can verify the source.
+
+3. **Given** the user edits a field value, **When** they save changes, **Then** the system persists the correction, removes the "Needs Review" flag, and sets confidence to 100%.
+
+4. **Given** the user has reviewed all flagged fields, **When** no "Needs Review" flags remain, **Then** the invoice status changes to "Verified" and the "Export" action becomes enabled.
+
+5. **Given** the user wants to skip review, **When** all fields have confidence ≥95%, **Then** the invoice is auto-marked "Verified" and available for immediate export.
+
+6. **Given** the user modifies line items (add, edit, or delete a row), **When** they save, **Then** the subtotal and total recalculate automatically.
+
+---
+
+### US-004: Export Invoices to Accounting Software
+
+**Priority:** High | **Points:** 5
+
+```
+As an Accounts Payable Clerk,
+I want to export verified invoice data to my accounting software (QuickBooks, Xero, or NetSuite),
+So that I can complete the AP workflow without switching between systems.
+```
+
+**Acceptance Criteria:**
+
+1. **Given** the user has connected their accounting platform via OAuth in settings, **When** they click "Export" on a verified invoice, **Then** the invoice data is pushed to the connected platform and the status updates to "Exported."
+
+2. **Given** the user selects multiple verified invoices, **When** they click "Export Selected," **Then** all selected invoices are exported in a single batch and each status updates to "Exported."
+
+3. **Given** the accounting platform returns a validation error (e.g., unknown vendor), **When** the export fails, **Then** the system displays the specific error, sets status to "Export Failed," and allows the user to correct and retry.
+
+4. **Given** no accounting integration is connected, **When** the user clicks "Export," **Then** the system offers CSV download as a fallback with columns matching the standard import format of QuickBooks, Xero, and NetSuite.
+
+5. **Given** an invoice was previously exported, **When** the user attempts to export it again, **Then** the system warns "This invoice was already exported on [date]. Export again?" requiring confirmation to prevent duplicates.
+
+---
+
+### US-005: View Invoice Processing History
+
+**Priority:** Medium | **Points:** 3
+
+```
+As an Accounts Payable Clerk,
+I want to view a searchable history of all processed invoices,
+So that I can track processing status, find past invoices, and audit the AP pipeline.
+```
+
+**Acceptance Criteria:**
+
+1. **Given** the user navigates to "Invoice History," **When** the page loads, **Then** a table displays all invoices sorted by upload date (newest first) with columns: vendor, invoice number, date, amount, status (Queued / Extracted / Verified / Exported / Failed).
+
+2. **Given** the user types in the search bar, **When** they enter a vendor name, invoice number, or amount, **Then** results filter in real-time (within 300ms) across all fields.
+
+3. **Given** the user clicks a filter chip for status (e.g., "Needs Review"), **When** applied, **Then** only invoices matching that status are displayed and the count updates.
+
+4. **Given** the user clicks on an invoice row, **When** the detail view opens, **Then** it shows the full extracted data, the original PDF, edit history, and export timestamps.
+
+---
+
+## MVP Summary
+
+| ID | Story | Points | Priority |
+|----|-------|--------|----------|
+| US-001 | Upload PDF Invoices | 5 | Critical |
+| US-002 | Extract Key Invoice Fields | 8 | Critical |
+| US-003 | Review and Correct Extracted Data | 5 | High |
+| US-004 | Export to Accounting Software | 5 | High |
+| US-005 | View Invoice Processing History | 3 | Medium |
+| | **Total** | **26** | |
+
+**Sprint fit:** At ~28-point velocity, this MVP is achievable in a single sprint with the extraction engine (US-002) as the critical-path item. If capacity is tighter, US-005 can defer to sprint 2 as a stretch goal.

package/skills/jarvis/engineering-team/eval-workspace/iteration-1/seo-audit/with_skill/outputs/response.md

@@ -0,0 +1,178 @@
+# SEO Audit: B2B SaaS Project Management Tool
+
+## Executive Summary
+
+A 2-year-old domain with 150 pages struggling for "project management software" likely faces a combination of **domain authority gap**, **content depth issues**, and **missing topical coverage**. "Project management software" is extremely competitive (Asana, Monday, ClickUp, Wrike dominate), so the strategy must combine technical excellence with smart content positioning.
+
+**Top 5 Priority Issues (Likely)**
+1. Competing head-on for ultra-competitive terms without sufficient authority
+2. Missing mid-funnel and long-tail content that builds topical authority
+3. Thin product/feature pages that don't satisfy search intent
+4. Weak internal linking and topical clustering
+5. Missing structured data (SoftwareApplication, FAQ, Review schemas)
+
+---
+
+## Prioritized Audit Checklist
+
+### Phase 1: Critical Fixes (Week 1-2) — Blocking Issues
+
+| # | Action | Impact | Effort |
+|---|--------|--------|--------|
+| 1 | **Run `site:yourdomain.com`** — compare indexed count vs. expected 150 pages. Flag gaps. | High | 15 min |
+| 2 | **Check robots.txt** — verify no accidental blocks on /features/, /pricing/, /blog/ | High | 10 min |
+| 3 | **Validate XML sitemap** — must exist, be submitted to Search Console, contain only canonical 200-status URLs | High | 30 min |
+| 4 | **Audit canonical tags** — every page needs a self-referencing canonical. Check for wrong cross-page canonicals | High | 1 hr |
+| 5 | **Fix redirect chains** — no page should require >1 redirect hop to resolve | High | 1 hr |
+| 6 | **Check for soft 404s** — pages returning 200 but showing error content | Medium | 30 min |
+| 7 | **HTTPS audit** — no mixed content, all HTTP URLs 301 to HTTPS | High | 30 min |
+
+**Tools:** Google Search Console Coverage report, Screaming Frog crawl, manual checks.
+
+---
+
+### Phase 2: Technical Foundations (Week 2-3)
+
+| # | Action | Impact | Effort |
+|---|--------|--------|--------|
+| 8 | **Core Web Vitals** — target LCP < 2.5s, INP < 200ms, CLS < 0.1. Run PageSpeed Insights on homepage, pricing, top 5 blog posts | High | 2-4 hrs |
+| 9 | **Image optimization** — convert to WebP, add descriptive alt text, implement lazy loading | Medium | 2 hrs |
+| 10 | **Mobile audit** — check tap targets, no horizontal scroll, same content parity as desktop | High | 1 hr |
+| 11 | **URL structure review** — ensure `/features/gantt-charts/` not `/page?id=123`. Readable, keyword-bearing, lowercase, hyphenated | Medium | 1 hr |
+| 12 | **Server response time** — TTFB under 200ms. Check CDN, caching headers, server config | Medium | 1-2 hrs |
+| 13 | **JavaScript rendering** — verify Google can render key content. Use URL Inspection tool's "View Rendered Page" | High | 1 hr |
+
+---
+
+### Phase 3: On-Page Optimization (Week 3-4)
+
+| # | Action | Impact | Effort |
+|---|--------|--------|--------|
+| 14 | **Title tag audit across all 150 pages** — unique, 50-60 chars, primary keyword front-loaded, compelling | High | 3 hrs |
+| 15 | **Meta descriptions** — unique per page, 150-160 chars, value proposition + CTA | Medium | 3 hrs |
+| 16 | **H1 audit** — one H1 per page, contains primary keyword, matches search intent | High | 2 hrs |
+| 17 | **Heading hierarchy** — logical H1 > H2 > H3 flow, no skipped levels | Low | 1 hr |
+| 18 | **Keyword cannibalization audit** — identify pages competing for the same keyword. Common in SaaS: blog post vs. feature page targeting same term | High | 2 hrs |
+| 19 | **Keyword mapping** — assign one primary + 2-3 secondary keywords per page. Document in a spreadsheet | High | 4 hrs |
+
+**Cannibalization red flag:** If both `/blog/best-project-management-software` and `/features/` target "project management software," Google won't know which to rank. Pick one, redirect or differentiate.
+
+---
+
+### Phase 4: Content Strategy (Week 4-6) — Highest Long-Term Impact
+
+This is where B2B SaaS sites most often fail. You need **topical authority**, not just keyword targeting.
+
+| # | Action | Impact | Effort |
+|---|--------|--------|--------|
+| 20 | **Content gap analysis** — compare your pages to top 5 competitors (Monday, Asana, ClickUp, Wrike, Teamwork). What do they have that you don't? | High | 4 hrs |
+| 21 | **Build comparison pages** — create `/compare/vs-asana/`, `/compare/vs-monday/` etc. These convert well and rank for high-intent terms | High | 2-3 days |
+| 22 | **Build alternative pages** — `/alternatives/asana-alternatives/`, targeting users unhappy with competitors | High | 1-2 days |
+| 23 | **Expand feature pages** — each feature (Gantt, Kanban, time tracking, reporting) needs 800+ words with screenshots, use cases, and how-tos | High | 1 week |
+| 24 | **Create use-case pages** — `/use-cases/marketing-teams/`, `/use-cases/software-development/`, `/use-cases/construction/` | High | 1 week |
+| 25 | **Build topical clusters** — example cluster around "project management": | High | Ongoing |
+
+**Example Topical Cluster:**
+```
+Pillar: /project-management-software/  (main target page)
+  ├── /blog/what-is-project-management/
+  ├── /blog/project-management-methodologies/
+  ├── /blog/agile-vs-waterfall/
+  ├── /blog/project-management-best-practices/
+  ├── /blog/how-to-create-project-plan/
+  ├── /glossary/gantt-chart/
+  ├── /glossary/critical-path/
+  ├── /templates/project-plan-template/
+  └── /guides/project-management-for-small-teams/
+```
+
+All cluster pages interlink to the pillar and to each other.
+
+| # | Action (continued) | Impact | Effort |
+|---|--------|--------|--------|
+| 26 | **Audit existing blog content** — refresh outdated posts, merge thin posts, add depth to top performers | Medium | Ongoing |
+| 27 | **Add E-E-A-T signals** — author bios with credentials, customer case studies with real data, "written by" + "reviewed by" bylines | Medium | 1-2 days |
+| 28 | **Create a glossary section** — 30-50 PM terms, each a standalone page. These build topical authority and earn long-tail traffic | Medium | 1 week |
+| 29 | **Free tools/templates** — project plan templates, budget calculators, timeline generators. These earn links naturally | High | 1-2 weeks |
+
+---
+
+### Phase 5: Structured Data & Rich Results (Week 5-6)
+
+| # | Action | Impact | Effort |
+|---|--------|--------|--------|
+| 30 | **SoftwareApplication schema** on product pages — name, pricing, rating, OS | High | 2 hrs |
+| 31 | **FAQ schema** on feature + comparison pages | Medium | 2 hrs |
+| 32 | **Organization schema** on homepage | Low | 30 min |
+| 33 | **BreadcrumbList schema** site-wide | Low | 1 hr |
+| 34 | **Review/AggregateRating schema** if you have customer reviews | High | 1 hr |
+| 35 | **HowTo schema** on tutorial/guide content | Medium | 1 hr |
+
+Validate all with Google's Rich Results Test.
+
+---
+
+### Phase 6: Internal Linking & Architecture (Week 6-7)
+
+| # | Action | Impact | Effort |
+|---|--------|--------|--------|
+| 36 | **Orphan page audit** — find pages with zero internal links pointing to them | High | 1 hr |
+| 37 | **Link depth audit** — every important page within 3 clicks of homepage | High | 1 hr |
+| 38 | **Add contextual internal links** — every blog post should link to 2-3 relevant feature/product pages | High | 3 hrs |
+| 39 | **Navigation audit** — features, pricing, use cases, resources accessible from main nav | Medium | 1 hr |
+| 40 | **Footer optimization** — link to top-level category pages, not individual posts | Low | 30 min |
+
+---
+
+### Phase 7: Authority Building (Ongoing)
+
+| # | Action | Impact | Effort |
+|---|--------|--------|--------|
+| 41 | **Backlink profile audit** — check toxic links, compare domain authority to competitors | High | 2 hrs |
+| 42 | **Digital PR** — publish original research/surveys about PM trends (linkable assets) | High | Ongoing |
+| 43 | **Guest posting** — contribute to PM and productivity publications | Medium | Ongoing |
+| 44 | **Integration partner pages** — co-marketing with tools you integrate (Slack, Google, etc.) | Medium | Ongoing |
+| 45 | **HARO / Connectively** — respond to journalist queries about project management | Medium | Ongoing |
+
+---
+
+## Quick Wins (Do This Week)
+
+These require minimal effort but yield fast results:
+
+1. **Fix title tags** on your top 10 pages by traffic — front-load keywords, add compelling hooks
+2. **Add FAQ schema** to your 5 highest-traffic pages
+3. **Interlink your top blog posts** to relevant product pages (add 2-3 contextual links each)
+4. **Submit updated sitemap** to Search Console if not done recently
+5. **Create one "vs" comparison page** for your closest competitor — these often rank within weeks
+
+---
+
+## Realistic Keyword Strategy
+
+Stop chasing "project management software" directly — it's a 3-5 year play at your domain age. Instead:
+
+| Term Type | Example | Difficulty | Timeline |
+|-----------|---------|------------|----------|
+| Long-tail | "project management software for marketing teams" | Low | 1-3 months |
+| Comparison | "asana vs [your brand]" | Medium | 2-4 months |
+| Alternatives | "monday.com alternatives" | Medium | 2-4 months |
+| Feature-specific | "gantt chart software free" | Medium | 3-6 months |
+| Educational | "how to manage multiple projects" | Low | 1-3 months |
+| Head term | "project management software" | Very High | 12-24 months |
+
+Build authority bottom-up: long-tail wins feed into topical authority, which eventually supports head-term rankings.
+
+---
+
+## Next Steps
+
+To make this audit actionable for **your specific site**, I'd need:
+
+1. **Your domain URL** — to run actual crawl checks and `site:` queries
+2. **Search Console access** — for real indexation/coverage data and keyword performance
+3. **Top 3-5 organic competitors** — for content gap analysis
+4. **Current monthly organic traffic** — to set baseline and measure progress
+5. **Any recent site changes** — redesigns, URL changes, CMS migrations
+
+Want me to dive deeper into any specific phase, or create a detailed content plan for the topical cluster strategy?

package/skills/jarvis/engineering-team/finance/.claude-plugin/plugin.json

@@ -0,0 +1,13 @@
+{
+  "name": "finance-skills",
+  "description": "2 finance skills: financial analyst (ratio analysis, DCF valuation, budgeting, forecasting) and SaaS metrics coach (ARR, MRR, churn, CAC, LTV, NRR, Quick Ratio, 12-month projections). 7 Python automation tools. Agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw.",
+  "version": "2.1.2",
+  "author": {
+    "name": "Alireza Rezvani",
+    "url": "https://alirezarezvani.com"
+  },
+  "homepage": "https://github.com/alirezarezvani/claude-skills/tree/main/finance",
+  "repository": "https://github.com/alirezarezvani/claude-skills",
+  "license": "MIT",
+  "skills": "./"
+}

package/skills/jarvis/engineering-team/finance/.codex/instructions.md

@@ -0,0 +1,28 @@
+# Finance Skills — Codex CLI Instructions
+
+When working on financial analysis tasks, use the finance skill system:
+
+## Python Tools
+
+All scripts in `finance/financial-analyst/scripts/` are stdlib-only and CLI-first:
+
+```bash
+python3 finance/financial-analyst/scripts/ratio_calculator.py --help
+python3 finance/financial-analyst/scripts/dcf_valuation.py --help
+python3 finance/financial-analyst/scripts/budget_variance_analyzer.py --help
+python3 finance/financial-analyst/scripts/forecast_builder.py --help
+```
+
+## Key Skills by Task
+
+| Task | Skill |
+|------|-------|
+| Financial ratios | financial-analyst |
+| DCF valuation | financial-analyst |
+| Budget variance | financial-analyst |
+| Forecasting | financial-analyst |
+
+## Rules
+
+- Always validate financial outputs against source data
+- Use Python tools for calculations, not manual estimates

package/skills/jarvis/engineering-team/finance/CLAUDE.md

@@ -0,0 +1,106 @@
+# Finance Skills - Claude Code Guidance
+
+This guide covers the finance skills and their Python automation tools.
+
+## Finance Skills Overview
+
+**Available Skills:**
+1. **financial-analyst/** - Financial statement analysis, ratio analysis, DCF valuation, budgeting, forecasting (4 Python tools)
+2. **saas-metrics-coach/** - SaaS financial health: ARR, MRR, churn, CAC, LTV, NRR, Quick Ratio, 12-month projections (3 Python tools)
+
+**Total Tools:** 7 Python automation tools, 5 knowledge bases, 6 templates
+
+**Commands:** 2 (`/financial-health`, `/saas-health`)
+
+## Python Automation Tools
+
+### 1. Ratio Calculator (`financial-analyst/scripts/ratio_calculator.py`)
+
+**Purpose:** Calculate and interpret financial ratios from statement data
+
+**Features:**
+- Profitability ratios (ROE, ROA, Gross/Operating/Net Margin)
+- Liquidity ratios (Current, Quick, Cash)
+- Leverage ratios (Debt-to-Equity, Interest Coverage, DSCR)
+- Efficiency ratios (Asset/Inventory/Receivables Turnover, DSO)
+- Valuation ratios (P/E, P/B, P/S, EV/EBITDA, PEG)
+- Built-in interpretation and benchmarking
+
+**Usage:**
+```bash
+python financial-analyst/scripts/ratio_calculator.py financial_data.json
+python financial-analyst/scripts/ratio_calculator.py financial_data.json --format json
+```
+
+### 2. DCF Valuation (`financial-analyst/scripts/dcf_valuation.py`)
+
+**Purpose:** Discounted Cash Flow enterprise and equity valuation
+
+**Features:**
+- Revenue and cash flow projections
+- WACC calculation (CAPM-based)
+- Terminal value (perpetuity growth and exit multiple methods)
+- Enterprise and equity value derivation
+- Two-way sensitivity analysis
+- No external dependencies (uses math/statistics)
+
+**Usage:**
+```bash
+python financial-analyst/scripts/dcf_valuation.py valuation_data.json
+python financial-analyst/scripts/dcf_valuation.py valuation_data.json --format json
+```
+
+### 3. Budget Variance Analyzer (`financial-analyst/scripts/budget_variance_analyzer.py`)
+
+**Purpose:** Analyze actual vs budget vs prior year performance
+
+**Features:**
+- Variance calculation (actual vs budget, actual vs prior year)
+- Materiality threshold filtering
+- Favorable/unfavorable classification
+- Department and category breakdown
+
+**Usage:**
+```bash
+python financial-analyst/scripts/budget_variance_analyzer.py budget_data.json
+python financial-analyst/scripts/budget_variance_analyzer.py budget_data.json --format json
+```
+
+### 4. Forecast Builder (`financial-analyst/scripts/forecast_builder.py`)
+
+**Purpose:** Driver-based revenue forecasting and cash flow projection
+
+**Features:**
+- Driver-based revenue forecast model
+- 13-week cash flow projection
+- Scenario modeling (base/bull/bear)
+- Trend analysis from historical data
+
+**Usage:**
+```bash
+python financial-analyst/scripts/forecast_builder.py forecast_data.json
+python financial-analyst/scripts/forecast_builder.py forecast_data.json --format json
+```
+
+## Quality Standards
+
+**All finance Python tools must:**
+- Use standard library only (math, statistics, json, argparse)
+- Support both JSON and human-readable output via `--format` flag
+- Provide clear error messages for invalid input
+- Return appropriate exit codes
+- Process files locally (no API calls)
+- Include argparse CLI with `--help` support
+
+## Related Skills
+
+- **C-Level:** Strategic financial decision-making -> `../c-level-advisor/`
+- **Business & Growth:** Revenue operations, sales metrics -> `../business-growth/`
+- **Product Team:** Budget allocation, RICE scoring -> `../product-team/`
+
+---
+
+**Last Updated:** March 2026
+**Skills Deployed:** 2/2 finance skills production-ready
+**Total Tools:** 7 Python automation tools
+**Commands:** /financial-health, /saas-health

package/skills/jarvis/engineering-team/finance/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: "finance-skills"
+description: "Financial analyst agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Ratio analysis, DCF valuation, budget variance, rolling forecasts. 4 Python tools (stdlib-only)."
+version: 1.0.0
+author: Alireza Rezvani
+license: MIT
+tags:
+  - finance
+  - financial-analysis
+  - dcf
+  - valuation
+  - budgeting
+agents:
+  - claude-code
+  - codex-cli
+  - openclaw
+---
+
+# Finance Skills
+
+Production-ready financial analysis skill for strategic decision-making.
+
+## Quick Start
+
+### Claude Code
+```
+/read finance/financial-analyst/SKILL.md
+```
+
+### Codex CLI
+```bash
+npx agent-skills-cli add alirezarezvani/claude-skills/finance
+```
+
+## Skills Overview
+
+| Skill | Folder | Focus |
+|-------|--------|-------|
+| Financial Analyst | `financial-analyst/` | Ratio analysis, DCF, budget variance, forecasting |
+
+## Python Tools
+
+4 scripts, all stdlib-only:
+
+```bash
+python3 financial-analyst/scripts/ratio_calculator.py --help
+python3 financial-analyst/scripts/dcf_valuation.py --help
+python3 financial-analyst/scripts/budget_variance_analyzer.py --help
+python3 financial-analyst/scripts/forecast_builder.py --help
+```
+
+## Rules
+
+- Load only the specific skill SKILL.md you need
+- Always validate financial outputs against source data