[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M714CRAHTV8CMQ3BTY046WZX":3,"skill-same:01M714CRAHTV8CMQ3BTY046WZX":69},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M714CRAHTV8CMQ3BTY046WZX","marine-engineering-metrics-review",null,"Track, interpret and act on the outcome metrics that matter for a marine engineer.\nTRIGGERS - Use when a marine engineer needs a metrics & outcomes review for ship owners, operators and crews in ships' engine rooms and shipyards.","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\u002Fmarine-engineering-metrics-review\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"marine engineering metrics review","review","engineering","metrics","metrics review","ship","owners","act","marine engineer","outcome","operators","outcomes","track","engine","when","use","triggers","engineer","for","2026-11-10 10:12:30",false,"---\nname: marine-engineering-metrics-review\ndescription: |\n  Track, interpret and act on the outcome metrics that matter for a marine engineer.\n  TRIGGERS - Use when a marine engineer needs a metrics & outcomes review for ship owners, operators and crews in ships' engine rooms and shipyards.\ncategory: Marine Engineering\nlicense: MIT\nversion: 1.0\n---\n# Metrics & Outcomes Review — Marine Engineering\n\nTrack, interpret and act on the outcome metrics that matter for a marine engineer. The deliverable is a metrics dashboard definition and an interpretation\u002Faction review.\nThis skill is written for a marine engineer working with ship owners, operators and crews in ships' engine rooms and shipyards.\n\n## When to use\n- You are a marine engineer preparing, delivering or reviewing this part of your work in ships' engine rooms and shipyards.\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| Planned maintenance | scheduled servicing based on time or running hours |\n| Bunkering | taking on fuel for a vessel |\n| Bilge | the lowest part of a ship where water collects |\n\n## Workflow\n1. **Step 1** - Define each metric precisely — start with machinery downtime — including source data in maintenance logs 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 machinery failures at sea; test one change at a time where possible\n5. **Step 5** - Report results honestly to stakeholders in ships' engine rooms and shipyards, including where outcomes fell short and what changes\n\n## Profession-Specific Components\n| Component | Details for Marine Engineering |\n|-----------|-------------------------------|\n| Core documentation | maintenance logs; machinery records; spares inventories; survey reports |\n| Core tools & equipment | engine monitoring systems; workshop machinery; testing equipment; planned maintenance software |\n| People involved | ship owners, operators and crews; the marine engineer; colleagues and other services in ships' engine rooms and shipyards |\n| Primary record | maintenance logs — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in ships' engine rooms and shipyards] | **Objective:** [What this must achieve] | **Audience:** [ship owners, operators and crews 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 maintenance logs.\n2. **Short-term:** Complete the workflow steps and record outcomes against machinery downtime.\n3. **Medium-term:** Review results, close actions, and update local procedures in ships' engine rooms and shipyards.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| machinery downtime | Agree a local target and track the trend | Measured from maintenance logs and reviewed on a set cycle |\n| maintenance completion | Agree a local target and track the trend | Measured from maintenance logs and reviewed on a set cycle |\n| fuel consumption | Agree a local target and track the trend | Measured from maintenance logs and reviewed on a set cycle |\n| survey outcomes | Agree a local target and track the trend | Measured from maintenance logs and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: machinery failures at sea.\n- Never let this happen: oil pollution incidents.\n- Never let this happen: burns and injuries.\n- Work only within the competence and authority of a marine engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to ships' engine rooms and shipyards'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 marine engineer in ships' engine rooms and shipyards applies this workflow for ship owners, operators and crews: they open\nmaintenance logs, work through the five steps using engine monitoring systems, and close by recording\nthe outcome against machinery downtime and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Metrics & Outcomes Review — Marine Engineering\n\nTrack, interpret and act on the outcome metrics that matter for a marine engineer. The deliverable is a metrics dashboard definition and an interpretation\u002Faction review.\nThis skill is written for a marine engineer working with ship owners, operators and crews in ships' engine rooms and shipyards.\n\n## When to use\n- You are a marine engineer preparing, delivering or reviewing this part of your work in ships' engine rooms and shipyards.\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| Planned maintenance | scheduled servicing based on time or running hours |\n| Bunkering | taking on fuel for a vessel |\n| Bilge | the lowest part of a ship where water collects |\n\n## Workflow\n1. **Step 1** - Define each metric precisely — start with machinery downtime — including source data in maintenance logs 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 machinery failures at sea; test one change at a time where possible\n5. **Step 5** - Report results honestly to stakeholders in ships' engine rooms and shipyards, including where outcomes fell short and what changes\n\n## Profession-Specific Components\n| Component | Details for Marine Engineering |\n|-----------|-------------------------------|\n| Core documentation | maintenance logs; machinery records; spares inventories; survey reports |\n| Core tools & equipment | engine monitoring systems; workshop machinery; testing equipment; planned maintenance software |\n| People involved | ship owners, operators and crews; the marine engineer; colleagues and other services in ships' engine rooms and shipyards |\n| Primary record | maintenance logs — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in ships' engine rooms and shipyards] | **Objective:** [What this must achieve] | **Audience:** [ship owners, operators and crews 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 maintenance logs.\n2. **Short-term:** Complete the workflow steps and record outcomes against machinery downtime.\n3. **Medium-term:** Review results, close actions, and update local procedures in ships' engine rooms and shipyards.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| machinery downtime | Agree a local target and track the trend | Measured from maintenance logs and reviewed on a set cycle |\n| maintenance completion | Agree a local target and track the trend | Measured from maintenance logs and reviewed on a set cycle |\n| fuel consumption | Agree a local target and track the trend | Measured from maintenance logs and reviewed on a set cycle |\n| survey outcomes | Agree a local target and track the trend | Measured from maintenance logs and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: machinery failures at sea.\n- Never let this happen: oil pollution incidents.\n- Never let this happen: burns and injuries.\n- Work only within the competence and authority of a marine engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to ships' engine rooms and shipyards'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 marine engineer in ships' engine rooms and shipyards applies this workflow for ship owners, operators and crews: they open\nmaintenance logs, work through the five steps using engine monitoring systems, and close by recording\nthe outcome against machinery downtime 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":43,"category":44,"description":45},1,"Marine Engineering","Track, interpret and act on the outcome metrics that matter for a marine engineer.\nTRIGGERS - Use when a marine engineer needs a metrics & outcomes review for ship owners, operators and crews in ships' engine rooms and shipyards.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fmarine-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":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill marine-engineering-metrics-review",{"tool":61,"command":62},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill marine-engineering-metrics-review",{"tool":64,"command":65},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill marine-engineering-metrics-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fmarine-engineering-metrics-review\u002FSKILL.md",true,[],[70,91,104,117,134,148],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":38},"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",[],[77,78,79,80,81,82,37,83,84,85,33,86,34,87,35,88,89,90],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","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":38},"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,78,99,100,33,86,34,101,87,35,102,37,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":38},"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,78,113,114,83,84,86,34,87,35,115,116,37,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":128,"publishedAt":38},"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":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000003","演示文稿","SCENARIO","使用场景",[129,78,130,131,37,132,90,35,133,83,84,33,86,34,87],"youth work stakeholder presentation","presentation","decision","proposals","present",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":38},"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",[],[141,142,143,78,144,84,81,145,83,33,86,34,87,35,37,146,147,90],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":157,"publishedAt":38},"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",[154],{"categoryNo":155,"categoryName":156,"taxonomyType":126,"taxonomyTypeDesc":127},"01JBSEEDCAT000000000000015","视觉设计",[78,158,159,160,37,35,87,161,162,90,84,83,86,34,33],"service","plan","youth work service plan","design","as"]