[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7171EE7DJ2K11FBTK6JTHKX":3,"skill-same:01M7171EE7DJ2K11FBTK6JTHKX":64},{"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":33,"linkOnly":34,"markdownContent":35,"markdownBody":36,"frontMatter":37,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7171EE7DJ2K11FBTK6JTHKX","payment-operations-scheduling-workload",null,"Plan schedules, caseloads and turnaround times for a payments operations specialist in payment operations centres.\nTRIGGERS - Use when a payments operations specialist needs a scheduling & workload management 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-scheduling-workload\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32],"payment","operations","workload","scheduling","payment operations scheduling workload","plan","for","specialist","payments","triggers","use","schedules","management","when","2026-11-10 10:12:30",false,"---\nname: payment-operations-scheduling-workload\ndescription: |\n  Plan schedules, caseloads and turnaround times for a payments operations specialist in payment operations centres.\n  TRIGGERS - Use when a payments operations specialist needs a scheduling & workload management for banks, fintechs and their customers in payment operations centres.\ncategory: Payment Operations\nlicense: MIT\nversion: 1.0\n---\n# Scheduling & Workload Management — Payment Operations\n\nPlan schedules, caseloads and turnaround times for a payments operations specialist in payment operations centres. The deliverable is a workable schedule template with priorities, buffers and escalation rules.\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 workable schedule template with priorities, buffers and escalation rules.\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** - Map demand: appointment or job types, durations, and the deadlines that drive straight-through processing rate\n2. **Step 2** - Build the schedule around fixed commitments in payment operations centres first, then fit flexible work around them\n3. **Step 3** - Protect buffer time for overruns, urgent cases and the admin behind payment queues — schedules without buffers fail by week two\n4. **Step 4** - Define triage rules so urgent work (for example anything involving failed payments harming customers) displaces routine work predictably\n5. **Step 5** - Review the schedule weekly against actuals and adjust booking rules, staffing or payment processing systems availability\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 workable schedule template with priorities, buffers and escalation rules, 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","# Scheduling & Workload Management — Payment Operations\n\nPlan schedules, caseloads and turnaround times for a payments operations specialist in payment operations centres. The deliverable is a workable schedule template with priorities, buffers and escalation rules.\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 workable schedule template with priorities, buffers and escalation rules.\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** - Map demand: appointment or job types, durations, and the deadlines that drive straight-through processing rate\n2. **Step 2** - Build the schedule around fixed commitments in payment operations centres first, then fit flexible work around them\n3. **Step 3** - Protect buffer time for overruns, urgent cases and the admin behind payment queues — schedules without buffers fail by week two\n4. **Step 4** - Define triage rules so urgent work (for example anything involving failed payments harming customers) displaces routine work predictably\n5. **Step 5** - Review the schedule weekly against actuals and adjust booking rules, staffing or payment processing systems availability\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 workable schedule template with priorities, buffers and escalation rules, 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":38,"category":39,"description":40},1,"Payment Operations","Plan schedules, caseloads and turnaround times for a payments operations specialist in payment operations centres.\nTRIGGERS - Use when a payments operations specialist needs a scheduling & workload management for banks, fintechs and their customers in payment operations centres.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fpayment-operations-scheduling-workload",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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-scheduling-workload",{"tool":56,"command":57},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-scheduling-workload",{"tool":59,"command":60},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-scheduling-workload","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fpayment-operations-scheduling-workload\u002FSKILL.md",true,[],[65,86,99,112,129,143],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":33},"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",[],[72,73,74,75,76,77,25,78,79,80,32,81,29,82,28,83,84,85],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"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":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":33},"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",[],[93,73,94,95,32,81,29,96,82,28,97,25,85,98,78,79],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":33},"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",[],[106,107,73,108,109,78,79,81,29,82,28,110,111,25,85,32],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":123,"publishedAt":33},"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",[118],{"categoryNo":119,"categoryName":120,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[124,73,125,126,25,127,85,28,128,78,79,32,81,29,82],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":33},"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",[],[136,137,138,73,139,79,76,140,78,32,81,29,82,28,25,141,142,85],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":33},"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",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":121,"taxonomyTypeDesc":122},"01JBSEEDCAT000000000000015","视觉设计",[73,153,24,154,25,28,82,155,156,85,79,78,81,29,32],"service","youth work service plan","design","as"]