[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71186PFA6R936D4D5ECDMJX":3,"skill-same:01M71186PFA6R936D4D5ECDMJX":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},"01M71186PFA6R936D4D5ECDMJX","forensic-science-troubleshooting-guide",null,"Diagnose and resolve common problems a forensic scientist meets in laboratories and crime scenes.\nTRIGGERS - Use when a forensic scientist needs a troubleshooting & problem solving for police, courts and legal teams in laboratories and crime scenes.","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\u002Fforensic-science-troubleshooting-guide\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"science","forensic science troubleshooting guide","troubleshooting","troubleshooting guide","guide","problem","diagnose","for","triggers","teams","scenes","use","when","common","legal","problem solving","2026-11-10 10:12:30",false,"---\nname: forensic-science-troubleshooting-guide\ndescription: |\n  Diagnose and resolve common problems a forensic scientist meets in laboratories and crime scenes.\n  TRIGGERS - Use when a forensic scientist needs a troubleshooting & problem solving for police, courts and legal teams in laboratories and crime scenes.\ncategory: Forensic Science\nlicense: MIT\nversion: 1.0\n---\n# Troubleshooting & Problem Solving — Forensic Science\n\nDiagnose and resolve common problems a forensic scientist meets in laboratories and crime scenes. The deliverable is a troubleshooting guide: symptoms, likely causes, checks and fixes.\nThis skill is written for a forensic scientist working with police, courts and legal teams in laboratories and crime scenes.\n\n## When to use\n- You are a forensic scientist preparing, delivering or reviewing this part of your work in laboratories and crime scenes.\n- You need a defensible, repeatable approach that produces a troubleshooting guide: symptoms, likely causes, checks and fixes.\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| Chain of custody | the documented movement of evidence |\n| Exhibit | an item of evidence in an investigation |\n| Proficiency testing | external checks of a scientist's accuracy |\n\n## Workflow\n1. **Step 1** - Describe the problem precisely from the record in examination records — when it started, what changed, who it affects\n2. **Step 2** - Work from most likely and most dangerous causes first; rule out anything connected to evidence contamination early\n3. **Step 3** - Run checks in a logical order using laboratory instruments, changing one variable at a time so the cause can be isolated\n4. **Step 4** - Apply the fix, then verify against report turnaround that the problem is actually resolved, not just quieter\n5. **Step 5** - Document the diagnosis and fix so the next occurrence is faster, and flag recurring problems for root-cause work\n\n## Profession-Specific Components\n| Component | Details for Forensic Science |\n|-----------|-------------------------------|\n| Core documentation | examination records; evidence logs; expert reports; court statements |\n| Core tools & equipment | laboratory instruments; comparison microscopes; DNA analysis systems; scene equipment |\n| People involved | police, courts and legal teams; the forensic scientist; colleagues and other services in laboratories and crime scenes |\n| Primary record | examination records — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in laboratories and crime scenes] | **Objective:** [What this must achieve] | **Audience:** [police, courts and legal teams and other stakeholders]\n\nThe finished output is a troubleshooting guide: symptoms, likely causes, checks and fixes, 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 examination records.\n2. **Short-term:** Complete the workflow steps and record outcomes against report turnaround.\n3. **Medium-term:** Review results, close actions, and update local procedures in laboratories and crime scenes.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| report turnaround | Agree a local target and track the trend | Measured from examination records and reviewed on a set cycle |\n| evidence integrity audits | Agree a local target and track the trend | Measured from examination records and reviewed on a set cycle |\n| court acceptance | Agree a local target and track the trend | Measured from examination records and reviewed on a set cycle |\n| proficiency test results | Agree a local target and track the trend | Measured from examination records and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: evidence contamination.\n- Never let this happen: interpretation overstated.\n- Never let this happen: chain of custody gaps.\n- Work only within the competence and authority of a forensic scientist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to laboratories and crime scenes'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 forensic scientist in laboratories and crime scenes applies this workflow for police, courts and legal teams: they open\nexamination records, work through the five steps using laboratory instruments, and close by recording\nthe outcome against report turnaround and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Troubleshooting & Problem Solving — Forensic Science\n\nDiagnose and resolve common problems a forensic scientist meets in laboratories and crime scenes. The deliverable is a troubleshooting guide: symptoms, likely causes, checks and fixes.\nThis skill is written for a forensic scientist working with police, courts and legal teams in laboratories and crime scenes.\n\n## When to use\n- You are a forensic scientist preparing, delivering or reviewing this part of your work in laboratories and crime scenes.\n- You need a defensible, repeatable approach that produces a troubleshooting guide: symptoms, likely causes, checks and fixes.\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| Chain of custody | the documented movement of evidence |\n| Exhibit | an item of evidence in an investigation |\n| Proficiency testing | external checks of a scientist's accuracy |\n\n## Workflow\n1. **Step 1** - Describe the problem precisely from the record in examination records — when it started, what changed, who it affects\n2. **Step 2** - Work from most likely and most dangerous causes first; rule out anything connected to evidence contamination early\n3. **Step 3** - Run checks in a logical order using laboratory instruments, changing one variable at a time so the cause can be isolated\n4. **Step 4** - Apply the fix, then verify against report turnaround that the problem is actually resolved, not just quieter\n5. **Step 5** - Document the diagnosis and fix so the next occurrence is faster, and flag recurring problems for root-cause work\n\n## Profession-Specific Components\n| Component | Details for Forensic Science |\n|-----------|-------------------------------|\n| Core documentation | examination records; evidence logs; expert reports; court statements |\n| Core tools & equipment | laboratory instruments; comparison microscopes; DNA analysis systems; scene equipment |\n| People involved | police, courts and legal teams; the forensic scientist; colleagues and other services in laboratories and crime scenes |\n| Primary record | examination records — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in laboratories and crime scenes] | **Objective:** [What this must achieve] | **Audience:** [police, courts and legal teams and other stakeholders]\n\nThe finished output is a troubleshooting guide: symptoms, likely causes, checks and fixes, 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 examination records.\n2. **Short-term:** Complete the workflow steps and record outcomes against report turnaround.\n3. **Medium-term:** Review results, close actions, and update local procedures in laboratories and crime scenes.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| report turnaround | Agree a local target and track the trend | Measured from examination records and reviewed on a set cycle |\n| evidence integrity audits | Agree a local target and track the trend | Measured from examination records and reviewed on a set cycle |\n| court acceptance | Agree a local target and track the trend | Measured from examination records and reviewed on a set cycle |\n| proficiency test results | Agree a local target and track the trend | Measured from examination records and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: evidence contamination.\n- Never let this happen: interpretation overstated.\n- Never let this happen: chain of custody gaps.\n- Work only within the competence and authority of a forensic scientist; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to laboratories and crime scenes'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 forensic scientist in laboratories and crime scenes applies this workflow for police, courts and legal teams: they open\nexamination records, work through the five steps using laboratory instruments, and close by recording\nthe outcome against report turnaround 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,"Forensic Science","Diagnose and resolve common problems a forensic scientist meets in laboratories and crime scenes.\nTRIGGERS - Use when a forensic scientist needs a troubleshooting & problem solving for police, courts and legal teams in laboratories and crime scenes.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fforensic-science-troubleshooting-guide",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 forensic-science-troubleshooting-guide",{"tool":58,"command":59},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill forensic-science-troubleshooting-guide",{"tool":61,"command":62},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill forensic-science-troubleshooting-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fforensic-science-troubleshooting-guide\u002FSKILL.md",true,[],[67,81,94,107,124,138],{"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,75,21,22,23,34,26,76,77,32,31,78,30,79,27,25,24,80],"youth work troubleshooting guide","work","outreach","settings","people","worker","communities",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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",[],[88,75,89,90,31,78,30,91,79,27,92,26,80,93,76,77],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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",[],[101,102,75,103,104,76,77,78,30,79,27,105,106,26,80,31],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":118,"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",[113],{"categoryNo":114,"categoryName":115,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[119,75,120,121,26,122,80,27,123,76,77,31,78,30,79],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"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",[],[131,132,133,75,134,77,23,135,76,31,78,30,79,27,26,136,137,80],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":139,"name":140,"nameZh":6,"description":141,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":142,"categories":143,"keywords":147,"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",[144],{"categoryNo":145,"categoryName":146,"taxonomyType":116,"taxonomyTypeDesc":117},"01JBSEEDCAT000000000000015","视觉设计",[75,148,149,150,26,27,79,151,152,80,77,76,78,30,31],"service","plan","youth work service plan","design","as"]