Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Financial Analysis Summary

ASecurity

Generates structured summaries of financial analyses for commercial litigation. Use when summarizing expert financial reports, economic damages analyses, lost profits calculations, business valuations, or financial dispute evidence for litigation support.

15 stars
0 votes
0 copies
2 views
Added 6/7/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill financial-analysis-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Financial Analysis Summary?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Financial Analysis Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-financial-analysis-summary/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-financial-analysis-summary)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: financial-analysis-summary
title: Financial Analysis Summary
description: Generates structured summaries of financial analyses for commercial litigation. Use when summarizing expert financial reports, economic damages analyses, lost profits calculations, business valuations, or financial dispute evidence for litigation support.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/financial-analysis-summary
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
---

# Financial Analysis Summary

Distills forensic accounting reports, economic damage studies, and expert financial findings into structured litigation summaries.

## Prerequisites

- **Source analysis** — expert reports, forensic accounting workpapers, or damage studies
- **Financial records** — statements, tax returns, transaction ledgers relied upon by the expert
- **Case context** — dispute type, relevant time period, jurisdiction, intended use (settlement, trial, appellate)

## Quick Start

1. Identify the dispute type and damage theory
2. Extract principal conclusions and dollar figures from the expert report
3. Map each conclusion to its methodology and supporting evidence
4. Build the summary following the output structure below
5. Calibrate tone to the target audience (jury, judge, opposing counsel)

## Output Structure

### 1. Executive Overview

Table with: nature of dispute, examination time period, principal conclusions (top-line damages or valuation range), expert name/credentials/scope.

### 2. Methodology

For each analytical approach, document:

- Method name and plain-language explanation
- Why selected for this case
- Applicable standards (GAAP, AICPA, ASA, NACVA)
- Key assumptions and inputs

Reference by claim type:

| Claim Type | Typical Methods |
|---|---|
| Lost profits | Before-and-after, yardstick, sales projection |
| Business valuation | DCF, market multiples, asset-based |
| Economic damages | But-for analysis, mitigation offset |
| Fraud/disgorgement | Tracing, net equity analysis |

### 3. Key Financial Findings

Present in causal sequence:

1. **Wrongful act** — financial impact chain
2. **Quantification** — calculations with stated assumptions
3. **Supporting evidence** — source documents, corroborating data
4. **Damage period** — start/end dates with rationale
5. **Total damages/valuation** — breakdown by component

Use tabular format: damage component, amount, method, period.

### 4. Data Sources & Limitations

- List each source with reliability assessment
- Identify record gaps and how addressed (interpolation, proxy data, conservative assumptions)
- Note documents requested but not produced

### 5. Sensitivity Analysis

Table comparing scenarios: base case, conservative, aggressive, and opposing expert position — each showing variable changed and resulting range.

### 6. Visual Exhibits

Include where they clarify analysis: trend charts, actual-vs-projected tables, waterfall charts, timeline diagrams. Number sequentially and cross-reference in text.

### 7. Summary of Opinions

Restate each conclusion in clear, quotable language with dollar amounts and basis.

## Pitfalls & Checks

- **Daubert/Frye readiness** — confirm methods are generally accepted and reliably applied to case facts; flag the jurisdiction's admissibility standard
- **Audience calibration** — settlement: leverage points and ranges; trial: clarity for lay jurors; appellate: methodological soundness
- **Objectivity** — present persuasively within the bounds of evidence; never overstate certainty
- **Precision** — all dollar amounts at appropriate precision; always include time periods and qualifications
- **Citations** — reference source documents, expert report page numbers, and supporting financial records for each conclusion
- **Competing experts** — acknowledge opposing methodologies and explain divergence points
- **Jurisdiction** — U.S.-focused by default; adapt admissibility standards and professional frameworks for non-U.S. matters

Attribution

ThomasMoreAIThomasMoreAI
View sourceSee grades on GitHubMore from ThomasMoreAI →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →