new-designation-screening-test
Generate a spreadsheet of test entries — newly designated names from OFAC, OFSI, and EU sanctions lists plus deliberate variations of those names — to validate that a sanctions screening system catches fresh designations and is tuned to the right fuzziness threshold. Use this whenever the user asks for sanctions list update test data, screening regression test data, screening QA, fuzzy match calibration, or wants to verify their screening lists are current. Trigger even if the user doesn't say 'screening' explicitly — phrases like 'test my sanctions list', 'check our SDN coverage', 'is my list
npx skills add lawve-ai/awesome-legal-skills --skill new-sanctions-designation-screening-test-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.
# New Designation Screening Test Generator This skill produces a spreadsheet that compliance teams can run through their sanctions screening system to verify two things at once: 1. **Coverage** — the screening list is current (catches names added in the most recent designations). 2. **Fuzzy tuning** — the screening engine is tuned to catch realistic name variations (transliterations, transpositions, alphabet swaps), not just exact strings. Each row in the output is a single test entry: a designated name or a deliberate variation of one, plus the metadata an analyst needs to interpret a hit (or a miss). ## When to run Run when the user asks for: - New designation test data / screening regression set - Validation that their sanctions list is up to date - A fuzzy-match calibration test set - Anything matching "test my screening" or "check our [SDN/OFSI/EU] coverage" If the user doesn't specify a lookback window, default to the trailing 7 days. If they say "since last run" and provide a prior date, use that. ## Workflow ### Step 1 — Pull recent designations from the Big 3 | Regulator | Source | What to capture | |---|---|---| | OFAC | `https://ofac.treasury.gov/recent-actions` | Additi
- When to run
- Workflow
- Step 1 — Pull recent designations from the Big 3
- Step 2 — Generate 6–8 variations per name, categorized by failure mode
- Step 3 — Tag each variation with an expected match strength
- Step 4 — Build the spreadsheet
- Output checklist before delivering
- Edge cases
What does the new-designation-screening-test skill do?
Generate a spreadsheet of test entries — newly designated names from OFAC, OFSI, and EU sanctions lists plus deliberate variations of those names — to validate that a sanctions screening system catches fresh designations and is tuned to the right fuzziness threshold. Use this whenever the user asks for sanctions list update test data, screening regression test data, screening QA, fuzzy match calibration, or wants to verify their screening lists are current. Trigger even if the user doesn't say 'screening' explicitly — phrases like 'test my sanctions list', 'check our SDN coverage', 'is my list
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill new-sanctions-designation-screening-test-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.