[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M716Z8KD2P9T2MJN2DP3J8YP":3,"skill-same:01M716Z8KD2P9T2MJN2DP3J8YP":69},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M716Z8KD2P9T2MJN2DP3J8YP","payment-operations-assessment-report",null,"Assess banks, fintechs and their customers and write a defensible findings report as a payments operations specialist.\nTRIGGERS - Use when a payments operations specialist needs a assessment & findings report 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-assessment-report\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37],"payment operations assessment report","assessment","payment","operations","report","as","for","payments","triggers","assess","use","when","specialist","write","2026-11-10 10:12:30",false,"---\nname: payment-operations-assessment-report\ndescription: |\n  Assess banks, fintechs and their customers and write a defensible findings report as a payments operations specialist.\n  TRIGGERS - Use when a payments operations specialist needs a assessment & findings report for banks, fintechs and their customers in payment operations centres.\ncategory: Payment Operations\nlicense: MIT\nversion: 1.0\n---\n# Assessment & Findings Report — Payment Operations\n\nAssess banks, fintechs and their customers and write a defensible findings report as a payments operations specialist. The deliverable is a structured assessment report with findings, evidence and recommendations.\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 assessment report with findings, evidence and recommendations.\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** - Review the intake record and payment queues so the assessment builds on verified information, not assumptions\n2. **Step 2** - Carry out the assessment using payment processing systems, following the recognised method for payment operations centres\n3. **Step 3** - Compare findings against the benchmarks behind straight-through processing rate and note where evidence is strong, weak or missing\n4. **Step 4** - Draft the report: findings first, then interpretation, then recommendations in priority order\n5. **Step 5** - Check the draft for accuracy and for failed payments harming customers; have it reviewed where the profession's standards require a second sign-off\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 assessment report with findings, evidence and recommendations, 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","# Assessment & Findings Report — Payment Operations\n\nAssess banks, fintechs and their customers and write a defensible findings report as a payments operations specialist. The deliverable is a structured assessment report with findings, evidence and recommendations.\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 assessment report with findings, evidence and recommendations.\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** - Review the intake record and payment queues so the assessment builds on verified information, not assumptions\n2. **Step 2** - Carry out the assessment using payment processing systems, following the recognised method for payment operations centres\n3. **Step 3** - Compare findings against the benchmarks behind straight-through processing rate and note where evidence is strong, weak or missing\n4. **Step 4** - Draft the report: findings first, then interpretation, then recommendations in priority order\n5. **Step 5** - Check the draft for accuracy and for failed payments harming customers; have it reviewed where the profession's standards require a second sign-off\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 assessment report with findings, evidence and recommendations, 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":43,"category":44,"description":45},1,"Payment Operations","Assess banks, fintechs and their customers and write a defensible findings report as a payments operations specialist.\nTRIGGERS - Use when a payments operations specialist needs a assessment & findings report for banks, fintechs and their customers in payment operations centres.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fpayment-operations-assessment-report",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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-assessment-report",{"tool":61,"command":62},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-assessment-report",{"tool":64,"command":65},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill payment-operations-assessment-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fpayment-operations-assessment-report\u002FSKILL.md",true,[],[70,91,104,117,134,148],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":38},"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",[],[77,78,79,80,81,82,30,83,84,85,35,86,34,87,32,88,89,90],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":38},"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",[],[98,78,99,100,35,86,34,101,87,32,102,30,90,103,83,84],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":38},"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",[],[111,112,78,113,114,83,84,86,34,87,32,115,116,30,90,35],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":128,"publishedAt":38},"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",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[129,78,130,131,30,132,90,32,133,83,84,35,86,34,87],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":38},"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",[],[141,142,143,78,144,84,81,145,83,35,86,34,87,32,30,146,147,90],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":38},"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",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000015","视觉设计",[78,158,159,160,30,32,87,161,29,90,84,83,86,34,35],"service","plan","youth work service plan","design"]