Forensic Accounting

Investigate financial discrepancies and suspected fraud with Benford's Law screening, vendor link analysis, round-trip tracking, and an evidence-chained forensic report.

⚠️ **Finance warning / Avertissement finance** : informational only, not investment advice. A forensic investigation can accuse real people and feed real legal proceedings: statistical flags are leads, not proof, mishandled evidence can damage a case, and any loss figure here is an estimate to be proven, never a promise of recovery or return. Accounting documents and conclusions produced with this skill must be verified by a qualified professional before any official use. Curated by Skill Harbor: the forensic accounting skill of GAJETOso/financeskills, written from the seat of a forensic accountant and certified fraud examiner. Use it for litigation support or a high-stakes internal investigation when something does not add up: suspicious transactions, missing funds, embezzlement checks, laundering detection, shell company questions or whistleblower claims. The assessment fixes the investigation context (legal case or internal, the specific suspicion, the period in question) and the access and confidentiality terms (bank statements, emails, ERP logs, and who is authorized to see the findings, privileged or not). The skill is honest about a hard limit: generic fetching and scraping cannot access secure banking portals or private ERP environments, so evidence must arrive as static files such as CSV exports or PDF statements, and no transaction is claimed as verified without raw source data. The framework follows the money in priority order: source of funds, use of funds, the internal control gaps that made it possible, and intent, error versus deliberate. The technical steps run Benford's Law analysis on leading digits to spot manufactured numbers, vendor link analysis matching employee addresses and phone numbers against vendor databases to flag ghost vendors and insider-owned shells, round-trip tracking for funds that leave and return through intermediaries, and a lifestyle audit where external data is available. The report structure quantifies the loss, lays out the evidence chain step by step with transaction reference IDs, lists the entities involved, and closes with specific control hardening recommendations. From the GAJETOso/financeskills repository (MIT). Skill Harbor never reviews the code, review it yourself before use.

At a glance

What: Investigate financial discrepancies and suspected fraud with Benford's Law screening, vendor link analysis, round-trip tracking, and an evidence-chained forensic report.
Cost: Free
Needs: Use "Forensic Accounting" with your Muse.
Install: Copy the installer prompt below into your Muse — your agent does the rest.

⚠️ **Finance warning / Avertissement finance** : informational only, not investment advice. A forensic investigation can accuse real people and feed real legal proceedings: statistical flags are leads, not proof, mishandled evidence can damage a case, and any loss figure here is an estimate to be proven, never a promise of recovery or return. Accounting documents and conclusions produced with this skill must be verified by a qualified professional before any official use. Curated by Skill Harbor: the forensic accounting skill of GAJETOso/financeskills, written from the seat of a forensic accountant and certified fraud examiner. Use it for litigation support or a high-stakes internal investigation when something does not add up: suspicious transactions, missing funds, embezzlement checks, laundering detection, shell company questions or whistleblower claims. The assessment fixes the investigation context (legal case or internal, the specific suspicion, the period in question) and the access and confidentiality terms (bank statements, emails, ERP logs, and who is authorized to see the findings, privileged or not). The skill is honest about a hard limit: generic fetching and scraping cannot access secure banking portals or private ERP environments, so evidence must arrive as static files such as CSV exports or PDF statements, and no transaction is claimed as verified without raw source data. The framework follows the money in priority order: source of funds, use of funds, the internal control gaps that made it possible, and intent, error versus deliberate. The technical steps run Benford's Law analysis on leading digits to spot manufactured numbers, vendor link analysis matching employee addresses and phone numbers against vendor databases to flag ghost vendors and insider-owned shells, round-trip tracking for funds that leave and return through intermediaries, and a lifestyle audit where external data is available. The report structure quantifies the loss, lays out the evidence chain step by step with transaction reference IDs, lists the entities involved, and closes with specific control hardening recommendations. From the GAJETOso/financeskills repository (MIT). Skill Harbor never reviews the code, review it yourself before use.

Version:

@

Created by: @gajetoso

Not verified? How to check before you trust →

Install — Free · open source (MIT) View source code

⌁

Install

Copy the install package below, then paste it into Muse

Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a build before installing →

After installation, ask me if I want to leave private feedback
Private for now: only the Skill Harbor team sees it. Sellers may be looped in later.

Use "Forensic Accounting" with your Muse. Prerequisites: the evidence itself as static files (CSV exports, PDF bank statements, ERP logs), the specific suspicion and the period in question, whether this serves a legal case, and who is authorized to see the findings. This skill cannot access banking portals or private ERP systems, and it will not verify anything without raw source data. Its documents and conclusions must be verified by a qualified professional before any official or legal use. Informational only, not investment advice. 1. Open the skill: https://github.com/GAJETOso/financeskills/blob/main/skills/forensic-accounting/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Run the investigation in order: source of funds, use of funds, control gaps, intent. Run the Benford screen, the vendor link analysis and the round-trip tracking, and deliver the forensic report with the evidence chain and reference IDs for every transaction cited." 3. Keep flagged items labeled as leads until the underlying source documents prove them; do not let a statistical flag read as a finding. Tip: decide the privilege question before the work starts, not after the report exists; it changes who should receive the findings. Safety: a skill is plain-text instructions; it runs nothing by itself. Investigation support only, no orders and no account access. Informational only, not investment advice.

?

Questions

How do I install a build?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.