[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70RNPC2APYJRN3GCNRR3SSZ":3,"skill-same:01M70RNPC2APYJRN3GCNRR3SSZ":71},{"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":23,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":70},"01M70RNPC2APYJRN3GCNRR3SSZ","banking-risk-compliance-referral-coordination",null,"Refer banks, regulators and boards onward and coordinate with other professionals and services.\nTRIGGERS - Use when a risk and compliance officer needs a referral & coordination for banks, regulators and boards in bank risk and compliance departments.","lionelsimai\u002Fclaude-skills-collection","lionelsimai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260158848?v=4","01M6CHZPS8G9TSB113TT0BBM6E","Lionel ","01M6CHZPXGW2SPE3BHQTGJ0S8J",38,"MIT","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fbanking-risk-compliance-referral-coordination\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"risk","referral","coordination","compliance","risk compliance","banking","banking risk compliance referral coordination","coordinate","for","compliance officer","triggers","use","when","with","services","bank","2026-11-10 10:12:30",false,"---\nname: banking-risk-compliance-referral-coordination\ndescription: |\n  Refer banks, regulators and boards onward and coordinate with other professionals and services.\n  TRIGGERS - Use when a risk and compliance officer needs a referral & coordination for banks, regulators and boards in bank risk and compliance departments.\ncategory: Banking Risk & Compliance\nlicense: MIT\nversion: 1.0\n---\n# Referral & Coordination — Banking Risk & Compliance\n\nRefer banks, regulators and boards onward and coordinate with other professionals and services. The deliverable is a referral pack and a coordination log with responses tracked.\nThis skill is written for a risk and compliance officer working with banks, regulators and boards in bank risk and compliance departments.\n\n## When to use\n- You are a risk and compliance officer preparing, delivering or reviewing this part of your work in bank risk and compliance departments.\n- You need a defensible, repeatable approach that produces a referral pack and a coordination log with responses tracked.\n- A colleague, auditor or client asks how this was done and what evidence supports it.\n\n## Key Concepts\n| Term | Meaning |\n|------|---------|\n| Risk register | the recorded list of risks, owners and controls |\n| Three lines | the model separating risk ownership, oversight and audit |\n| Conduct risk | the risk of harm to customers or markets from behaviour |\n\n## Workflow\n1. **Step 1** - Confirm the referral is appropriate: what banks, regulators and boards need that sits outside the risk and compliance officer scope in bank risk and compliance departments\n2. **Step 2** - Prepare the referral from risk registers — relevant history, current status, the specific question being asked\n3. **Step 3** - With consent, send the referral and log who received it and when; chase non-responses on a set schedule\n4. **Step 4** - Share incoming findings back into the main record so the plan and monitoring completion stay joined up\n5. **Step 5** - Close the loop with banks, regulators and boards: explain what happens next, who owns it, and what to do if things worsen — mindful of undetected misconduct\n\n## Profession-Specific Components\n| Component | Details for Banking Risk & Compliance |\n|-----------|-------------------------------|\n| Core documentation | risk registers; compliance monitoring plans; incident reports; regulatory returns |\n| Core tools & equipment | risk systems; monitoring tools; case management; reporting platforms |\n| People involved | banks, regulators and boards; the risk and compliance officer; colleagues and other services in bank risk and compliance departments |\n| Primary record | risk registers — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in bank risk and compliance departments] | **Objective:** [What this must achieve] | **Audience:** [banks, regulators and boards and other stakeholders]\n\nThe finished output is a referral pack and a coordination log with responses tracked, structured as:\n1. Summary of position and evidence\n2. Detail, following the workflow above\n3. Decisions, actions, owners and dates\n4. Review point and escalation route\n\n### Action Plan\n1. **Immediate:** Confirm scope, consent and the evidence available in risk registers.\n2. **Short-term:** Complete the workflow steps and record outcomes against monitoring completion.\n3. **Medium-term:** Review results, close actions, and update local procedures in bank risk and compliance departments.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| monitoring completion | Agree a local target and track the trend | Measured from risk registers and reviewed on a set cycle |\n| issue closure times | Agree a local target and track the trend | Measured from risk registers and reviewed on a set cycle |\n| regulatory findings | Agree a local target and track the trend | Measured from risk registers and reviewed on a set cycle |\n| training completion | Agree a local target and track the trend | Measured from risk registers and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: undetected misconduct.\n- Never let this happen: late regulatory returns.\n- Never let this happen: control failures.\n- Work only within the competence and authority of a risk and compliance officer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to bank risk and compliance departments's rules.\n- Verify names, dates, figures and measurements twice before anything is issued or signed off.\n- Use only real, verified information from the case in hand — never invent results, credentials or evidence.\n\n## Example (illustrative)\nA risk and compliance officer in bank risk and compliance departments applies this workflow for banks, regulators and boards: they open\nrisk registers, work through the five steps using risk systems, and close by recording\nthe outcome against monitoring completion and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Referral & Coordination — Banking Risk & Compliance\n\nRefer banks, regulators and boards onward and coordinate with other professionals and services. The deliverable is a referral pack and a coordination log with responses tracked.\nThis skill is written for a risk and compliance officer working with banks, regulators and boards in bank risk and compliance departments.\n\n## When to use\n- You are a risk and compliance officer preparing, delivering or reviewing this part of your work in bank risk and compliance departments.\n- You need a defensible, repeatable approach that produces a referral pack and a coordination log with responses tracked.\n- A colleague, auditor or client asks how this was done and what evidence supports it.\n\n## Key Concepts\n| Term | Meaning |\n|------|---------|\n| Risk register | the recorded list of risks, owners and controls |\n| Three lines | the model separating risk ownership, oversight and audit |\n| Conduct risk | the risk of harm to customers or markets from behaviour |\n\n## Workflow\n1. **Step 1** - Confirm the referral is appropriate: what banks, regulators and boards need that sits outside the risk and compliance officer scope in bank risk and compliance departments\n2. **Step 2** - Prepare the referral from risk registers — relevant history, current status, the specific question being asked\n3. **Step 3** - With consent, send the referral and log who received it and when; chase non-responses on a set schedule\n4. **Step 4** - Share incoming findings back into the main record so the plan and monitoring completion stay joined up\n5. **Step 5** - Close the loop with banks, regulators and boards: explain what happens next, who owns it, and what to do if things worsen — mindful of undetected misconduct\n\n## Profession-Specific Components\n| Component | Details for Banking Risk & Compliance |\n|-----------|-------------------------------|\n| Core documentation | risk registers; compliance monitoring plans; incident reports; regulatory returns |\n| Core tools & equipment | risk systems; monitoring tools; case management; reporting platforms |\n| People involved | banks, regulators and boards; the risk and compliance officer; colleagues and other services in bank risk and compliance departments |\n| Primary record | risk registers — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in bank risk and compliance departments] | **Objective:** [What this must achieve] | **Audience:** [banks, regulators and boards and other stakeholders]\n\nThe finished output is a referral pack and a coordination log with responses tracked, structured as:\n1. Summary of position and evidence\n2. Detail, following the workflow above\n3. Decisions, actions, owners and dates\n4. Review point and escalation route\n\n### Action Plan\n1. **Immediate:** Confirm scope, consent and the evidence available in risk registers.\n2. **Short-term:** Complete the workflow steps and record outcomes against monitoring completion.\n3. **Medium-term:** Review results, close actions, and update local procedures in bank risk and compliance departments.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| monitoring completion | Agree a local target and track the trend | Measured from risk registers and reviewed on a set cycle |\n| issue closure times | Agree a local target and track the trend | Measured from risk registers and reviewed on a set cycle |\n| regulatory findings | Agree a local target and track the trend | Measured from risk registers and reviewed on a set cycle |\n| training completion | Agree a local target and track the trend | Measured from risk registers and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: undetected misconduct.\n- Never let this happen: late regulatory returns.\n- Never let this happen: control failures.\n- Work only within the competence and authority of a risk and compliance officer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to bank risk and compliance departments's rules.\n- Verify names, dates, figures and measurements twice before anything is issued or signed off.\n- Use only real, verified information from the case in hand — never invent results, credentials or evidence.\n\n## Example (illustrative)\nA risk and compliance officer in bank risk and compliance departments applies this workflow for banks, regulators and boards: they open\nrisk registers, work through the five steps using risk systems, and close by recording\nthe outcome against monitoring completion and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n",{"name":5,"license":15,"version":45,"category":46,"description":47},1,"Banking Risk & Compliance","Refer banks, regulators and boards onward and coordinate with other professionals and services.\nTRIGGERS - Use when a risk and compliance officer needs a referral & coordination for banks, regulators and boards in bank risk and compliance departments.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fbanking-risk-compliance-referral-coordination",5,"https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection","https:\u002F\u002Fgithub.com\u002Flionelsimai","www.theaicapitol.com","Founder at The AI Capitol | I help founders turn AI into 10X revenue through systems, not tools. Ex-Apple • Ex-TikTok 👉 http:\u002F\u002Flionelsim.substack.com","2026-11-09 07:48:48",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill banking-risk-compliance-referral-coordination",{"tool":63,"command":64},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill banking-risk-compliance-referral-coordination",{"tool":66,"command":67},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill banking-risk-compliance-referral-coordination","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fbanking-risk-compliance-referral-coordination\u002FSKILL.md",true,[],[72,93,106,119,136,150],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":40},"01M71E7TB5HAR0K6EXB80YXBT7","youth-work-troubleshooting-guide","Diagnose and resolve common problems a youth worker meets in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a troubleshooting & problem solving for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-troubleshooting-guide\u002FSKILL.md",[],[79,80,81,82,83,84,32,85,86,87,36,88,35,89,34,90,91,92],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":40},"01M71E7R3YHK4RAQVCRPB4CTXN","youth-work-tools-equipment-checklist","Select, check and maintain the tools and equipment a youth worker relies on.\nTRIGGERS - Use when a youth worker needs a tools & equipment checklist for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-tools-equipment-checklist\u002FSKILL.md",[],[100,80,101,102,36,88,35,103,89,34,104,32,92,105,85,86],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":40},"01M71E7NX1BMFEFBH01KCRJDEP","youth-work-supplies-procurement","Specify, source and manage the supplies and materials used in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a supplies & procurement for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-supplies-procurement\u002FSKILL.md",[],[113,114,80,115,116,85,86,88,35,89,34,117,118,32,92,36],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":130,"publishedAt":40},"01M71E7JVFP6P96GAT2VT9JY0D","youth-work-stakeholder-presentation","Present youth worker findings and proposals to decision-makers and stakeholders.\nTRIGGERS - Use when a youth worker needs a stakeholder presentation for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-stakeholder-presentation\u002FSKILL.md",[125],{"categoryNo":126,"categoryName":127,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[131,80,132,133,32,134,92,34,135,85,86,36,88,35,89],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":142,"publishedAt":40},"01M71E7GE5VA1RG4XEM2GAZRFY","youth-work-session-delivery","Prepare for and deliver a professional session or appointment for young people and their communities in youth centres, schools and outreach settings.\nTRIGGERS - Use when a youth worker needs a session delivery guide for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-session-delivery\u002FSKILL.md",[],[143,144,145,80,146,86,83,147,85,36,88,35,89,34,32,148,149,92],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":159,"publishedAt":40},"01M71E7DQSMY2ZW1BF3A1Z0VJM","youth-work-service-plan","Design a realistic, measurable service plan for young people and their communities as a youth worker.\nTRIGGERS - Use when a youth worker needs a service plan design for young people and their communities in youth centres, schools and outreach settings.","https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fyouth-work-service-plan\u002FSKILL.md",[156],{"categoryNo":157,"categoryName":158,"taxonomyType":128,"taxonomyTypeDesc":129},"01JBSEEDCAT000000000000015","视觉设计",[80,160,161,162,32,34,89,163,164,92,86,85,88,35,36],"service","plan","youth work service plan","design","as"]