.archive/finance-team/skills/financial-analysis/SKILL.md
Comprehensive financial analysis workflow covering ratio analysis, trend analysis, benchmarking, and variance analysis. Delivers documented, audit-ready insights.
npx skillsauth add lerianstudio/ring financial-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill provides a structured workflow for comprehensive financial analysis using the financial-analyst agent.
The financial analysis workflow follows 5 phases:
| Phase | Name | Description | |-------|------|-------------| | 1 | Objective Definition | Clarify analysis scope and questions | | 2 | Data Collection | Gather and verify source documents | | 3 | Analysis Execution | Calculate ratios, identify trends | | 4 | Interpretation | Draw conclusions, identify insights | | 5 | Documentation | Prepare audit-ready deliverable |
MANDATORY: Define analysis scope before proceeding
| Question | Purpose | |----------|---------| | What decision does this analysis support? | Ensures relevance | | What time periods are being analyzed? | Sets scope | | What comparisons are needed? | Determines benchmarks | | Who is the audience? | Tailors presentation | | What is the materiality threshold? | Focuses effort |
If ANY of these are unclear, STOP and ask:
MANDATORY: Verify all data sources before analysis
| Analysis Type | Required Data | |--------------|---------------| | Trend Analysis | 3-5 periods of financial statements | | Peer Comparison | Peer company financials (same period) | | Variance Analysis | Budget/forecast and actual results | | Credit Analysis | Balance sheet, cash flow, debt schedules |
| Check | Verification | |-------|--------------| | Source documented | Each data point cites source | | Period matched | All data from same period | | Currency consistent | Single currency or conversion noted | | Audit status | Audited vs unaudited noted |
| Rationalization | Why It's WRONG | Required Action | |-----------------|----------------|-----------------| | "Data looks right" | Looks right ≠ is right | VERIFY against source | | "Same source as always" | Sources can change | CONFIRM source current | | "Minor discrepancy" | All discrepancies matter | INVESTIGATE and document |
Dispatch to specialist with full context
Task tool:
subagent_type: "ring:financial-analyst"
prompt: |
Perform financial analysis per these specifications:
**Objective**: [from Phase 1]
**Period**: [time periods]
**Comparison**: [benchmarks/peers]
**Materiality**: [threshold]
**Data Provided**:
[Attach verified data from Phase 2]
**Required Analysis**:
- [ ] Ratio analysis (liquidity, profitability, leverage, efficiency)
- [ ] Trend analysis (period over period)
- [ ] Benchmark comparison (if applicable)
- [ ] Variance analysis (if applicable)
**Output Requirements**:
- All calculations shown
- All sources cited
- All assumptions documented
| Element | Requirement | |---------|-------------| | Executive Summary | Key findings in 3-5 bullets | | Analysis Methodology | Methods used and why | | Key Findings | With supporting calculations | | Data Sources | Complete citation | | Assumptions | All assumptions documented | | Recommendations | Actionable next steps |
MANDATORY: Provide context for all findings
| Finding Type | Required Context | |--------------|------------------| | Ratio result | Industry comparison, trend direction | | Variance | Root cause, materiality assessment | | Trend | Sustainability, drivers, implications | | Anomaly | Investigation result, explanation |
| Check | Validation | |-------|------------| | Findings supported | Each finding traces to data | | Conclusions logical | Interpretation follows from facts | | Recommendations actionable | Clear next steps provided | | Limitations disclosed | Analysis boundaries stated |
MANDATORY: Ensure audit-ready deliverable
| Element | Status | |---------|--------| | All data sources cited | Required | | All calculations shown | Required | | All assumptions documented | Required | | Methodology explained | Required | | Limitations disclosed | Required | | Version control | Required |
See shared-patterns/execution-report.md for base metrics.
Analysis-Specific Metrics:
See shared-patterns/pressure-resistance.md for universal pressures.
| Pressure Type | Request | Agent Response | |---------------|---------|----------------| | "Just give me the conclusion" | "I'll provide conclusions with supporting analysis. Undocumented conclusions cannot be defended." | | "Skip the ratios we don't need" | "Comprehensive analysis requires complete ratio set. I'll calculate all standard ratios." | | "Use approximate numbers" | "Analysis requires precise figures. I'll use exact amounts from source documents." |
See shared-patterns/anti-rationalization.md for universal anti-rationalizations.
| Rationalization | Why It's WRONG | Required Action | |-----------------|----------------|-----------------| | "Standard analysis doesn't need documentation" | ALL analysis needs documentation | DOCUMENT methodology | | "Ratios speak for themselves" | Ratios need interpretation | PROVIDE context | | "Industry benchmark is well-known" | Benchmarks need citation | CITE source | | "Similar to prior analysis" | Each analysis is independent | PERFORM fresh analysis |
Upon completion, report:
| Metric | Value | |--------|-------| | Duration | Xm Ys | | Data Sources | N verified | | Ratios Calculated | N | | Trends Identified | N | | Recommendations | N | | Result | COMPLETE/PARTIAL |
| Indicator | Status | |-----------|--------| | All sources verified | YES/NO | | All calculations shown | YES/NO | | All assumptions documented | YES/NO | | Audit ready | YES/NO |
development
Analyzes a Go service using lib-commons v2/v3 and generates a visual migration report showing every change needed to upgrade to lib-commons v4. Produces an interactive HTML page (via ring:visualize) and optionally generates refactoring tasks for ring:dev-cycle.
documentation
Patterns and structure for writing functional documentation including guides, conceptual explanations, tutorials, and best practices documentation.
development
Patterns and structure for writing API reference documentation including endpoint descriptions, request/response schemas, and error documentation.
documentation
Voice and tone guidelines for technical documentation. Ensures consistent, clear, and human writing across all documentation.