skills/legal/sar-filing/SKILL.md
Drafts FinCEN Suspicious Activity Reports (Form 111) for BSA/AML regulatory filing. Compiles subject identification, transaction timelines, red-flag analysis, and activity classifications. Use when a financial institution detects suspicious transactions requiring mandatory SAR filing, continuing activity reports, or BSA compliance documentation.
npx skillsauth add casemark/skills sar-filingInstall 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.
Drafts a FinCEN-ready SAR (Form 111) from transaction records, investigation files, and institutional data.
Gather before drafting:
| Field | Detail | |---|---| | Filing type | Initial / Continuing / Corrective | | Institution | Legal name, EIN/LEI | | Regulator | OCC / Fed / FDIC / NCUA / State | | SAR contact | Name, title, phone, secure email | | Detection date | When activity first identified | | Filing deadline | 30 days (60 if no subject) | | Prior BSA ID | If continuing: reference number + new trigger |
Classify each party: Subject, Purchaser/Sender, Payee/Receiver, Other.
Individuals: Legal name, aliases, DOB, SSN/ITIN, address, government ID (type/number/jurisdiction/expiration). Foreign nationals: passport, citizenship, visa, high-risk jurisdiction nexus.
Entities: Legal name, DBAs, EIN, formation state/date, business nature, beneficial owners (≥25% ownership or substantial control).
Relationships: Document familial, business, signatory, nominee, or intermediary connections between parties.
For each account: number, type, open date, status (active/closed/restricted/frozen), holders/signers, stated purpose, baseline activity profile, and deviations triggering concern.
Include: branch contacts, prior compliance concerns, correspondent/MSB/processor relationships with fund-flow tracing, CIP/CDD/EDD procedures performed, closure details if applicable.
Select FinCEN categories:
| Category | Examples | |---|---| | Structuring | Below CTR thresholds | | Money laundering | Layering, integration, funnel accounts | | Terrorist financing | OFAC/SDN nexus | | Fraud | Check kiting, wire fraud, elder exploitation | | Identity crimes | Synthetic ID, stolen credentials | | Cyber | Account takeover, intrusion-related transfers | | Sanctions evasion | Sanctioned jurisdictions/persons | | Other | Unlicensed MSB, trade-based ML, human trafficking |
Thresholds: ≥$5,000 (subject identified) / ≥$25,000 (no subject). For blocked/attempted transactions, explain why filing is warranted. Confirm no exemption applies and filing is not duplicative.
State total dollar amount, currency, and complete time period.
Address Who/What/When/Where/Why/How chronologically:
Index attachments by category: transaction records, customer ID docs, correspondence, monitoring system output, investigation memos, inter-institution communications. Label each with title and narrative relevance.
development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.