[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7171BDK6D0F72ECJD6C31CV":3,"skill-same:01M7171BDK6D0F72ECJD6C31CV":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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M7171BDK6D0F72ECJD6C31CV","payment-operations-safety-protocol",null,"Work safely in payment operations centres: a practical safety protocol for a payments operations specialist and banks, fintechs and their customers.\nTRIGGERS - Use when a payments operations specialist needs a safety protocol 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-safety-protocol\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"payment","operations","protocol","Safety","payment operations safety protocol","practical","work","for","specialist","payments","triggers","use","when","2026-11-10 10:12:30",false,"---\nname: payment-operations-safety-protocol\ndescription: |\n  Work safely in payment operations centres: a practical safety protocol for a payments operations specialist and banks, fintechs and their customers.\n  TRIGGERS - Use when a payments operations specialist needs a safety protocol for banks, fintechs and their customers in payment operations centres.\ncategory: Payment Operations\nlicense: MIT\nversion: 1.0\n---\n# Safety Protocol — Payment Operations\n\nWork safely in payment operations centres: a practical safety protocol for a payments operations specialist and banks, fintechs and their customers. The deliverable is a written safety protocol with checks, responsibilities and emergency 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 written safety protocol with checks, responsibilities and emergency 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** - Identify the hazards present in payment operations centres for staff, banks, fintechs and their customers and visitors, starting with failed payments harming customers\n2. **Step 2** - Write controls in order: eliminate, substitute, engineer, administrate, then protective equipment such as payment processing systems\n3. **Step 3** - Set pre-start checks and stop-work authority — anyone can halt work that looks unsafe, without penalty\n4. **Step 4** - Define what happens when something goes wrong: first response, escalation, recording in payment queues\n5. **Step 5** - Review the protocol after every incident and at least annually; brief and re-brief everyone it covers\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 written safety protocol with checks, responsibilities and emergency 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","# Safety Protocol — Payment Operations\n\nWork safely in payment operations centres: a practical safety protocol for a payments operations specialist and banks, fintechs and their customers. The deliverable is a written safety protocol with checks, responsibilities and emergency 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 written safety protocol with checks, responsibilities and emergency 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** - Identify the hazards present in payment operations centres for staff, banks, fintechs and their customers and visitors, starting with failed payments harming customers\n2. **Step 2** - Write controls in order: eliminate, substitute, engineer, administrate, then protective equipment such as payment processing systems\n3. **Step 3** - Set pre-start checks and stop-work authority — anyone can halt work that looks unsafe, without penalty\n4. **Step 4** - Define what happens when something goes wrong: first response, escalation, recording in payment queues\n5. **Step 5** - Review the protocol after every incident and at least annually; brief and re-brief everyone it covers\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 written safety protocol with checks, responsibilities and emergency 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":37,"category":38,"description":39},1,"Payment Operations","Work safely in payment operations centres: a practical safety protocol for a payments operations specialist and banks, fintechs and their customers.\nTRIGGERS - Use when a payments operations specialist needs a safety protocol for banks, fintechs and their customers in payment operations centres.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fpayment-operations-safety-protocol",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-safety-protocol",{"tool":55,"command":56},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-safety-protocol",{"tool":58,"command":59},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-safety-protocol","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fpayment-operations-safety-protocol\u002FSKILL.md",true,[],[64,84,97,110,127,141],{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":32},"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",[],[71,25,72,73,74,75,26,76,77,78,31,79,30,80,29,81,82,83],"youth work troubleshooting guide","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"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":32},"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",[],[91,25,92,93,31,79,30,94,80,29,95,26,83,96,76,77],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":32},"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",[],[104,105,25,106,107,76,77,79,30,80,29,108,109,26,83,31],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":121,"publishedAt":32},"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",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[122,25,123,124,26,125,83,29,126,76,77,31,79,30,80],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":32},"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",[],[134,135,136,25,137,77,74,138,76,31,79,30,80,29,26,139,140,83],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":32},"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",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000015","视觉设计",[25,151,152,153,26,29,80,154,155,83,77,76,79,30,31],"service","plan","youth work service plan","design","as"]