[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M711MMTPJWCM8PYK3TSK014M":3,"skill-same:01M711MMTPJWCM8PYK3TSK014M":68},{"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":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M711MMTPJWCM8PYK3TSK014M","gastroenterology-incident-report",null,"Respond to, record and learn from incidents involving patients with digestive system conditions in an endoscopy unit and gastroenterology clinic.\nTRIGGERS - Use when a gastroenterologist needs a incident reporting & response for patients with digestive system conditions in an endoscopy unit and gastroenterology clinic.","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\u002Fgastroenterology-incident-report\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"incident report","report","gastroenterology","gastroenterology incident report","incident","reporting","record","with","learn","when","use","triggers","incident reporting","incidents","respond","system","for","unit","2026-11-10 10:12:30",false,"---\nname: gastroenterology-incident-report\ndescription: |\n  Respond to, record and learn from incidents involving patients with digestive system conditions in an endoscopy unit and gastroenterology clinic.\n  TRIGGERS - Use when a gastroenterologist needs a incident reporting & response for patients with digestive system conditions in an endoscopy unit and gastroenterology clinic.\ncategory: Gastroenterology\nlicense: MIT\nversion: 1.0\n---\n# Incident Reporting & Response — Gastroenterology\n\nRespond to, record and learn from incidents involving patients with digestive system conditions in an endoscopy unit and gastroenterology clinic. The deliverable is a factual incident report and a lessons-learned action list.\nThis skill is written for a gastroenterologist working with patients with digestive system conditions in an endoscopy unit and gastroenterology clinic.\n\n## When to use\n- You are a gastroenterologist preparing, delivering or reviewing this part of your work in an endoscopy unit and gastroenterology clinic.\n- You need a defensible, repeatable approach that produces a factual incident report and a lessons-learned action list.\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| Endoscopy | examining the digestive tract with a flexible camera |\n| Cirrhosis | advanced scarring of the liver |\n| IBD | inflammatory bowel disease, mainly Crohn's disease and ulcerative colitis |\n\n## Workflow\n1. **Step 1** - Make the situation safe first; attend to people before paperwork, and escalate if missed gastrointestinal bleeding is still live\n2. **Step 2** - Record facts while they are fresh: what happened, when, who was involved, what was observed — in endoscopy reports\n3. **Step 3** - Notify the people and bodies who must know, within the timeframes that apply in an endoscopy unit and gastroenterology clinic\n4. **Step 4** - Support those affected, including honest communication with patients with digestive system conditions about what happened and what happens next\n5. **Step 5** - Analyse causes without blame, agree preventive actions with owners and dates, and track them to closure\n\n## Profession-Specific Components\n| Component | Details for Gastroenterology |\n|-----------|-------------------------------|\n| Core documentation | endoscopy reports; bowel screening results; liver function reviews; biopsy reports |\n| Core tools & equipment | endoscopes; capsule endoscopy systems; sedation monitoring; laboratory analysers |\n| People involved | patients with digestive system conditions; the gastroenterologist; colleagues and other services in an endoscopy unit and gastroenterology clinic |\n| Primary record | endoscopy reports — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in an endoscopy unit and gastroenterology clinic] | **Objective:** [What this must achieve] | **Audience:** [patients with digestive system conditions and other stakeholders]\n\nThe finished output is a factual incident report and a lessons-learned action list, 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 endoscopy reports.\n2. **Short-term:** Complete the workflow steps and record outcomes against endoscopy waiting times.\n3. **Medium-term:** Review results, close actions, and update local procedures in an endoscopy unit and gastroenterology clinic.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| endoscopy waiting times | Agree a local target and track the trend | Measured from endoscopy reports and reviewed on a set cycle |\n| bowel cancer detection rate | Agree a local target and track the trend | Measured from endoscopy reports and reviewed on a set cycle |\n| sedation incident rate | Agree a local target and track the trend | Measured from endoscopy reports and reviewed on a set cycle |\n| clinic follow-up completion | Agree a local target and track the trend | Measured from endoscopy reports and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: missed gastrointestinal bleeding.\n- Never let this happen: sedation complications.\n- Never let this happen: delayed cancer pathway.\n- Work only within the competence and authority of a gastroenterologist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to an endoscopy unit and gastroenterology clinic'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 gastroenterologist in an endoscopy unit and gastroenterology clinic applies this workflow for patients with digestive system conditions: they open\nendoscopy reports, work through the five steps using endoscopes, and close by recording\nthe outcome against endoscopy waiting times and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Incident Reporting & Response — Gastroenterology\n\nRespond to, record and learn from incidents involving patients with digestive system conditions in an endoscopy unit and gastroenterology clinic. The deliverable is a factual incident report and a lessons-learned action list.\nThis skill is written for a gastroenterologist working with patients with digestive system conditions in an endoscopy unit and gastroenterology clinic.\n\n## When to use\n- You are a gastroenterologist preparing, delivering or reviewing this part of your work in an endoscopy unit and gastroenterology clinic.\n- You need a defensible, repeatable approach that produces a factual incident report and a lessons-learned action list.\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| Endoscopy | examining the digestive tract with a flexible camera |\n| Cirrhosis | advanced scarring of the liver |\n| IBD | inflammatory bowel disease, mainly Crohn's disease and ulcerative colitis |\n\n## Workflow\n1. **Step 1** - Make the situation safe first; attend to people before paperwork, and escalate if missed gastrointestinal bleeding is still live\n2. **Step 2** - Record facts while they are fresh: what happened, when, who was involved, what was observed — in endoscopy reports\n3. **Step 3** - Notify the people and bodies who must know, within the timeframes that apply in an endoscopy unit and gastroenterology clinic\n4. **Step 4** - Support those affected, including honest communication with patients with digestive system conditions about what happened and what happens next\n5. **Step 5** - Analyse causes without blame, agree preventive actions with owners and dates, and track them to closure\n\n## Profession-Specific Components\n| Component | Details for Gastroenterology |\n|-----------|-------------------------------|\n| Core documentation | endoscopy reports; bowel screening results; liver function reviews; biopsy reports |\n| Core tools & equipment | endoscopes; capsule endoscopy systems; sedation monitoring; laboratory analysers |\n| People involved | patients with digestive system conditions; the gastroenterologist; colleagues and other services in an endoscopy unit and gastroenterology clinic |\n| Primary record | endoscopy reports — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in an endoscopy unit and gastroenterology clinic] | **Objective:** [What this must achieve] | **Audience:** [patients with digestive system conditions and other stakeholders]\n\nThe finished output is a factual incident report and a lessons-learned action list, 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 endoscopy reports.\n2. **Short-term:** Complete the workflow steps and record outcomes against endoscopy waiting times.\n3. **Medium-term:** Review results, close actions, and update local procedures in an endoscopy unit and gastroenterology clinic.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| endoscopy waiting times | Agree a local target and track the trend | Measured from endoscopy reports and reviewed on a set cycle |\n| bowel cancer detection rate | Agree a local target and track the trend | Measured from endoscopy reports and reviewed on a set cycle |\n| sedation incident rate | Agree a local target and track the trend | Measured from endoscopy reports and reviewed on a set cycle |\n| clinic follow-up completion | Agree a local target and track the trend | Measured from endoscopy reports and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: missed gastrointestinal bleeding.\n- Never let this happen: sedation complications.\n- Never let this happen: delayed cancer pathway.\n- Work only within the competence and authority of a gastroenterologist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to an endoscopy unit and gastroenterology clinic'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 gastroenterologist in an endoscopy unit and gastroenterology clinic applies this workflow for patients with digestive system conditions: they open\nendoscopy reports, work through the five steps using endoscopes, and close by recording\nthe outcome against endoscopy waiting times 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":42,"category":43,"description":44},1,"Gastroenterology","Respond to, record and learn from incidents involving patients with digestive system conditions in an endoscopy unit and gastroenterology clinic.\nTRIGGERS - Use when a gastroenterologist needs a incident reporting & response for patients with digestive system conditions in an endoscopy unit and gastroenterology clinic.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fgastroenterology-incident-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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill gastroenterology-incident-report",{"tool":60,"command":61},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill gastroenterology-incident-report",{"tool":63,"command":64},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill gastroenterology-incident-report","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fgastroenterology-incident-report\u002FSKILL.md",true,[],[69,90,103,116,133,147],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":37},"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",[],[76,77,78,79,80,81,35,82,83,84,28,85,29,86,30,87,88,89],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":37},"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",[],[97,77,98,99,28,85,29,100,86,30,101,35,89,102,82,83],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":37},"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",[],[110,111,77,112,113,82,83,85,29,86,30,114,115,35,89,28],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":127,"publishedAt":37},"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",[122],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[128,77,129,130,35,131,89,30,132,82,83,28,85,29,86],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":37},"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",[],[140,141,142,77,143,83,80,144,82,28,85,29,86,30,35,145,146,89],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":156,"publishedAt":37},"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",[153],{"categoryNo":154,"categoryName":155,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000015","视觉设计",[77,157,158,159,35,30,86,160,161,89,83,82,85,29,28],"service","plan","youth work service plan","design","as"]