agentleFS
iblaiiblai/financial-services-agents/skills/lexisnexis-worldcompliance/SKILL.md

lexisnexis-worldcompliance

Skill15 starsChanged 5 months agoMITView on GitHub

LexisNexis WorldCompliance screening platform; lets an agent screen individuals and entities against OFAC SDN, PEP databases, global sanctions lists, and adverse media with confidence-scored match results.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run PEP screening to identify politically exposed persons and their close associates

    line 14
  2. Distinctive:

    Run ongoing monitoring alerts for existing customers against updated list versions

    line 18
  3. Distinctive:

    Always log the list version and screening timestamp with each result — regulators expect evidence that the correct list version was in …

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

LexisNexis WorldCompliance

What it is

LexisNexis WorldCompliance is a global sanctions, PEP (Politically Exposed Person), and adverse media screening database used by financial institutions to satisfy AML, KYC, and OFAC compliance obligations. It covers OFAC SDN and consolidated non-SDN lists, FATF grey/black lists, hundreds of global sanctions programs, law enforcement databases, and real-time adverse media. The KYC/AML and compliance agents rely on it as the primary watchlist screening engine.

When to use this skill

  • Screen a new customer's name, date of birth, and nationality against OFAC and global sanctions lists
  • Run PEP screening to identify politically exposed persons and their close associates
  • Retrieve adverse media results for enhanced due diligence (EDD) on high-risk customers
  • Log the list version and screening timestamp for AML audit trail requirements
  • Confirm match dispositions (true match vs. false positive) and record analyst sign-off
  • Run ongoing monitoring alerts for existing customers against updated list versions

Credentials

This skill authenticates using env vars declared in metadata above. Set them in ~/.openclaw/.env (see .env.example at the config root). Required variables:

  • LEXISNEXIS_WC_API_KEY - WorldCompliance API key
  • LEXISNEXIS_WC_API_SECRET - WorldCompliance API secret
  • LEXISNEXIS_WC_BASE_URL - API base URL (e.g. https://api.worldcompliance.com/v1)

Key operations

  • POST /screening/entity — screen an individual or entity; returns match results with confidence scores and list detail
  • GET /screening/results/{screeningId} — retrieve a previous screening result by ID
  • POST /screening/entity/batch — submit a batch of entities for bulk screening
  • GET /lists — retrieve available list versions and their effective dates
  • POST /dispositions/{screeningId} — record a match disposition (true match / false positive) with analyst ID
  • GET /monitoring/alerts — retrieve ongoing monitoring alerts for enrolled entities

Notes

  • Always log the list version and screening timestamp with each result — regulators expect evidence that the correct list version was in effect at the time of screening
  • Confidence score thresholds for auto-pass vs. manual review should be set by your compliance officer; do not change thresholds without approval
  • Adverse media screening is a separate entitlement from sanctions/PEP screening; confirm subscription scope
  • Sandbox environment uses test entity profiles that return predictable match results; never run sandbox credentials against production lists

Download now (ZIP)

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.