[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71706SNX2MY2BH4ZWN9JS97":3,"skill-same:01M71706SNX2MY2BH4ZWN9JS97":67},{"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":36,"linkOnly":37,"markdownContent":38,"markdownBody":39,"frontMatter":40,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M71706SNX2MY2BH4ZWN9JS97","payment-operations-handover-briefing",null,"Hand over banks, fintechs and their customers or active work to another professional without losing critical detail.\nTRIGGERS - Use when a payments operations specialist needs a handover briefing for banks, fintechs and their customers in payment operations centres.","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\u002Fpayment-operations-handover-briefing\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35],"payment operations handover briefing","briefing","payment","operations","handover","specialist","active","work","hand","when","detail","critical","use","triggers","payments","for","professional","2026-11-10 10:12:30",false,"---\nname: payment-operations-handover-briefing\ndescription: |\n  Hand over banks, fintechs and their customers or active work to another professional without losing critical detail.\n  TRIGGERS - Use when a payments operations specialist needs a handover briefing for banks, fintechs and their customers in payment operations centres.\ncategory: Payment Operations\nlicense: MIT\nversion: 1.0\n---\n# Handover Briefing — Payment Operations\n\nHand over banks, fintechs and their customers or active work to another professional without losing critical detail. The deliverable is a structured handover brief covering status, risks and next actions.\nThis skill is written for a payments operations specialist working with banks, fintechs and their customers in payment operations centres.\n\n## When to use\n- You are a payments operations specialist preparing, delivering or reviewing this part of your work in payment operations centres.\n- You need a defensible, repeatable approach that produces a structured handover brief covering status, risks and next actions.\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| Straight-through processing | payments completed without manual intervention |\n| Exception | a payment needing manual review or repair |\n| Cut-off | the deadline for same-day payment processing |\n\n## Workflow\n1. **Step 1** - Summarise the current position from payment queues: what is done, what is in progress, what is waiting\n2. **Step 2** - Highlight live risks first — failed payments harming customers — and the controls or watchpoints already in place\n3. **Step 3** - State the next actions with owners and deadlines, and the results expected for straight-through processing rate\n4. **Step 4** - Walk the receiving professional through the brief, answer questions, and confirm understanding\n5. **Step 5** - Record that handover happened, who accepted it, and where the full record lives in payment operations centres\n\n## Profession-Specific Components\n| Component | Details for Payment Operations |\n|-----------|-------------------------------|\n| Core documentation | payment queues; exception reports; reconciliation files; incident logs |\n| Core tools & equipment | payment processing systems; screening tools; reconciliation software; case management |\n| People involved | banks, fintechs and their customers; the payments operations specialist; colleagues and other services in payment operations centres |\n| Primary record | payment queues — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in payment operations centres] | **Objective:** [What this must achieve] | **Audience:** [banks, fintechs and their customers and other stakeholders]\n\nThe finished output is a structured handover brief covering status, risks and next actions, 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 payment queues.\n2. **Short-term:** Complete the workflow steps and record outcomes against straight-through processing rate.\n3. **Medium-term:** Review results, close actions, and update local procedures in payment operations centres.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| straight-through processing rate | Agree a local target and track the trend | Measured from payment queues and reviewed on a set cycle |\n| exception resolution times | Agree a local target and track the trend | Measured from payment queues and reviewed on a set cycle |\n| error rates | Agree a local target and track the trend | Measured from payment queues and reviewed on a set cycle |\n| cut-off compliance | Agree a local target and track the trend | Measured from payment queues and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: failed payments harming customers.\n- Never let this happen: sanctions screening misses.\n- Never let this happen: fraud losses.\n- Work only within the competence and authority of a payments operations specialist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to payment operations centres'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 payments operations specialist in payment operations centres applies this workflow for banks, fintechs and their customers: they open\npayment queues, work through the five steps using payment processing systems, and close by recording\nthe outcome against straight-through processing rate and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Handover Briefing — Payment Operations\n\nHand over banks, fintechs and their customers or active work to another professional without losing critical detail. The deliverable is a structured handover brief covering status, risks and next actions.\nThis skill is written for a payments operations specialist working with banks, fintechs and their customers in payment operations centres.\n\n## When to use\n- You are a payments operations specialist preparing, delivering or reviewing this part of your work in payment operations centres.\n- You need a defensible, repeatable approach that produces a structured handover brief covering status, risks and next actions.\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| Straight-through processing | payments completed without manual intervention |\n| Exception | a payment needing manual review or repair |\n| Cut-off | the deadline for same-day payment processing |\n\n## Workflow\n1. **Step 1** - Summarise the current position from payment queues: what is done, what is in progress, what is waiting\n2. **Step 2** - Highlight live risks first — failed payments harming customers — and the controls or watchpoints already in place\n3. **Step 3** - State the next actions with owners and deadlines, and the results expected for straight-through processing rate\n4. **Step 4** - Walk the receiving professional through the brief, answer questions, and confirm understanding\n5. **Step 5** - Record that handover happened, who accepted it, and where the full record lives in payment operations centres\n\n## Profession-Specific Components\n| Component | Details for Payment Operations |\n|-----------|-------------------------------|\n| Core documentation | payment queues; exception reports; reconciliation files; incident logs |\n| Core tools & equipment | payment processing systems; screening tools; reconciliation software; case management |\n| People involved | banks, fintechs and their customers; the payments operations specialist; colleagues and other services in payment operations centres |\n| Primary record | payment queues — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in payment operations centres] | **Objective:** [What this must achieve] | **Audience:** [banks, fintechs and their customers and other stakeholders]\n\nThe finished output is a structured handover brief covering status, risks and next actions, 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 payment queues.\n2. **Short-term:** Complete the workflow steps and record outcomes against straight-through processing rate.\n3. **Medium-term:** Review results, close actions, and update local procedures in payment operations centres.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| straight-through processing rate | Agree a local target and track the trend | Measured from payment queues and reviewed on a set cycle |\n| exception resolution times | Agree a local target and track the trend | Measured from payment queues and reviewed on a set cycle |\n| error rates | Agree a local target and track the trend | Measured from payment queues and reviewed on a set cycle |\n| cut-off compliance | Agree a local target and track the trend | Measured from payment queues and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: failed payments harming customers.\n- Never let this happen: sanctions screening misses.\n- Never let this happen: fraud losses.\n- Work only within the competence and authority of a payments operations specialist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to payment operations centres'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 payments operations specialist in payment operations centres applies this workflow for banks, fintechs and their customers: they open\npayment queues, work through the five steps using payment processing systems, and close by recording\nthe outcome against straight-through processing rate 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":41,"category":42,"description":43},1,"Payment Operations","Hand over banks, fintechs and their customers or active work to another professional without losing critical detail.\nTRIGGERS - Use when a payments operations specialist needs a handover briefing for banks, fintechs and their customers in payment operations centres.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fpayment-operations-handover-briefing",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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-handover-briefing",{"tool":59,"command":60},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-handover-briefing",{"tool":62,"command":63},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-handover-briefing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fpayment-operations-handover-briefing\u002FSKILL.md",true,[],[68,88,101,114,131,144],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":36},"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",[],[75,26,76,77,78,79,34,80,81,82,28,83,31,84,32,85,86,87],"youth work troubleshooting guide","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":36},"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",[],[95,26,96,97,28,83,31,98,84,32,99,34,87,100,80,81],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":36},"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",[],[108,109,26,110,111,80,81,83,31,84,32,112,113,34,87,28],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":125,"publishedAt":36},"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",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[126,26,127,128,34,129,87,32,130,80,81,28,83,31,84],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":137,"publishedAt":36},"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",[],[138,139,140,26,141,81,78,142,80,28,83,31,84,32,34,35,143,87],"delivery","work session","session","youth work session delivery","prepare","deliver",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":153,"publishedAt":36},"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",[150],{"categoryNo":151,"categoryName":152,"taxonomyType":123,"taxonomyTypeDesc":124},"01JBSEEDCAT000000000000015","视觉设计",[26,154,155,156,34,32,84,157,158,87,81,80,83,31,28],"service","plan","youth work service plan","design","as"]