[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70RNKBWBYT2W7ZHRWHPH3DA":3,"skill-same:01M70RNKBWBYT2W7ZHRWHPH3DA":72},{"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":41,"linkOnly":42,"markdownContent":43,"markdownBody":44,"frontMatter":45,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":56,"updatedAt":57,"install":58,"resources":71},"01M70RNKBWBYT2W7ZHRWHPH3DA","banking-risk-compliance-records-documentation",null,"Create and maintain accurate, auditable records for work with banks, regulators and boards.\nTRIGGERS - Use when a risk and compliance officer needs a records & documentation 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-records-documentation\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,40],"records","documentation","compliance","risk compliance","banking","banking risk compliance records documentation","risk","bank","work","create","with","when","use","maintain","triggers","compliance officer","for","2026-11-10 10:12:30",false,"---\nname: banking-risk-compliance-records-documentation\ndescription: |\n  Create and maintain accurate, auditable records for work with banks, regulators and boards.\n  TRIGGERS - Use when a risk and compliance officer needs a records & documentation for banks, regulators and boards in bank risk and compliance departments.\ncategory: Banking Risk & Compliance\nlicense: MIT\nversion: 1.0\n---\n# Records & Documentation — Banking Risk & Compliance\n\nCreate and maintain accurate, auditable records for work with banks, regulators and boards. The deliverable is a documentation standard, templates and a completed record set.\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 documentation standard, templates and a completed record set.\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** - Use risk registers as the single source of truth; record facts, observations and decisions — not speculation\n2. **Step 2** - Write entries contemporaneously where possible, dated and attributable, in the format bank risk and compliance departments requires\n3. **Step 3** - Record measurements and outcomes that feed monitoring completion exactly as observed, with units and method noted\n4. **Step 4** - Store and share records under the confidentiality and retention rules that apply in bank risk and compliance departments, guarding against undetected misconduct\n5. **Step 5** - Audit a sample of records monthly for completeness and correct anything missing while the work is still current\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 documentation standard, templates and a completed record set, 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","# Records & Documentation — Banking Risk & Compliance\n\nCreate and maintain accurate, auditable records for work with banks, regulators and boards. The deliverable is a documentation standard, templates and a completed record set.\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 documentation standard, templates and a completed record set.\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** - Use risk registers as the single source of truth; record facts, observations and decisions — not speculation\n2. **Step 2** - Write entries contemporaneously where possible, dated and attributable, in the format bank risk and compliance departments requires\n3. **Step 3** - Record measurements and outcomes that feed monitoring completion exactly as observed, with units and method noted\n4. **Step 4** - Store and share records under the confidentiality and retention rules that apply in bank risk and compliance departments, guarding against undetected misconduct\n5. **Step 5** - Audit a sample of records monthly for completeness and correct anything missing while the work is still current\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 documentation standard, templates and a completed record set, 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":46,"category":47,"description":48},1,"Banking Risk & Compliance","Create and maintain accurate, auditable records for work with banks, regulators and boards.\nTRIGGERS - Use when a risk and compliance officer needs a records & documentation for banks, regulators and boards in bank risk and compliance departments.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fbanking-risk-compliance-records-documentation",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":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill banking-risk-compliance-records-documentation",{"tool":64,"command":65},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill banking-risk-compliance-records-documentation",{"tool":67,"command":68},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill banking-risk-compliance-records-documentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fbanking-risk-compliance-records-documentation\u002FSKILL.md",true,[],[73,93,105,118,135,149],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":41},"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",[],[80,32,81,82,83,84,40,85,86,87,35,88,36,89,38,90,91,92],"youth work troubleshooting guide","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":41},"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,32,101,102,35,88,36,37,89,38,103,40,92,104,85,86],"youth work tools equipment checklist","checklist","Tools","select","check",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":41},"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",[],[112,113,32,114,115,85,86,88,36,89,38,116,117,40,92,35],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":129,"publishedAt":41},"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",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[130,32,131,132,40,133,92,38,134,85,86,35,88,36,89],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":41},"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",[],[142,143,144,32,145,86,83,146,85,35,88,36,89,38,40,147,148,92],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":41},"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",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000015","视觉设计",[32,159,160,161,40,38,89,162,163,92,86,85,88,36,35],"service","plan","youth work service plan","design","as"]