enforcement-action-analysis-amir-fadavi
Analyze any OFAC or OFSI enforcement action — by URL, pasted text, or uploaded document — and produce a structured root cause analysis as a formatted Excel (.xlsx) spreadsheet. Use this skill whenever a user names, links to, pastes, or uploads an OFAC or OFSI enforcement action and asks for any of the following: root cause analysis, compliance gaps, what went wrong, lessons learned, organizational self-assessment, or remediation planning. Also trigger when a user asks \"analyze this enforcement action\", \"what were the root causes\", \"turn this into a checklist\", or \"how do I make sure thi
npx skills add lawve-ai/awesome-legal-skills --skill enforcement-action-analysis-amir-fadavi --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Enforcement Action Analysis Skill Produces a structured root cause analysis of any OFAC or OFSI enforcement action as a formatted Excel spreadsheet. The output is a six-column table designed to be used as a working document by compliance officers, in-house counsel, external counsel, and consultants — at financial institutions and non-financial firms alike. --- ## Input The user will provide the enforcement action in one of three ways: 1. **URL** — fetch and parse the document (PDF or HTML) 2. **Pasted text** — use the text directly from the conversation 3. **Uploaded file** — read from `/mnt/user-data/uploads/` If none is provided, ask the user to supply the enforcement action before proceeding. --- ## Step 1 — Extract the Case Facts Before identifying root causes, extract the following from the enforcement action: - **Subject** (name of the settling party) - **Regulator** (OFAC or OFSI; include department/division if stated) - **Date** of settlement or enforcement release - **Settlement amount** - **Sanctions program** (e.g., Iran, Russia, Cuba) and specific regulations cited - **Violation period** - **Number of apparent violations** - **Egregious / non-egregious** - **Voluntari
- Input
- Step 1 — Extract the Case Facts
- Step 2 — Identify Root Causes
- Column: What Went Wrong
- Column: How It Went Wrong
- Column: What Could Have Stopped It
- OFAC Root Cause Taxonomy (reference)
- Step 3 — Build the Spreadsheet
- Sheet structure
- Column layout
- Styling
- Output path
- Full code template
- Step 4 — Present the File
What does the enforcement-action-analysis-amir-fadavi skill do?
Analyze any OFAC or OFSI enforcement action — by URL, pasted text, or uploaded document — and produce a structured root cause analysis as a formatted Excel (.xlsx) spreadsheet. Use this skill whenever a user names, links to, pastes, or uploads an OFAC or OFSI enforcement action and asks for any of the following: root cause analysis, compliance gaps, what went wrong, lessons learned, organizational self-assessment, or remediation planning. Also trigger when a user asks \"analyze this enforcement action\", \"what were the root causes\", \"turn this into a checklist\", or \"how do I make sure thi
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill enforcement-action-analysis-amir-fadavi --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.