agentleFS
MosoFinMosoFin/mosofin-finance-skills/skills/duplicate-invoice-detection/SKILL.md

duplicate-invoice-detection

Skill2 starsChanged 3 months agoAGPL-3.0View on GitHub

Scans the accounts payable register for likely duplicate invoices and payments — the same invoice resubmitted, the same amount paid through two channels, altered invoice numbers, vendor-name variants, and vendor credits never applied — rates each cluster's confidence, quantifies exposure, puts unpaid duplicates first and proposes recovery. In a group, also finds one invoice paid by two entities. Reads bills, payments and the vendor master through a connected Mosofin workspace when the user agrees, or works from an uploaded AP register and payment history. States that the same-bank-account rule cannot run without vendor bank details. Use when the user asks to check for duplicate invoices or payments, scan AP for duplicates, detect invoice fraud or 'have we paid this twice', or uploads a payment history or AP register. Do not use for general fraud detection across all transaction types. Read-only: produces a duplicate-suspect workpaper with evidence, a rules-run sheet and coverage sheet, and posts nothing.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.