[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70RY3EBPQA1BFSMF9J8VRY2":3,"skill-same:01M70RY3EBPQA1BFSMF9J8VRY2":70},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M70RY3EBPQA1BFSMF9J8VRY2","biomedical-engineering-stakeholder-presentation",null,"Present biomedical engineer findings and proposals to decision-makers and stakeholders.\nTRIGGERS - Use when a biomedical engineer needs a stakeholder presentation for hospitals, device manufacturers and patients in hospital engineering departments and laboratories.","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\u002Fbiomedical-engineering-stakeholder-presentation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"biomedical","engineering","biomedical engineering stakeholder presentation","presentation","biomedical engineering","proposals","for","engineer","decision","triggers","use","biomedical engineer","when","present","device","2026-11-10 10:12:30",false,"---\nname: biomedical-engineering-stakeholder-presentation\ndescription: |\n  Present biomedical engineer findings and proposals to decision-makers and stakeholders.\n  TRIGGERS - Use when a biomedical engineer needs a stakeholder presentation for hospitals, device manufacturers and patients in hospital engineering departments and laboratories.\ncategory: Biomedical Engineering\nlicense: MIT\nversion: 1.0\n---\n# Stakeholder Presentation — Biomedical Engineering\n\nPresent biomedical engineer findings and proposals to decision-makers and stakeholders. The deliverable is a presentation structure with evidence summary and decision asks.\nThis skill is written for a biomedical engineer working with hospitals, device manufacturers and patients in hospital engineering departments and laboratories.\n\n## When to use\n- You are a biomedical engineer preparing, delivering or reviewing this part of your work in hospital engineering departments and laboratories.\n- You need a defensible, repeatable approach that produces a presentation structure with evidence summary and decision asks.\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| Calibration | adjusting a device to measure or perform accurately |\n| Asset register | the inventory of medical devices and their status |\n| Adverse incident | an event where a device may have caused harm |\n\n## Workflow\n1. **Step 1** - Open with the decision or conclusion, then the evidence — busy stakeholders should not wait for the point\n2. **Step 2** - Support claims with data from device evaluations and movement in device uptime, with sources and limits stated\n3. **Step 3** - Address the hard parts directly, including device failures harming patients and what it would take to reduce it\n4. **Step 4** - Make the ask specific: what decision, by when, with what resources for work in hospital engineering departments and laboratories\n5. **Step 5** - Follow up in writing the same day: decisions made, actions agreed, owners and dates\n\n## Profession-Specific Components\n| Component | Details for Biomedical Engineering |\n|-----------|-------------------------------|\n| Core documentation | device evaluations; maintenance records; incident investigations; specifications |\n| Core tools & equipment | test equipment; asset management systems; design software; calibration tools |\n| People involved | hospitals, device manufacturers and patients; the biomedical engineer; colleagues and other services in hospital engineering departments and laboratories |\n| Primary record | device evaluations — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in hospital engineering departments and laboratories] | **Objective:** [What this must achieve] | **Audience:** [hospitals, device manufacturers and patients and other stakeholders]\n\nThe finished output is a presentation structure with evidence summary and decision asks, 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 device evaluations.\n2. **Short-term:** Complete the workflow steps and record outcomes against device uptime.\n3. **Medium-term:** Review results, close actions, and update local procedures in hospital engineering departments and laboratories.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| device uptime | Agree a local target and track the trend | Measured from device evaluations and reviewed on a set cycle |\n| maintenance completion | Agree a local target and track the trend | Measured from device evaluations and reviewed on a set cycle |\n| incident rates | Agree a local target and track the trend | Measured from device evaluations and reviewed on a set cycle |\n| evaluation turnaround | Agree a local target and track the trend | Measured from device evaluations and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: device failures harming patients.\n- Never let this happen: maintenance backlogs.\n- Never let this happen: unapproved modifications.\n- Work only within the competence and authority of a biomedical engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to hospital engineering departments and laboratories'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 biomedical engineer in hospital engineering departments and laboratories applies this workflow for hospitals, device manufacturers and patients: they open\ndevice evaluations, work through the five steps using test equipment, and close by recording\nthe outcome against device uptime and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Stakeholder Presentation — Biomedical Engineering\n\nPresent biomedical engineer findings and proposals to decision-makers and stakeholders. The deliverable is a presentation structure with evidence summary and decision asks.\nThis skill is written for a biomedical engineer working with hospitals, device manufacturers and patients in hospital engineering departments and laboratories.\n\n## When to use\n- You are a biomedical engineer preparing, delivering or reviewing this part of your work in hospital engineering departments and laboratories.\n- You need a defensible, repeatable approach that produces a presentation structure with evidence summary and decision asks.\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| Calibration | adjusting a device to measure or perform accurately |\n| Asset register | the inventory of medical devices and their status |\n| Adverse incident | an event where a device may have caused harm |\n\n## Workflow\n1. **Step 1** - Open with the decision or conclusion, then the evidence — busy stakeholders should not wait for the point\n2. **Step 2** - Support claims with data from device evaluations and movement in device uptime, with sources and limits stated\n3. **Step 3** - Address the hard parts directly, including device failures harming patients and what it would take to reduce it\n4. **Step 4** - Make the ask specific: what decision, by when, with what resources for work in hospital engineering departments and laboratories\n5. **Step 5** - Follow up in writing the same day: decisions made, actions agreed, owners and dates\n\n## Profession-Specific Components\n| Component | Details for Biomedical Engineering |\n|-----------|-------------------------------|\n| Core documentation | device evaluations; maintenance records; incident investigations; specifications |\n| Core tools & equipment | test equipment; asset management systems; design software; calibration tools |\n| People involved | hospitals, device manufacturers and patients; the biomedical engineer; colleagues and other services in hospital engineering departments and laboratories |\n| Primary record | device evaluations — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in hospital engineering departments and laboratories] | **Objective:** [What this must achieve] | **Audience:** [hospitals, device manufacturers and patients and other stakeholders]\n\nThe finished output is a presentation structure with evidence summary and decision asks, 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 device evaluations.\n2. **Short-term:** Complete the workflow steps and record outcomes against device uptime.\n3. **Medium-term:** Review results, close actions, and update local procedures in hospital engineering departments and laboratories.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| device uptime | Agree a local target and track the trend | Measured from device evaluations and reviewed on a set cycle |\n| maintenance completion | Agree a local target and track the trend | Measured from device evaluations and reviewed on a set cycle |\n| incident rates | Agree a local target and track the trend | Measured from device evaluations and reviewed on a set cycle |\n| evaluation turnaround | Agree a local target and track the trend | Measured from device evaluations and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: device failures harming patients.\n- Never let this happen: maintenance backlogs.\n- Never let this happen: unapproved modifications.\n- Work only within the competence and authority of a biomedical engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to hospital engineering departments and laboratories'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 biomedical engineer in hospital engineering departments and laboratories applies this workflow for hospitals, device manufacturers and patients: they open\ndevice evaluations, work through the five steps using test equipment, and close by recording\nthe outcome against device uptime 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":44,"category":45,"description":46},1,"Biomedical Engineering","Present biomedical engineer findings and proposals to decision-makers and stakeholders.\nTRIGGERS - Use when a biomedical engineer needs a stakeholder presentation for hospitals, device manufacturers and patients in hospital engineering departments and laboratories.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fbiomedical-engineering-stakeholder-presentation",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill biomedical-engineering-stakeholder-presentation",{"tool":62,"command":63},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill biomedical-engineering-stakeholder-presentation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill biomedical-engineering-stakeholder-presentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fbiomedical-engineering-stakeholder-presentation\u002FSKILL.md",true,[],[71,92,105,118,127,141],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":39},"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",[],[78,79,80,81,82,83,30,84,85,86,36,87,34,88,33,89,90,91],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":39},"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",[],[99,79,100,101,36,87,34,102,88,33,103,30,91,104,84,85],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":39},"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",[],[112,113,79,114,115,84,85,87,34,88,33,116,117,30,91,36],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":39},"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",[124],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[126,79,27,32,30,29,91,33,37,84,85,36,87,34,88],"youth work stakeholder presentation",{"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":39},"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,79,137,85,82,138,84,36,87,34,88,33,30,139,140,91],"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":39},"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":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[79,151,152,153,30,33,88,154,155,91,85,84,87,34,36],"service","plan","youth work service plan","design","as"]