[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70W5EB7GSACRPSEMCW55MT8":3,"skill-same:01M70W5EB7GSACRPSEMCW55MT8":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},"01M70W5EB7GSACRPSEMCW55MT8","clinical-research-client-explanation",null,"Explain complex clinical research practitioner matters to trial participants, sponsors and investigators in plain, honest language.\nTRIGGERS - Use when a clinical research practitioner needs a client explanation & communication guide for trial participants, sponsors and investigators in hospitals and research sites.","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\u002Fclinical-research-client-explanation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"clinical research client explanation","clinical","research","clinical research","client","for","triggers","sites","use","when","explain","communication","plain","language","guide","2026-11-10 10:12:30",false,"---\nname: clinical-research-client-explanation\ndescription: |\n  Explain complex clinical research practitioner matters to trial participants, sponsors and investigators in plain, honest language.\n  TRIGGERS - Use when a clinical research practitioner needs a client explanation & communication guide for trial participants, sponsors and investigators in hospitals and research sites.\ncategory: Clinical Research\nlicense: MIT\nversion: 1.0\n---\n# Client Explanation & Communication Guide — Clinical Research\n\nExplain complex clinical research practitioner matters to trial participants, sponsors and investigators in plain, honest language. The deliverable is a communication pack: explanation script, FAQs and a written summary.\nThis skill is written for a clinical research practitioner working with trial participants, sponsors and investigators in hospitals and research sites.\n\n## When to use\n- You are a clinical research practitioner preparing, delivering or reviewing this part of your work in hospitals and research sites.\n- You need a defensible, repeatable approach that produces a communication pack: explanation script, FAQs and a written summary.\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| Protocol | the detailed plan for a clinical trial |\n| Informed consent | a participant's voluntary agreement after full explanation |\n| Adverse event | an untoward medical occurrence in a participant |\n\n## Workflow\n1. **Step 1** - Identify what trial participants, sponsors and investigators actually need to decide or understand, and the misconceptions to clear up first\n2. **Step 2** - Translate the technical content — including terms behind protocols — into plain language without losing accuracy\n3. **Step 3** - Structure the explanation: what we found, what it means, the options, the recommendation and the risks such as consent failures\n4. **Step 4** - Check understanding by asking trial participants, sponsors and investigators to play it back in their own words; correct gaps kindly\n5. **Step 5** - Follow up with a written summary the same day and record the conversation in the file\n\n## Profession-Specific Components\n| Component | Details for Clinical Research |\n|-----------|-------------------------------|\n| Core documentation | protocols; consent forms; case report forms; monitoring reports |\n| Core tools & equipment | electronic data capture; trial management systems; laboratory kits; randomisation systems |\n| People involved | trial participants, sponsors and investigators; the clinical research practitioner; colleagues and other services in hospitals and research sites |\n| Primary record | protocols — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in hospitals and research sites] | **Objective:** [What this must achieve] | **Audience:** [trial participants, sponsors and investigators and other stakeholders]\n\nThe finished output is a communication pack: explanation script, FAQs and a written summary, 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 protocols.\n2. **Short-term:** Complete the workflow steps and record outcomes against recruitment to target.\n3. **Medium-term:** Review results, close actions, and update local procedures in hospitals and research sites.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| recruitment to target | Agree a local target and track the trend | Measured from protocols and reviewed on a set cycle |\n| protocol deviation rates | Agree a local target and track the trend | Measured from protocols and reviewed on a set cycle |\n| data query resolution | Agree a local target and track the trend | Measured from protocols and reviewed on a set cycle |\n| monitoring findings | Agree a local target and track the trend | Measured from protocols and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: consent failures.\n- Never let this happen: protocol deviations unreported.\n- Never let this happen: participant safety signals missed.\n- Work only within the competence and authority of a clinical research practitioner; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to hospitals and research sites'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 clinical research practitioner in hospitals and research sites applies this workflow for trial participants, sponsors and investigators: they open\nprotocols, work through the five steps using electronic data capture, and close by recording\nthe outcome against recruitment to target and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Client Explanation & Communication Guide — Clinical Research\n\nExplain complex clinical research practitioner matters to trial participants, sponsors and investigators in plain, honest language. The deliverable is a communication pack: explanation script, FAQs and a written summary.\nThis skill is written for a clinical research practitioner working with trial participants, sponsors and investigators in hospitals and research sites.\n\n## When to use\n- You are a clinical research practitioner preparing, delivering or reviewing this part of your work in hospitals and research sites.\n- You need a defensible, repeatable approach that produces a communication pack: explanation script, FAQs and a written summary.\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| Protocol | the detailed plan for a clinical trial |\n| Informed consent | a participant's voluntary agreement after full explanation |\n| Adverse event | an untoward medical occurrence in a participant |\n\n## Workflow\n1. **Step 1** - Identify what trial participants, sponsors and investigators actually need to decide or understand, and the misconceptions to clear up first\n2. **Step 2** - Translate the technical content — including terms behind protocols — into plain language without losing accuracy\n3. **Step 3** - Structure the explanation: what we found, what it means, the options, the recommendation and the risks such as consent failures\n4. **Step 4** - Check understanding by asking trial participants, sponsors and investigators to play it back in their own words; correct gaps kindly\n5. **Step 5** - Follow up with a written summary the same day and record the conversation in the file\n\n## Profession-Specific Components\n| Component | Details for Clinical Research |\n|-----------|-------------------------------|\n| Core documentation | protocols; consent forms; case report forms; monitoring reports |\n| Core tools & equipment | electronic data capture; trial management systems; laboratory kits; randomisation systems |\n| People involved | trial participants, sponsors and investigators; the clinical research practitioner; colleagues and other services in hospitals and research sites |\n| Primary record | protocols — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in hospitals and research sites] | **Objective:** [What this must achieve] | **Audience:** [trial participants, sponsors and investigators and other stakeholders]\n\nThe finished output is a communication pack: explanation script, FAQs and a written summary, 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 protocols.\n2. **Short-term:** Complete the workflow steps and record outcomes against recruitment to target.\n3. **Medium-term:** Review results, close actions, and update local procedures in hospitals and research sites.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| recruitment to target | Agree a local target and track the trend | Measured from protocols and reviewed on a set cycle |\n| protocol deviation rates | Agree a local target and track the trend | Measured from protocols and reviewed on a set cycle |\n| data query resolution | Agree a local target and track the trend | Measured from protocols and reviewed on a set cycle |\n| monitoring findings | Agree a local target and track the trend | Measured from protocols and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: consent failures.\n- Never let this happen: protocol deviations unreported.\n- Never let this happen: participant safety signals missed.\n- Work only within the competence and authority of a clinical research practitioner; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to hospitals and research sites'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 clinical research practitioner in hospitals and research sites applies this workflow for trial participants, sponsors and investigators: they open\nprotocols, work through the five steps using electronic data capture, and close by recording\nthe outcome against recruitment to target 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,"Clinical Research","Explain complex clinical research practitioner matters to trial participants, sponsors and investigators in plain, honest language.\nTRIGGERS - Use when a clinical research practitioner needs a client explanation & communication guide for trial participants, sponsors and investigators in hospitals and research sites.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fclinical-research-client-explanation",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 clinical-research-client-explanation",{"tool":62,"command":63},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill clinical-research-client-explanation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill clinical-research-client-explanation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fclinical-research-client-explanation\u002FSKILL.md",true,[],[71,91,104,117,132,146],{"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,38,82,29,83,84,85,33,86,32,87,30,88,89,90],"youth work troubleshooting guide","work","troubleshooting","troubleshooting 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":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",[],[98,79,99,100,33,86,32,101,87,30,102,29,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":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",[],[111,112,79,113,114,83,84,86,32,87,30,115,116,29,90,33],"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":126,"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",[123],{"categoryNo":124,"categoryName":125,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",[127,79,128,129,29,130,90,30,131,83,84,33,86,32,87],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":138,"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",[],[139,140,141,79,142,84,38,143,83,33,86,32,87,30,29,144,145,90],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":155,"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",[152],{"categoryNo":153,"categoryName":154,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[79,156,157,158,29,30,87,159,160,90,84,83,86,32,33],"service","plan","youth work service plan","design","as"]