[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M714R4GCF6S4D6P3XAABAPXG":3,"skill-same:01M714R4GCF6S4D6P3XAABAPXG":83},{"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":31,"publishedAt":52,"linkOnly":53,"markdownContent":54,"markdownBody":55,"frontMatter":56,"refName":60,"commitSha":61,"skillDirectory":62,"forksCount":63,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M714R4GCF6S4D6P3XAABAPXG","mechanical-engineering-formal-report-writing",null,"Write formal reports as a mechanical engineer that stand up to scrutiny from any reader.\nTRIGGERS - Use when a mechanical engineer needs a formal report writing for manufacturing and product clients in design offices, factories and test facilities.","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\u002Fmechanical-engineering-formal-report-writing\u002FSKILL.md",[18,23,28],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000034","行政与办公人员","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51],"mechanical","writing","report writing","report","mechanical engineering","engineering","mechanical engineering formal report writing","write","manufacturing","product","test","reports","when","use","design","triggers","up","engineer","for","as","2026-11-10 10:12:30",false,"---\nname: mechanical-engineering-formal-report-writing\ndescription: |\n  Write formal reports as a mechanical engineer that stand up to scrutiny from any reader.\n  TRIGGERS - Use when a mechanical engineer needs a formal report writing for manufacturing and product clients in design offices, factories and test facilities.\ncategory: Mechanical Engineering\nlicense: MIT\nversion: 1.0\n---\n# Formal Report Writing — Mechanical Engineering\n\nWrite formal reports as a mechanical engineer that stand up to scrutiny from any reader. The deliverable is a report template with structure, evidence standards and review steps.\nThis skill is written for a mechanical engineer working with manufacturing and product clients in design offices, factories and test facilities.\n\n## When to use\n- You are a mechanical engineer preparing, delivering or reviewing this part of your work in design offices, factories and test facilities.\n- You need a defensible, repeatable approach that produces a report template with structure, evidence standards and review steps.\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| Tolerance | the permitted variation in a dimension |\n| Fatigue | weakening of material from repeated loading |\n| Prototype | an early version built to test a design |\n\n## Workflow\n1. **Step 1** - Establish the report's purpose, audience and deadline before writing; gather source material from design files\n2. **Step 2** - Structure: summary, background, method, findings, analysis, recommendations — in that order\n3. **Step 3** - Write findings factually and separately from opinion; label professional judgement as judgement\n4. **Step 4** - Support key points with evidence and with prototype test pass rates where outcomes are claimed; acknowledge limitations openly\n5. **Step 5** - Proofread for accuracy and tone, check names, dates and figures twice, and consider component failures before release\n\n## Profession-Specific Components\n| Component | Details for Mechanical Engineering |\n|-----------|-------------------------------|\n| Core documentation | design files; test reports; maintenance analyses; specifications |\n| Core tools & equipment | CAD software; simulation tools; test rigs; measurement instruments |\n| People involved | manufacturing and product clients; the mechanical engineer; colleagues and other services in design offices, factories and test facilities |\n| Primary record | design files — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design offices, factories and test facilities] | **Objective:** [What this must achieve] | **Audience:** [manufacturing and product clients and other stakeholders]\n\nThe finished output is a report template with structure, evidence standards and review steps, 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 design files.\n2. **Short-term:** Complete the workflow steps and record outcomes against prototype test pass rates.\n3. **Medium-term:** Review results, close actions, and update local procedures in design offices, factories and test facilities.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| prototype test pass rates | Agree a local target and track the trend | Measured from design files and reviewed on a set cycle |\n| design change counts | Agree a local target and track the trend | Measured from design files and reviewed on a set cycle |\n| failure rates in service | Agree a local target and track the trend | Measured from design files and reviewed on a set cycle |\n| project milestones | Agree a local target and track the trend | Measured from design files and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: component failures.\n- Never let this happen: test safety incidents.\n- Never let this happen: design tolerance errors.\n- Work only within the competence and authority of a mechanical engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design offices, factories and test facilities'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 mechanical engineer in design offices, factories and test facilities applies this workflow for manufacturing and product clients: they open\ndesign files, work through the five steps using CAD software, and close by recording\nthe outcome against prototype test pass rates and agreeing the next review date. (Illustrative example only —\nreplace with the real details of the case in hand.)\n","# Formal Report Writing — Mechanical Engineering\n\nWrite formal reports as a mechanical engineer that stand up to scrutiny from any reader. The deliverable is a report template with structure, evidence standards and review steps.\nThis skill is written for a mechanical engineer working with manufacturing and product clients in design offices, factories and test facilities.\n\n## When to use\n- You are a mechanical engineer preparing, delivering or reviewing this part of your work in design offices, factories and test facilities.\n- You need a defensible, repeatable approach that produces a report template with structure, evidence standards and review steps.\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| Tolerance | the permitted variation in a dimension |\n| Fatigue | weakening of material from repeated loading |\n| Prototype | an early version built to test a design |\n\n## Workflow\n1. **Step 1** - Establish the report's purpose, audience and deadline before writing; gather source material from design files\n2. **Step 2** - Structure: summary, background, method, findings, analysis, recommendations — in that order\n3. **Step 3** - Write findings factually and separately from opinion; label professional judgement as judgement\n4. **Step 4** - Support key points with evidence and with prototype test pass rates where outcomes are claimed; acknowledge limitations openly\n5. **Step 5** - Proofread for accuracy and tone, check names, dates and figures twice, and consider component failures before release\n\n## Profession-Specific Components\n| Component | Details for Mechanical Engineering |\n|-----------|-------------------------------|\n| Core documentation | design files; test reports; maintenance analyses; specifications |\n| Core tools & equipment | CAD software; simulation tools; test rigs; measurement instruments |\n| People involved | manufacturing and product clients; the mechanical engineer; colleagues and other services in design offices, factories and test facilities |\n| Primary record | design files — keep it current, dated and attributable |\n\n## Output Format\n**Context:** [Situation in design offices, factories and test facilities] | **Objective:** [What this must achieve] | **Audience:** [manufacturing and product clients and other stakeholders]\n\nThe finished output is a report template with structure, evidence standards and review steps, 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 design files.\n2. **Short-term:** Complete the workflow steps and record outcomes against prototype test pass rates.\n3. **Medium-term:** Review results, close actions, and update local procedures in design offices, factories and test facilities.\n\n## Success Metrics\n| Metric | Target | Method |\n|--------|--------|--------|\n| prototype test pass rates | Agree a local target and track the trend | Measured from design files and reviewed on a set cycle |\n| design change counts | Agree a local target and track the trend | Measured from design files and reviewed on a set cycle |\n| failure rates in service | Agree a local target and track the trend | Measured from design files and reviewed on a set cycle |\n| project milestones | Agree a local target and track the trend | Measured from design files and reviewed on a set cycle |\n\n## Guardrails & Quality Checks\n- Never let this happen: component failures.\n- Never let this happen: test safety incidents.\n- Never let this happen: design tolerance errors.\n- Work only within the competence and authority of a mechanical engineer; escalate or refer anything beyond it.\n- Record facts and observations, not speculation, and keep records confidential to design offices, factories and test facilities'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 mechanical engineer in design offices, factories and test facilities applies this workflow for manufacturing and product clients: they open\ndesign files, work through the five steps using CAD software, and close by recording\nthe outcome against prototype test pass rates 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":57,"category":58,"description":59},1,"Mechanical Engineering","Write formal reports as a mechanical engineer that stand up to scrutiny from any reader.\nTRIGGERS - Use when a mechanical engineer needs a formal report writing for manufacturing and product clients in design offices, factories and test facilities.\n","main","c605eae5729892d78c0b76dfdd58d3533bb26a91","skills\u002Fmechanical-engineering-formal-report-writing",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":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add lionelsimai\u002Fclaude-skills-collection --skill mechanical-engineering-formal-report-writing",{"tool":75,"command":76},"bunx","bunx skills add lionelsimai\u002Fclaude-skills-collection --skill mechanical-engineering-formal-report-writing",{"tool":78,"command":79},"pnpm","pnpm dlx skills add lionelsimai\u002Fclaude-skills-collection --skill mechanical-engineering-formal-report-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flionelsimai\u002Fclaude-skills-collection\u002Fblob\u002Fmain\u002Fskills\u002Fmechanical-engineering-formal-report-writing\u002FSKILL.md",true,[],[84,105,118,131,146,160],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":52},"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",[],[91,92,93,94,95,96,50,97,98,99,44,100,45,101,47,102,103,104],"youth work troubleshooting guide","work","troubleshooting","troubleshooting guide","guide","problem solving","outreach","settings","common","people","worker","diagnose","problem","communities",{"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":52},"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",[],[112,92,113,114,44,100,45,115,101,47,116,50,104,117,97,98],"youth work tools equipment checklist","checklist","Tools","maintain","select","check",{"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":124,"publishedAt":52},"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",[],[125,126,92,127,128,97,98,100,45,101,47,129,130,50,104,44],"procurement","youth work supplies procurement","materials","source","specify","manage",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":135,"categories":136,"keywords":140,"publishedAt":52},"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",[137],{"categoryNo":138,"categoryName":139,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000003","演示文稿",[141,92,142,143,50,144,104,47,145,97,98,44,100,45,101],"youth work stakeholder presentation","presentation","decision","proposals","present",{"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":152,"publishedAt":52},"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",[],[153,154,155,92,156,98,95,157,97,44,100,45,101,47,50,158,159,104],"delivery","work session","session","youth work session delivery","prepare","professional","deliver",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":169,"publishedAt":52},"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",[166],{"categoryNo":167,"categoryName":168,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",[92,170,171,172,50,47,101,46,51,104,98,97,100,45,44],"service","plan","youth work service plan"]