[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F6864HVB5KCXN6J2ER7EYR":3,"skill-same:01M7F6864HVB5KCXN6J2ER7EYR":63},{"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":43,"commitSha":44,"skillDirectory":45,"forksCount":14,"repositoryHtmlUrl":46,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7F6864HVB5KCXN6J2ER7EYR","analyzing-ai-in-financial-services",null,"Evaluates AI\u002FML applications in financial services with model governance, bias assessment, and regulatory considerations. Use when analyzing AI in finance, evaluating ML models, or assessing AI governance.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fanalyzing-ai-in-financial-services\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: analyzing-ai-in-financial-services\nlanguage: en\ndescription: Evaluates AI\u002FML applications in financial services with model governance, bias assessment, and regulatory considerations. Use when analyzing AI in finance, evaluating ML models, or assessing AI governance.\ntags:\n  - analysis\n  - financial-technology\n  - regulatory\nmetadata:\n  author: casemark\n  practice_areas:\n    - Fintech\n    - Payments\n    - Digital Banking\n  document_types:\n    - Analysis Report\n  skill_modes:\n    - Analysis\nsource: \"https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills\"\nsource_repository: \"CaseMark\u002Fskills\"\nsource_path: \"skills\u002Ffinance\u002Fanalyzing-ai-in-financial-services\u002FSKILL.md\"\nlicense: \"Apache-2.0\"\nimported_at: \"2026-09-20\"\n---\n# Analyzing AI In Financial Services\n\n## When To Use\n\n- Evaluating an AI\u002FML model deployed or proposed for credit decisioning, fraud detection, AML\u002FKYC, trading, or customer-facing automation\n- Assessing model risk management (MRM) posture against SR 11-7, OCC 2011-12, or equivalent guidance [VERIFY jurisdiction-specific MRM guidance]\n- Reviewing algorithmic bias and fair-lending implications for underwriting or pricing models\n- Analyzing vendor-supplied AI tools (e.g., BaaS scoring engines, conversational AI for digital banking)\n- Preparing for regulatory examination or audit of AI\u002FML systems in a financial institution\n\n## Inputs To Gather\n\n- **Model documentation**: model cards, technical specifications, training data descriptions, feature lists\n- **Performance metrics**: accuracy, precision\u002Frecall, AUC-ROC, stability metrics (PSI), back-testing results\n- **Governance artifacts**: model inventory entry, validation reports, change-management logs, approval records\n- **Bias\u002Ffairness data**: disparate impact ratios across protected classes, HMDA or ECOA-relevant statistics [VERIFY applicable fair-lending statutes by jurisdiction]\n- **Regulatory context**: institution charter type (bank, credit union, non-bank lender), applicable supervisory framework, any open MRAs or consent orders\n- **Use-case scope**: specific business function the AI serves (e.g., real-time fraud scoring, deposit pricing, chatbot servicing)\n\n## Workflow\n\n1. **Define scope and materiality**\n   - Classify the model by risk tier (critical, high, medium, low) based on financial exposure, customer impact, and regulatory sensitivity\n   - Confirm whether the model is first-party built, vendor-supplied, or open-source derived — governance expectations differ for each\n\n2. **Assess model governance framework**\n   - Map the institution's MRM program against SR 11-7 three-lines-of-defense structure [VERIFY if institution falls under OCC, Fed, or state regulator]\n   - Check for documented model owner, independent validation function, and escalation procedures\n   - Verify model inventory completeness — flag any shadow models or undocumented deployments\n\n3. **Evaluate technical soundness**\n   - Review feature selection for proxies of protected characteristics (e.g., zip code as race proxy in credit models)\n   - Examine training data vintage, representativeness, and label quality\n   - Assess explainability: can adverse-action reasons be generated per ECOA\u002FReg B requirements? [VERIFY if adverse-action notice obligations apply]\n   - Check for concept drift monitoring and automated retraining triggers\n\n4. **Conduct bias and fairness analysis**\n   - Calculate disparate impact ratios for lending\u002Fpricing models across race, sex, age, and other protected classes\n   - Apply appropriate fairness metrics (demographic parity, equalized odds, predictive parity) based on use case\n   - Identify whether pre-processing, in-processing, or post-processing debiasing techniques are employed\n   - Flag any model where disparate impact exceeds the four-fifths threshold without documented business justification\n\n5. **Map regulatory and compliance exposure**\n   - Cross-reference against CFPB guidance on automated decisioning and adverse-action notices\n   - For payment\u002Fdigital-banking AI, evaluate PCI-DSS data handling, BSA\u002FAML transaction-monitoring adequacy [VERIFY PCI scope for specific deployment]\n   - Assess third-party risk management (TPRM) obligations if model is vendor-supplied (OCC 2013-29 \u002F updated interagency guidance)\n   - Note any state-specific AI laws (e.g., Colorado AI Act, NYC Local Law 144 for automated employment decisions) [VERIFY state\u002Flocal AI legislation applicability]\n\n6. **Synthesize findings and risk-rate**\n   - Assign overall risk rating with supporting rationale\n   - Prioritize findings by severity: critical (immediate remediation), high (next exam cycle), moderate (roadmap), low (enhancement)\n   - Identify compensating controls that mitigate identified gaps\n\n## Output\n\nProduce an **AI\u002FML Model Analysis Report** containing:\n\n- **Executive summary**: model name, use case, risk tier, overall assessment (acceptable \u002F acceptable with conditions \u002F unacceptable)\n- **Governance assessment**: MRM program maturity, validation independence, inventory accuracy\n- **Technical evaluation**: model performance, explainability, drift monitoring, data quality\n- **Bias and fairness findings**: disparate impact results, fairness metrics, debiasing controls\n- **Regulatory exposure map**: applicable regulations, compliance gaps, pending enforcement trends\n- **Remediation roadmap**: prioritized findings with owners, timelines, and success criteria\n- **Appendices**: data tables, metric calculations, regulatory cross-reference matrix\n\n## Quality Checks\n\n- Every finding cites a specific regulatory provision, guidance document, or industry standard (SR 11-7, ECOA, CFPB circulars)\n- Disparate impact calculations include methodology notes and confidence intervals\n- Vendor-supplied models are assessed under both MRM and TPRM frameworks — do not evaluate under only one\n- All jurisdiction-dependent conclusions are tagged with [VERIFY] for reviewer confirmation\n- Adverse-action explainability is tested with sample outputs, not just documented as \"supported\"\n- Report distinguishes between model risk (technical) and compliance risk (regulatory) — do not conflate the two\n","# Analyzing AI In Financial Services\n\n## When To Use\n\n- Evaluating an AI\u002FML model deployed or proposed for credit decisioning, fraud detection, AML\u002FKYC, trading, or customer-facing automation\n- Assessing model risk management (MRM) posture against SR 11-7, OCC 2011-12, or equivalent guidance [VERIFY jurisdiction-specific MRM guidance]\n- Reviewing algorithmic bias and fair-lending implications for underwriting or pricing models\n- Analyzing vendor-supplied AI tools (e.g., BaaS scoring engines, conversational AI for digital banking)\n- Preparing for regulatory examination or audit of AI\u002FML systems in a financial institution\n\n## Inputs To Gather\n\n- **Model documentation**: model cards, technical specifications, training data descriptions, feature lists\n- **Performance metrics**: accuracy, precision\u002Frecall, AUC-ROC, stability metrics (PSI), back-testing results\n- **Governance artifacts**: model inventory entry, validation reports, change-management logs, approval records\n- **Bias\u002Ffairness data**: disparate impact ratios across protected classes, HMDA or ECOA-relevant statistics [VERIFY applicable fair-lending statutes by jurisdiction]\n- **Regulatory context**: institution charter type (bank, credit union, non-bank lender), applicable supervisory framework, any open MRAs or consent orders\n- **Use-case scope**: specific business function the AI serves (e.g., real-time fraud scoring, deposit pricing, chatbot servicing)\n\n## Workflow\n\n1. **Define scope and materiality**\n   - Classify the model by risk tier (critical, high, medium, low) based on financial exposure, customer impact, and regulatory sensitivity\n   - Confirm whether the model is first-party built, vendor-supplied, or open-source derived — governance expectations differ for each\n\n2. **Assess model governance framework**\n   - Map the institution's MRM program against SR 11-7 three-lines-of-defense structure [VERIFY if institution falls under OCC, Fed, or state regulator]\n   - Check for documented model owner, independent validation function, and escalation procedures\n   - Verify model inventory completeness — flag any shadow models or undocumented deployments\n\n3. **Evaluate technical soundness**\n   - Review feature selection for proxies of protected characteristics (e.g., zip code as race proxy in credit models)\n   - Examine training data vintage, representativeness, and label quality\n   - Assess explainability: can adverse-action reasons be generated per ECOA\u002FReg B requirements? [VERIFY if adverse-action notice obligations apply]\n   - Check for concept drift monitoring and automated retraining triggers\n\n4. **Conduct bias and fairness analysis**\n   - Calculate disparate impact ratios for lending\u002Fpricing models across race, sex, age, and other protected classes\n   - Apply appropriate fairness metrics (demographic parity, equalized odds, predictive parity) based on use case\n   - Identify whether pre-processing, in-processing, or post-processing debiasing techniques are employed\n   - Flag any model where disparate impact exceeds the four-fifths threshold without documented business justification\n\n5. **Map regulatory and compliance exposure**\n   - Cross-reference against CFPB guidance on automated decisioning and adverse-action notices\n   - For payment\u002Fdigital-banking AI, evaluate PCI-DSS data handling, BSA\u002FAML transaction-monitoring adequacy [VERIFY PCI scope for specific deployment]\n   - Assess third-party risk management (TPRM) obligations if model is vendor-supplied (OCC 2013-29 \u002F updated interagency guidance)\n   - Note any state-specific AI laws (e.g., Colorado AI Act, NYC Local Law 144 for automated employment decisions) [VERIFY state\u002Flocal AI legislation applicability]\n\n6. **Synthesize findings and risk-rate**\n   - Assign overall risk rating with supporting rationale\n   - Prioritize findings by severity: critical (immediate remediation), high (next exam cycle), moderate (roadmap), low (enhancement)\n   - Identify compensating controls that mitigate identified gaps\n\n## Output\n\nProduce an **AI\u002FML Model Analysis Report** containing:\n\n- **Executive summary**: model name, use case, risk tier, overall assessment (acceptable \u002F acceptable with conditions \u002F unacceptable)\n- **Governance assessment**: MRM program maturity, validation independence, inventory accuracy\n- **Technical evaluation**: model performance, explainability, drift monitoring, data quality\n- **Bias and fairness findings**: disparate impact results, fairness metrics, debiasing controls\n- **Regulatory exposure map**: applicable regulations, compliance gaps, pending enforcement trends\n- **Remediation roadmap**: prioritized findings with owners, timelines, and success criteria\n- **Appendices**: data tables, metric calculations, regulatory cross-reference matrix\n\n## Quality Checks\n\n- Every finding cites a specific regulatory provision, guidance document, or industry standard (SR 11-7, ECOA, CFPB circulars)\n- Disparate impact calculations include methodology notes and confidence intervals\n- Vendor-supplied models are assessed under both MRM and TPRM frameworks — do not evaluate under only one\n- All jurisdiction-dependent conclusions are tagged with [VERIFY] for reviewer confirmation\n- Adverse-action explainability is tested with sample outputs, not just documented as \"supported\"\n- Report distinguishes between model risk (technical) and compliance risk (regulatory) — do not conflate the two\n",{"name":5,"tags":24,"source":28,"license":15,"language":29,"metadata":30,"description":7,"imported_at":40,"source_path":41,"source_repository":42},[25,26,27],"analysis","financial-technology","regulatory","https:\u002F\u002Fgithub.com\u002FCaseMark\u002Fskills","en",{"author":31,"skill_modes":32,"document_types":34,"practice_areas":36},"casemark",[33],"Analysis",[35],"Analysis Report",[37,38,39],"Fintech","Payments","Digital Banking","2026-09-20","skills\u002Ffinance\u002Fanalyzing-ai-in-financial-services\u002FSKILL.md","CaseMark\u002Fskills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Ffinance\u002Fanalyzing-ai-in-financial-services","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill analyzing-ai-in-financial-services",{"tool":55,"command":56},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill analyzing-ai-in-financial-services",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill analyzing-ai-in-financial-services","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Ffinance\u002Fanalyzing-ai-in-financial-services\u002FSKILL.md",true,[],[64,72,79,86,93,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":68,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]