What problem does it solve? Compliance officers and banking agents often know a regulation but not which concrete customer, account, or transaction fields must be present and in what state to satisfy it. This Skill translates regulatory rules into a precise, field-level requirements breakdown against the bank's live data model, identifying exactly what data is collected, missing, or needs verification. ## Core Features & Use Cases - Rule-to-Field Mapping: Retrieves applicable rules via search_compliance_rules and maps each requirement to a concrete data-model field (e.g., kyc_status == "verified", age derived from date_of_birth). - Gap Analysis: When supplied with a customer's actual data, marks every requirement as met, missing, or needs-verification and lists blocking gaps in priority order. - Determination Output: Produces an approve / review / reject / escalate decision with a requirements checklist table, documentary evidence list, and cited sources. - Use Case: An agent asked "what do we still need to collect to open a credit card for this customer?" receives an extensive checklist covering identity, KYC status, age gating, income evidence, and existing-relationship rules, each tied to a specific field and regulation section. ## Quick Start Ask the compliance agent what data is required for a customer to be compliant when opening a savings account, and include any known customer field values for a gap analysis.
