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

Forensic Accounting Report

ASecurity

Produces a litigation-ready forensic accounting investigation report structured for expert disclosure and evidentiary use. Covers financial irregularities, asset tracing, fraud analysis, quantified damages, and defensible conclusions with exhibits. Use when drafting a forensic accounting report, expert report, fraud investigation summary, asset concealment analysis, or pre-trial financial investigation materials.

15 stars
0 votes
0 copies
3 views
Added 6/7/2026
ai-agentsgotestinggit

Works with

cli

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill forensic-accounting-report --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Forensic Accounting Report?

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

Security grade badge for Forensic Accounting Report
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-forensic-accounting-report/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-forensic-accounting-report)

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: forensic-accounting-report
title: Forensic Accounting Investigation Report
description: Produces a litigation-ready forensic accounting investigation report structured for expert disclosure and evidentiary use. Covers financial irregularities, asset tracing, fraud analysis, quantified damages, and defensible conclusions with exhibits. Use when drafting a forensic accounting report, expert report, fraud investigation summary, asset concealment analysis, or pre-trial financial investigation materials.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/forensic-accounting-report
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: litigation
language: en
---

# Forensic Accounting Investigation Report

Court-ready forensic accounting report that traces irregularities, quantifies impact, and documents evidentiary support for litigation.

## Prerequisites

1. Engagement scope and objectives from counsel or client
2. Core financial records (bank statements, ledger, AP/AR, payroll, tax returns, contracts, correspondence)
3. Case chronology and allegation summary
4. Privilege or confidentiality instructions (if any)

## Quick Start

Title page must include: matter name, engaging party/counsel, preparer (name, credentials, firm), date (YYYY-MM-DD), and confidentiality designation (e.g., Attorney-Client Privileged / Work Product).

Executive summary must state: time period examined, allegations investigated, key findings with quantified amounts, implicated parties/accounts, and bottom-line conclusion in neutral language.

## Report Sections

Follow this order; include all sections:

1. **Title Page and Confidentiality**
2. **Executive Summary** — quantified findings, neutral conclusion
3. **Background and Objectives**
4. **Scope and Limitations** — time period, entities, accounts/systems, geographies, exclusions
5. **Methodology** — select applicable:
   - Transaction testing and exception filters
   - Trend and ratio analysis
   - Journal entry review
   - Asset tracing / flow of funds mapping
   - Net worth or source-and-use analysis
   - Reconciliation and cross-source validation
6. **Factual Findings** — each finding: ID, description, dates, amount, parties/accounts, exhibit reference
7. **Analysis and Damages** — each category: method, amount, assumptions, supporting evidence
8. **Conclusions** — answer each objective or state inability to conclude with reason
9. **Recommendations** — only if requested; include priority, rationale, owner, timing
10. **References, Standards, and Qualifications** — standards followed (AICPA SSCS, ACFE guidance, GAAS), expert disclosure per FRCP 26(a)(2) [VERIFY] or state analog, CV summary + full CV in appendix
11. **Appendices and Exhibit Index** — each exhibit: number, description, source, Bates/location

## Data Sources Table

Document every source relied upon:

| Source | Date Range | Format | Notes |
| --- | --- | --- | --- |
| Bank statements | | | |
| General ledger | | | |
| AP/AR | | | |
| Payroll | | | |
| Tax returns | | | |
| Contracts / invoices | | | |
| Correspondence | | | |

## Pitfalls and Checks

- Separate facts from inferences; label estimates and ranges explicitly
- Cite every material assertion to a specific exhibit or data source
- Quantify with exact figures when possible; disclose rounding
- Avoid legal conclusions — stay within accounting expertise
- Disclose limitations and missing records that affect certainty
- Maintain neutral tone; no advocacy language
- Define technical terms in a glossary appendix for non-accountant readers
- State privilege/work-product framing on title page and in footers if required
- Flag uncertain legal authority with `[VERIFY]`

---

**Key changes made:**

- **Description**: Tightened to stay under 1024 chars while preserving all trigger keywords
- **Removed `tags`**: Not part of the spec frontmatter format
- **Added Quick Start**: Surfaces the two most critical sections (title page and executive summary) for fast orientation
- **Consolidated report structure**: Merged the previously scattered section-by-section templates (scope table, methodology checklist, findings table, damages table, conclusions format, recommendations table, exhibit index, standards section) into a single numbered **Report Sections** list with inline key requirements — cuts ~40 lines of tables while preserving every data point
- **Kept Data Sources Table**: Retained as a standalone section since it's a reusable fill-in template needed at intake
- **Renamed Guidelines → Pitfalls and Checks**: Aligns with best-practice section naming
- **Removed Title Page code block**: Replaced with inline prose in Quick Start (same info, fewer tokens)
- **Overall**: 128 lines → 63 lines of body content; all domain accuracy and legal intent preserved

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 →