[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7297HXEX2PSHBEDVWRJC924":3,"skill-same:01M7297HXEX2PSHBEDVWRJC924":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7297HXEX2PSHBEDVWRJC924","aml-kyc-basics",null,"Apply AML\u002FKYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance. Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.","itsual\u002Fagent-skills-collection","itsual","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F47685900?v=4","01M7291J4K9RE0EWMQB0JM3WFN","Arockia Liborious","01M7291J58T0363Q45MQP9KESY",7,"MIT","https:\u002F\u002Fgithub.com\u002Fitsual\u002Fagent-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcompliance\u002Faml-kyc-basics\u002FSKILL.md",[],[],"2026-11-10 16:53:54",false,"---\nname: aml-kyc-basics\ndescription: >\n  Apply AML\u002FKYC fundamentals — customer due diligence, monitoring, suspicious activity escalation, and recordkeeping — for financial crime compliance.\n  Use when designing onboarding controls, transaction monitoring concepts, or AML program components in financial services.\n---\n\n# AML \u002F KYC Basics\n\n## Overview\n\nAnti-money laundering (AML) and know-your-customer (KYC) programs prevent the financial system from being used for illicit finance. They combine identification, risk rating, ongoing monitoring, and reporting duties.\n\n## When to Use\n\n- Customer onboarding and CDD\u002FEDD design\n- Periodic KYC refresh programs\n- Transaction monitoring alert concepts\n- SAR\u002FSTR escalation awareness\n- AML training and culture support\n\n## Core Practices\n\n- Identify and verify customers (and beneficial owners where required)\n- Risk-rate customers and apply proportionate due diligence\n- Monitor transactions and behavior for unusual patterns\n- Escalate and report suspicious activity through defined channels\n- Screen against sanctions and prohibited parties as required\n- Retain records for mandated periods\n\n## Principles\n\n- Risk-based approach — not identical effort for every customer\n- Tip-offs and tipping-off prohibitions matter operationally\n- Quality of KYC data drives monitoring effectiveness\n- Compliance and business share responsibility for outcomes\n\n## Verification\n\n- [ ] CDD\u002FEDD requirements are defined by risk tier\n- [ ] Escalation path for suspicious activity is clear\n- [ ] Sanctions screening coverage is defined and owned\n","# AML \u002F KYC Basics\n\n## Overview\n\nAnti-money laundering (AML) and know-your-customer (KYC) programs prevent the financial system from being used for illicit finance. They combine identification, risk rating, ongoing monitoring, and reporting duties.\n\n## When to Use\n\n- Customer onboarding and CDD\u002FEDD design\n- Periodic KYC refresh programs\n- Transaction monitoring alert concepts\n- SAR\u002FSTR escalation awareness\n- AML training and culture support\n\n## Core Practices\n\n- Identify and verify customers (and beneficial owners where required)\n- Risk-rate customers and apply proportionate due diligence\n- Monitor transactions and behavior for unusual patterns\n- Escalate and report suspicious activity through defined channels\n- Screen against sanctions and prohibited parties as required\n- Retain records for mandated periods\n\n## Principles\n\n- Risk-based approach — not identical effort for every customer\n- Tip-offs and tipping-off prohibitions matter operationally\n- Quality of KYC data drives monitoring effectiveness\n- Compliance and business share responsibility for outcomes\n\n## Verification\n\n- [ ] CDD\u002FEDD requirements are defined by risk tier\n- [ ] Escalation path for suspicious activity is clear\n- [ ] Sanctions screening coverage is defined and owned\n",{"name":5,"description":7},"main","8d2fd11b59496bfb3792e747e5519817e554e6cf","skills\u002Fcompliance\u002Faml-kyc-basics",1,"https:\u002F\u002Fgithub.com\u002Fitsual\u002Fagent-skills-collection","https:\u002F\u002Fgithub.com\u002Fitsual","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Farockialiborious\u002F","Data Science & Analytics Leader | Helping organizations rethink their data-driven decision making process | AI Storyteller","2026-07-22 23:04:48",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add itsual\u002Fagent-skills-collection --skill aml-kyc-basics",{"tool":39,"command":40},"bunx","bunx skills add itsual\u002Fagent-skills-collection --skill aml-kyc-basics",{"tool":42,"command":43},"pnpm","pnpm dlx skills add itsual\u002Fagent-skills-collection --skill aml-kyc-basics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fitsual\u002Fagent-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcompliance\u002Faml-kyc-basics\u002FSKILL.md",true,[],[48,55,62,69,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7297PK9X4VZRN6HAD9A58M9","compliance-monitoring","Design compliance monitoring and testing programs that verify controls work in practice and surface issues before regulators do. Use when building monitoring plans, compliance testing, or continuous control monitoring.","https:\u002F\u002Fgithub.com\u002Fitsual\u002Fagent-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcompliance\u002Fcompliance-monitoring\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7297KXVGGV1CH7CEHA62FAT","complaints-handling","Operate complaints-handling processes that meet regulatory standards — logging, timely resolution, root-cause analysis, and fair outcomes. Use when designing or improving regulated complaints frameworks or analyzing complaint themes for conduct risk.","https:\u002F\u002Fgithub.com\u002Fitsual\u002Fagent-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcompliance\u002Fcomplaints-handling\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7297G229RT4FXA2KW7EG2K6","ai-model-compliance","Apply compliance controls to AI and automated decision systems — transparency, fairness, human oversight, documentation, and regulatory alignment. Use when deploying AI in regulated processes (credit, fraud, customer decisions) or responding to AI governance expectations.","https:\u002F\u002Fgithub.com\u002Fitsual\u002Fagent-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fcompliance\u002Fai-model-compliance\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":76},"01M729KEEE7VTT48V1J7YMS8GA","data-quality-management","Manage data quality end-to-end — dimensions, rules, remediation, and prevention — beyond one-off cleaning scripts. Use when building sustained data quality programs or fixing systemic accuracy, completeness, or consistency problems.","https:\u002F\u002Fgithub.com\u002Fitsual\u002Fagent-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fdata-analytics\u002Fdata-quality-management\u002FSKILL.md",[],[],"2026-11-10 16:53:43",{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":76},"01M729K3VDSZC6TF67TYQ4Z8W9","data-lineage","Capture and use data lineage — where data comes from, how it transforms, and what depends on it — for impact analysis, debugging, and trust. Use when tracing metric origins, assessing change impact, or diagnosing broken pipelines.","https:\u002F\u002Fgithub.com\u002Fitsual\u002Fagent-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fdata-analytics\u002Fdata-lineage\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":76},"01M729JV2ACQ310VG2KQ3267EN","data-governance","Establish data governance — ownership, policies, decision rights, and accountability — so data is trusted, compliant, and usable across the organization. Use when designing governance operating models, assigning data owners, or fixing chronic trust and access problems.","https:\u002F\u002Fgithub.com\u002Fitsual\u002Fagent-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fdata-analytics\u002Fdata-governance\u002FSKILL.md",[],[]]