kyc-risk-rating

Compute composite KYC risk ratings across four FATF-aligned dimensions.

28|19|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/panaversity/agentfactory-business-plugins --skill kyc-risk-rating
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kyc-risk-rating
Source: https://github.com/panaversity/agentfactory-business-plugins/tree/main/banking/skills/kyc-risk-rating
Command: npx skills add https://github.com/panaversity/agentfactory-business-plugins --skill kyc-risk-rating

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate and standardize KYC risk rating to consistently classify customers and determine appropriate due diligence.

Core Features & Use Cases

  • FATF-aligned risk scoring across four dimensions: customer type, geography, product/service risk, and behavioural indicators.
  • Automatic determination of overall CDD level, required monitoring frequency, and escalation paths for mandatory overrides (e.g., PEPs, blacklist jurisdictions).
  • Use Case: A financial institution quickly assesses new clients, assigns risk categories, and generates a regulator-ready risk assessment with supporting rationale.

Quick Start

Run the KYC risk engine on a new customer profile to generate a risk rating and recommended CDD level.

Frequently Asked Questions about kyc-risk-rating

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calculate KYC risk ratings for new customers?▼

To calculate KYC risk ratings, aggregate four dimensions: customer type, geographic, product/service, and behavioural indicators. Apply FATF-aligned scoring to determine the overall CDD level and required monitoring frequency.

What is a FATF-aligned AML risk assessment?▼

A FATF-aligned AML risk assessment standardizes customer due diligence by scoring risk across geography, customer type, product/service, and behaviour. It determines the required CDD level and generates a regulator-ready assessment with supporting rationale.

How does CDD level affect transaction monitoring frequency?▼

CDD level directly dictates monitoring frequency by applying FATF-aligned risk scoring to customer profiles. Higher risk classifications trigger increased monitoring and mandatory escalation paths for high-risk jurisdictions or PEPs.

Can I automate PEP and high-risk jurisdiction overrides for AML compliance?▼

Yes, you can automate mandatory overrides for AML compliance. The risk engine automatically applies escalation paths when it detects PEPs or blacklist jurisdictions, ensuring regulator-ready CDD levels and trigger-based refresh recommendations.

What is the best way to standardize customer due diligence across a financial institution?▼

The best way to standardize customer due diligence is automating KYC risk scoring across four dimensions: customer type, geography, product/service, and behavioural indicators. This consistently classifies clients and yields a regulator-ready risk assessment.

When should I apply mandatory overrides in AML risk scoring?▼

Apply mandatory overrides in AML risk scoring when customers are identified as PEPs or reside in high-risk jurisdictions. These triggers bypass standard composite scoring to enforce strict CDD levels and escalate monitoring frequency.