[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71007ZSCCS8TFN711MB5TS7":3,"skill-same:01M71007ZSCCS8TFN711MB5TS7":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":18,"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},"01M71007ZSCCS8TFN711MB5TS7","environmental-engineering-metrics-review",null,"Track, interpret and act on the outcome metrics that matter for a environmental engineer.\nTRIGGERS - Use when a environmental engineer needs a metrics & outcomes review for water companies, industries and regulators in treatment plants, client sites and design 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\u002Fenvironmental-engineering-metrics-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"environmental engineering metrics review","review","environmental engineering","environmental","engineering","metrics","metrics review","client","act","outcome","outcomes","track","when","use","design","sites","environmental engineer","triggers","engineer","for","2026-11-10 10:12:30",false,"---\nname: environmental-engineering-metrics-review\ndescription: |\n  Track, interpret and act on the outcome metrics that matter for a environmental engineer.\n  TRIGGERS - Use when a environmental engineer needs a metrics & outcomes review for water companies, industries and regulators in treatment plants, client sites and design offices.\ncategory: Environmental Engineering\nlicense: MIT\nversion: 1.0\n---\n# Metrics & Outcomes Review — Environmental Engineering\n\nTrack, interpret and act on the outcome metrics that matter for a environmental engineer. The deliverable is a metrics dashboard definition and an interpretation\u002Faction review.\nThis skill is written for a environmental engineer working with water companies, industries and regulators in treatment plants, client sites and design offices.\n\n## When to use\n- You are a environmental engineer preparing, delivering or reviewing this part of your work in treatment plants, client sites and design offices.\n- You need a defensible, repeatable approach that produces a metrics dashboard definition and an interpretation\u002Faction review.\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| Consent | permission to discharge treated water or waste |\n| Effluent | liquid waste discharged from a process |\n| Remediation | cleaning up contaminated land or water |\n\n## Workflow\n1. **Step 1** - Define each metric precisely — start with permit compliance — including source data in impact assessments and collection method\n2. **Step 2** - Set review cadence and comparison baselines so trends, not single data points, drive decisions\n3. **Step 3** - Investigate movements before celebrating or panicking: check data quality, case mix and one-off causes\n4. **Step 4** - Link metric movements to practice changes and to risks such as pollution incidents; test one change at a time where possible\n5. **Step 5** - Report results honestly to stakeholders in treatment plants, client sites and design offices, including where outcomes fell short and what changes\n\n## Profession-Specific Components\n| Component | Details for Environmental Engineering |\n|-----------|-------------------------------|\n| Core documentation | impact assessments; treatment designs; monitoring reports; permit applications |\n| Core tools & equipment | modelling software; sampling equipment; laboratory analysis; treatment plant systems |\n| People involved | water companies, industries and regulators; the environmental engineer; colleagues and other services in treatment plants, client sites and design offices |\n| Primary record | impact assessments — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in treatment plants, client sites and design offices] | **Objective:** [What this must achieve] | **Audience:** [water companies, industries and regulators and other stakeholders]\n\nThe finished output is a metrics dashboard definition and an interpretation\u002Faction review, 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 impact assessments.\n2. **Short-term:** Complete the workflow steps and record outcomes against permit compliance.\n3. **Medium-term:** Review results, close actions, and update local procedures in treatment plants, client sites and design offices.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| permit compliance | Agree a local target and track the trend | Measured from impact assessments and reviewed on a set cycle |\n| pollutant reduction | Agree a local target and track the trend | Measured from impact assessments and reviewed on a set cycle |\n| monitoring completion | Agree a local target and track the trend | Measured from impact assessments and reviewed on a set cycle |\n| project delivery | Agree a local target and track the trend | Measured from impact assessments and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: pollution incidents.\n- Never let this happen: consent breaches.\n- Never let this happen: design underperformance.\n- Work only within the competence and authority of a environmental engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to treatment plants, client sites and design 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 environmental engineer in treatment plants, client sites and design offices applies this workflow for water companies, industries and regulators: they open\nimpact assessments, work through the five steps using modelling software, and close by recording\nthe outcome against permit compliance and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Metrics & Outcomes Review — Environmental Engineering\n\nTrack, interpret and act on the outcome metrics that matter for a environmental engineer. The deliverable is a metrics dashboard definition and an interpretation\u002Faction review.\nThis skill is written for a environmental engineer working with water companies, industries and regulators in treatment plants, client sites and design offices.\n\n## When to use\n- You are a environmental engineer preparing, delivering or reviewing this part of your work in treatment plants, client sites and design offices.\n- You need a defensible, repeatable approach that produces a metrics dashboard definition and an interpretation\u002Faction review.\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| Consent | permission to discharge treated water or waste |\n| Effluent | liquid waste discharged from a process |\n| Remediation | cleaning up contaminated land or water |\n\n## Workflow\n1. **Step 1** - Define each metric precisely — start with permit compliance — including source data in impact assessments and collection method\n2. **Step 2** - Set review cadence and comparison baselines so trends, not single data points, drive decisions\n3. **Step 3** - Investigate movements before celebrating or panicking: check data quality, case mix and one-off causes\n4. **Step 4** - Link metric movements to practice changes and to risks such as pollution incidents; test one change at a time where possible\n5. **Step 5** - Report results honestly to stakeholders in treatment plants, client sites and design offices, including where outcomes fell short and what changes\n\n## Profession-Specific Components\n| Component | Details for Environmental Engineering |\n|-----------|-------------------------------|\n| Core documentation | impact assessments; treatment designs; monitoring reports; permit applications |\n| Core tools & equipment | modelling software; sampling equipment; laboratory analysis; treatment plant systems |\n| People involved | water companies, industries and regulators; the environmental engineer; colleagues and other services in treatment plants, client sites and design offices |\n| Primary record | impact assessments — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in treatment plants, client sites and design offices] | **Objective:** [What this must achieve] | **Audience:** [water companies, industries and regulators and other stakeholders]\n\nThe finished output is a metrics dashboard definition and an interpretation\u002Faction review, 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 impact assessments.\n2. **Short-term:** Complete the workflow steps and record outcomes against permit compliance.\n3. **Medium-term:** Review results, close actions, and update local procedures in treatment plants, client sites and design offices.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| permit compliance | Agree a local target and track the trend | Measured from impact assessments and reviewed on a set cycle |\n| pollutant reduction | Agree a local target and track the trend | Measured from impact assessments and reviewed on a set cycle |\n| monitoring completion | Agree a local target and track the trend | Measured from impact assessments and reviewed on a set cycle |\n| project delivery | Agree a local target and track the trend | Measured from impact assessments and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: pollution incidents.\n- Never let this happen: consent breaches.\n- Never let this happen: design underperformance.\n- Work only within the competence and authority of a environmental engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to treatment plants, client sites and design 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 environmental engineer in treatment plants, client sites and design offices applies this workflow for water companies, industries and regulators: they open\nimpact assessments, work through the five steps using modelling software, and close by recording\nthe outcome against permit compliance 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,"Environmental Engineering","Track, interpret and act on the outcome metrics that matter for a environmental engineer.\nTRIGGERS - Use when a environmental engineer needs a metrics & outcomes review for water companies, industries and regulators in treatment plants, client sites and design offices.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fenvironmental-engineering-metrics-review",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 environmental-engineering-metrics-review",{"tool":62,"command":63},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill environmental-engineering-metrics-review",{"tool":65,"command":66},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill environmental-engineering-metrics-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fenvironmental-engineering-metrics-review\u002FSKILL.md",true,[],[71,92,105,118,135,149],{"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,38,84,85,86,31,87,32,88,36,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,31,87,32,102,88,36,103,38,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,32,88,36,116,117,38,91,31],"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":129,"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":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[130,79,131,132,38,133,91,36,134,84,85,31,87,32,88],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"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",[],[142,143,144,79,145,85,82,146,84,31,87,32,88,36,38,147,148,91],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":158,"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",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000015","视觉设计",[79,159,160,161,38,36,88,33,162,91,85,84,87,32,31],"service","plan","youth work service plan","as"]