[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7128BFDY090DMY1GSQ004QC":3,"skill-same:01M7128BFDY090DMY1GSQ004QC":66},{"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":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":50,"updatedAt":51,"install":52,"resources":65},"01M7128BFDY090DMY1GSQ004QC","healthcare-administration-risk-assessment",null,"Identify, score and control the risks in work for patients, clinical teams and service managers in hospital and clinic administration offices.\nTRIGGERS - Use when a healthcare administrator needs a risk assessment for patients, clinical teams and service managers in hospital and clinic administration offices.","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\u002Fhealthcare-administration-risk-assessment\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"healthcare","risk","assessment","healthcare administration risk assessment","risk assessment","administration","for","triggers","teams","clinical","use","when","managers","work","control","service","2026-11-10 10:12:30",false,"---\nname: healthcare-administration-risk-assessment\ndescription: |\n  Identify, score and control the risks in work for patients, clinical teams and service managers in hospital and clinic administration offices.\n  TRIGGERS - Use when a healthcare administrator needs a risk assessment for patients, clinical teams and service managers in hospital and clinic administration offices.\ncategory: Healthcare Administration\nlicense: MIT\nversion: 1.0\n---\n# Risk Assessment — Healthcare Administration\n\nIdentify, score and control the risks in work for patients, clinical teams and service managers in hospital and clinic administration offices. The deliverable is a risk assessment with likelihood\u002Fimpact scores, controls and owners.\nThis skill is written for a healthcare administrator working with patients, clinical teams and service managers in hospital and clinic administration offices.\n\n## When to use\n- You are a healthcare administrator preparing, delivering or reviewing this part of your work in hospital and clinic administration offices.\n- You need a defensible, repeatable approach that produces a risk assessment with likelihood\u002Fimpact scores, controls and owners.\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| Waiting list | the record of patients awaiting an appointment or procedure |\n| Utilisation | how fully booked capacity is used |\n| Triage category | the priority assigned to a referral |\n\n## Workflow\n1. **Step 1** - Map the activity step by step and list what could go wrong at each stage for patients, clinical teams and service managers and staff\n2. **Step 2** - Score each risk for likelihood and impact, giving special weight to waiting list errors\n3. **Step 3** - For every high risk, define a control that removes, reduces or contains it, using patient administration systems where relevant\n4. **Step 4** - Record the assessment in clinic schedules, assign an owner to each control, and set a review date\n5. **Step 5** - Brief everyone involved before work starts; stop and reassess if conditions in hospital and clinic administration offices change\n\n## Profession-Specific Components\n| Component | Details for Healthcare Administration |\n|-----------|-------------------------------|\n| Core documentation | clinic schedules; waiting list records; referral logs; complaint files |\n| Core tools & equipment | patient administration systems; scheduling software; telephony systems; reporting dashboards |\n| People involved | patients, clinical teams and service managers; the healthcare administrator; colleagues and other services in hospital and clinic administration offices |\n| Primary record | clinic schedules — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in hospital and clinic administration offices] | **Objective:** [What this must achieve] | **Audience:** [patients, clinical teams and service managers and other stakeholders]\n\nThe finished output is a risk assessment with likelihood\u002Fimpact scores, controls and owners, 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 clinic schedules.\n2. **Short-term:** Complete the workflow steps and record outcomes against waiting list accuracy.\n3. **Medium-term:** Review results, close actions, and update local procedures in hospital and clinic administration offices.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| waiting list accuracy | Agree a local target and track the trend | Measured from clinic schedules and reviewed on a set cycle |\n| clinic utilisation | Agree a local target and track the trend | Measured from clinic schedules and reviewed on a set cycle |\n| referral processing times | Agree a local target and track the trend | Measured from clinic schedules and reviewed on a set cycle |\n| complaint response times | Agree a local target and track the trend | Measured from clinic schedules and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: waiting list errors.\n- Never let this happen: patient data breaches.\n- Never let this happen: clinic overbooking.\n- Work only within the competence and authority of a healthcare administrator; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to hospital and clinic administration offices'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 healthcare administrator in hospital and clinic administration offices applies this workflow for patients, clinical teams and service managers: they open\nclinic schedules, work through the five steps using patient administration systems, and close by recording\nthe outcome against waiting list accuracy and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Risk Assessment — Healthcare Administration\n\nIdentify, score and control the risks in work for patients, clinical teams and service managers in hospital and clinic administration offices. The deliverable is a risk assessment with likelihood\u002Fimpact scores, controls and owners.\nThis skill is written for a healthcare administrator working with patients, clinical teams and service managers in hospital and clinic administration offices.\n\n## When to use\n- You are a healthcare administrator preparing, delivering or reviewing this part of your work in hospital and clinic administration offices.\n- You need a defensible, repeatable approach that produces a risk assessment with likelihood\u002Fimpact scores, controls and owners.\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| Waiting list | the record of patients awaiting an appointment or procedure |\n| Utilisation | how fully booked capacity is used |\n| Triage category | the priority assigned to a referral |\n\n## Workflow\n1. **Step 1** - Map the activity step by step and list what could go wrong at each stage for patients, clinical teams and service managers and staff\n2. **Step 2** - Score each risk for likelihood and impact, giving special weight to waiting list errors\n3. **Step 3** - For every high risk, define a control that removes, reduces or contains it, using patient administration systems where relevant\n4. **Step 4** - Record the assessment in clinic schedules, assign an owner to each control, and set a review date\n5. **Step 5** - Brief everyone involved before work starts; stop and reassess if conditions in hospital and clinic administration offices change\n\n## Profession-Specific Components\n| Component | Details for Healthcare Administration |\n|-----------|-------------------------------|\n| Core documentation | clinic schedules; waiting list records; referral logs; complaint files |\n| Core tools & equipment | patient administration systems; scheduling software; telephony systems; reporting dashboards |\n| People involved | patients, clinical teams and service managers; the healthcare administrator; colleagues and other services in hospital and clinic administration offices |\n| Primary record | clinic schedules — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in hospital and clinic administration offices] | **Objective:** [What this must achieve] | **Audience:** [patients, clinical teams and service managers and other stakeholders]\n\nThe finished output is a risk assessment with likelihood\u002Fimpact scores, controls and owners, 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 clinic schedules.\n2. **Short-term:** Complete the workflow steps and record outcomes against waiting list accuracy.\n3. **Medium-term:** Review results, close actions, and update local procedures in hospital and clinic administration offices.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| waiting list accuracy | Agree a local target and track the trend | Measured from clinic schedules and reviewed on a set cycle |\n| clinic utilisation | Agree a local target and track the trend | Measured from clinic schedules and reviewed on a set cycle |\n| referral processing times | Agree a local target and track the trend | Measured from clinic schedules and reviewed on a set cycle |\n| complaint response times | Agree a local target and track the trend | Measured from clinic schedules and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: waiting list errors.\n- Never let this happen: patient data breaches.\n- Never let this happen: clinic overbooking.\n- Work only within the competence and authority of a healthcare administrator; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to hospital and clinic administration offices'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 healthcare administrator in hospital and clinic administration offices applies this workflow for patients, clinical teams and service managers: they open\nclinic schedules, work through the five steps using patient administration systems, and close by recording\nthe outcome against waiting list accuracy 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":40,"category":41,"description":42},1,"Healthcare Administration","Identify, score and control the risks in work for patients, clinical teams and service managers in hospital and clinic administration offices.\nTRIGGERS - Use when a healthcare administrator needs a risk assessment for patients, clinical teams and service managers in hospital and clinic administration offices.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fhealthcare-administration-risk-assessment",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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill healthcare-administration-risk-assessment",{"tool":58,"command":59},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill healthcare-administration-risk-assessment",{"tool":61,"command":62},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill healthcare-administration-risk-assessment","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fhealthcare-administration-risk-assessment\u002FSKILL.md",true,[],[67,87,100,113,130,144],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":35},"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",[],[74,32,75,76,77,78,25,79,80,81,30,82,29,83,26,84,85,86],"youth work troubleshooting guide","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":35},"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",[],[94,32,95,96,30,82,29,97,83,26,98,25,86,99,79,80],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":35},"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",[],[107,108,32,109,110,79,80,82,29,83,26,111,112,25,86,30],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":124,"publishedAt":35},"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",[119],{"categoryNo":120,"categoryName":121,"taxonomyType":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[125,32,126,127,25,128,86,26,129,79,80,30,82,29,83],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":35},"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",[],[137,138,139,32,140,80,77,141,79,30,82,29,83,26,25,142,143,86],"delivery","work session","session","youth work session delivery","prepare","professional","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":35},"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":122,"taxonomyTypeDesc":123},"01JBSEEDCAT000000000000015","视觉设计",[32,34,154,155,25,26,83,156,157,86,80,79,82,29,30],"plan","youth work service plan","design","as"]