Screen customers against sanctions and PEP watchlists with HITL decision gates.
npx skills add https://github.com/vyayasan/kyc-analyst --skill screening-vyayasan
Please help me install this Agent Skill. Skill: screening Source: https://github.com/vyayasan/kyc-analyst/tree/main/skills/screening Command: npx skills add https://github.com/vyayasan/kyc-analyst --skill screening-vyayasan
Screening customers against sanctions and PEP lists is repetitive, time-consuming, and easy to document inconsistently, especially when you must assess false positives and escalate uncertain cases.
Use case example: You onboard a customer and beneficial owners, run screening across relevant databases, then generate a manager/MLRO escalation brief only for true matches or unclear cases while documenting why likely false positives are accepted.
Run screening for a customer name and attributes by invoking /kyc:onboard-interactive with the customer identity and risk context.
High-intent search queries and answers about installing and using this skill.
Sanctions and PEP screening searches multiple watchlists like OFAC, EU, and UN for each customer target, evaluating match quality to reduce false positives. It applies to onboarding, refresh, and batch screening scenarios covering individuals, entities, and beneficial owners.
False positive assessment during watchlist screening evaluates name similarity, DOB, nationality, location, evidence, and contextual support signals. It applies human-in-the-loop decision gates categorized as TRUE MATCH, FALSE POSITIVE, or UNCERTAIN to ensure accurate compliance outcomes.
Regulatory escalation briefs for KYC screening matches are produced for TRUE MATCH and UNCERTAIN outcomes. The screening process generates compliance-ready reports with documentation artifacts and manager or MLRO escalation outputs when warranted.
Sanctions screening supports onboarding, refresh, and ad hoc or batch screening scenarios. It searches over twelve databases including OpenSanctions and Interpol, recording search evidence and applying decision gates for individuals, entities, directors, and close associates.
Human-in-the-loop decision gates are required for AML compliance screening to categorize outcomes as TRUE MATCH, FALSE POSITIVE, or UNCERTAIN. This ensures regulatory-style reporting accuracy and proper documentation of likely false positives before acceptance.
JoelLewisEmbed CIP/KYC identity verification and OFAC sanctions screening into account opening workflows.
writerReview sanctions screening hits and document OFAC match dispositions.
brainbytes-devDesign AML/KYC compliance programs with customer due diligence and risk classification.
smith-hornDeploy and manage cloud-based AI agent swarms with Flow Nexus.
