KYC Desk - an onboarding packet in, a CIP file out

Paste the client or investor onboarding packet you were just handed - the application, the ownership chart, the identification details, the source-of-funds narrative, the document list, whatever you have - and get the five things an onboarding analyst produces from it, in one sitting. Five lanes over one packet: the structured KYC record with an explicit account of what the packet does not contain; a customer-identification determination that separates present from verified and routes the application to the approval tier it needs; a CDD customer risk rating argued factor by factor with its enhanced-diligence triggers and refresh interval; an anti-money-laundering review of the declared funding and activity; and the client-facing request for information that closes the gaps, paired with the internal action plan. A free in-browser prescan reads the packet before anything is sent: it walks the ownership chains and multiplies every indirect holding out against the FinCEN 25% threshold so a person holding 24% twice is surfaced at 48%, foots each entity's direct owners to 100% against a tolerance derived from the precision they were written to, checks the CIP elements party by party, validates SSN and EIN structure and passport shape and document expiry, computes ages against the senior-investor line, resolves jurisdictions by whole name against a dated snapshot, foots the funding schedule against the $10,000 reporting threshold including same-day sub-threshold sets that cross it together, matches the document inventory against the required set for the account type, and scores the risk factors with every term and the total printed - and the model then has to answer for each of those findings. Every declaration is three-valued, so "PEP: n/a" reads as unanswered and never as no. Identities are masked in your browser before anything is sent and the run is blocked if a masked value survives into the request. It screens nothing: it holds no sanctions, PEP or adverse-media list and reaches no network, so a packet with no screening result yields "screening is not evidenced", never "clear". Derived from five agent skills: @anthropics/kyc-doc-parse (parsing an onboarding packet into structured KYC fields, Apache-2.0), @joellewis/know-your-customer (customer identification, due diligence and risk rating), @joellewis/anti-money-laundering (BSA/AML red flags, structuring, reporting thresholds), @joellewis/account-opening-compliance (risk-based approval routing) and @joellewis/client-onboarding (NIGO remediation and the request letter) - the four @joellewis skills MIT. A derived work, not affiliated with or endorsed by their authors. Drafts for a human reviewer; not legal or compliance advice and not a regulatory determination.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.