[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M741TSP17DN5Q3BVXX64SNVM":3,"skill-same:01M741TSP17DN5Q3BVXX64SNVM":52},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M741TSP17DN5Q3BVXX64SNVM","engineer-subsystem",null,"Turn a mechanical design brief into a saved CAD study, author or revise its model, and preserve requirements and failed measurements through Text-to-CAD.","openai\u002Fcommunity-plugins","openai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14957082?v=4","01M6AC29YGCR4S2NTJFV0G8B81","OpenAI","01M6AC5WQR6C9PX4PQWD6S1KTD",21,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fphysical-engineering\u002Fskills\u002Fengineer-subsystem\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: engineer-subsystem\ndescription: Turn a mechanical design brief into a saved CAD study, author or revise its model, and preserve requirements and failed measurements through Text-to-CAD.\n---\n\n# Engineer a subsystem\n\nUse this workflow for a new mechanical part or the bundled drone assembly.\nRead [the brief](..\u002F..\u002Freferences\u002Fbrief-template.md) and\n[compatibility](..\u002F..\u002Freferences\u002Fcompatibility.md). Resolve the plugin root two\ndirectories above this skill; assets must work from the installed package.\n\n## Establish the study\n\n1. Resolve the user's goal, interfaces, material assumptions and acceptance\n   limits. Record unresolved requirements. Choose `mechanical-part` for a custom\n   single-solid part with supported measurements, or `drone-module` only for the\n   two-part example. Do not force a new project into the drone dimensions.\n2. Use `scripts\u002Fengineering.py`. Inspect `--help` as needed. New studies need an\n   empty directory. Resume existing studies with `resume STUDY`; `study.json`\n   is authoritative and `context.md` is a generated summary.\n3. Check Python 3.14 and `PE_RUNTIME`. If needed, explain the dependency download\n   and use `setup --runtime DIR` in an authorized location. Preserve existing CAD\n   installations and respect host permissions.\n4. For a custom part, follow the [model and requirements contract](..\u002F..\u002Freferences\u002Fcustom-part.md),\n   then run `init STUDY --profile mechanical-part --requirements FILE`. Omitting\n   the file provides a sensor plate starter. Save the functional brief and\n   unresolved requirements in `src\u002Fbrief.md` so handoffs retain them. Use `init STUDY --profile drone-module`\n   for the [drone brief](..\u002F..\u002Freferences\u002Fdrone-brief.md).\n\n## Author and revise\n\nImplement the accepted brief in the study's `src\u002Fmodel.py` and export source.\nThe generic starter constructs a plate; replace it for another shape. Keep its\nexport contract. Use the separately installed Text-to-CAD authoring\u002Fviewing\ncapabilities for CAD work. Inspect externally supplied Python before execution.\n\nRun `build STUDY`, then use `verify-engineering-design`. Model declarations and\nrendered appearance are not acceptance measurements. A property unsupported by\nthe checker needs a separate measurement method; retain it as unresolved.\n\nFor a custom part, save revised requirements and run\n`change STUDY --requirements FILE --reason TEXT`. For the drone example, use\n`--battery B` or `--frame-pitch-x 110`. Never edit the installed checker or weaken\nacceptance limits to make geometry pass. A changed requirement does not update\nold geometry: verify it first, retain the actual result, then revise and build.\n\nKeep failed runs. Routine repairs within the brief need no further approval;\nconflicting requirements need an explicit decision before alteration. Record\nreal interventions; unknown usage or cost stays unknown.\n\n## Return\n\nSummarize the selected profile\u002Frun, requirement revision, measured results and\nnext action. Show the actual CAD view when available. Use\n`prepare-engineering-handoff` to regenerate deliveries. Distinguish the measured\ngeometry from unresolved manufacturing, structural and other physical checks.\n","# Engineer a subsystem\n\nUse this workflow for a new mechanical part or the bundled drone assembly.\nRead [the brief](..\u002F..\u002Freferences\u002Fbrief-template.md) and\n[compatibility](..\u002F..\u002Freferences\u002Fcompatibility.md). Resolve the plugin root two\ndirectories above this skill; assets must work from the installed package.\n\n## Establish the study\n\n1. Resolve the user's goal, interfaces, material assumptions and acceptance\n   limits. Record unresolved requirements. Choose `mechanical-part` for a custom\n   single-solid part with supported measurements, or `drone-module` only for the\n   two-part example. Do not force a new project into the drone dimensions.\n2. Use `scripts\u002Fengineering.py`. Inspect `--help` as needed. New studies need an\n   empty directory. Resume existing studies with `resume STUDY`; `study.json`\n   is authoritative and `context.md` is a generated summary.\n3. Check Python 3.14 and `PE_RUNTIME`. If needed, explain the dependency download\n   and use `setup --runtime DIR` in an authorized location. Preserve existing CAD\n   installations and respect host permissions.\n4. For a custom part, follow the [model and requirements contract](..\u002F..\u002Freferences\u002Fcustom-part.md),\n   then run `init STUDY --profile mechanical-part --requirements FILE`. Omitting\n   the file provides a sensor plate starter. Save the functional brief and\n   unresolved requirements in `src\u002Fbrief.md` so handoffs retain them. Use `init STUDY --profile drone-module`\n   for the [drone brief](..\u002F..\u002Freferences\u002Fdrone-brief.md).\n\n## Author and revise\n\nImplement the accepted brief in the study's `src\u002Fmodel.py` and export source.\nThe generic starter constructs a plate; replace it for another shape. Keep its\nexport contract. Use the separately installed Text-to-CAD authoring\u002Fviewing\ncapabilities for CAD work. Inspect externally supplied Python before execution.\n\nRun `build STUDY`, then use `verify-engineering-design`. Model declarations and\nrendered appearance are not acceptance measurements. A property unsupported by\nthe checker needs a separate measurement method; retain it as unresolved.\n\nFor a custom part, save revised requirements and run\n`change STUDY --requirements FILE --reason TEXT`. For the drone example, use\n`--battery B` or `--frame-pitch-x 110`. Never edit the installed checker or weaken\nacceptance limits to make geometry pass. A changed requirement does not update\nold geometry: verify it first, retain the actual result, then revise and build.\n\nKeep failed runs. Routine repairs within the brief need no further approval;\nconflicting requirements need an explicit decision before alteration. Record\nreal interventions; unknown usage or cost stays unknown.\n\n## Return\n\nSummarize the selected profile\u002Frun, requirement revision, measured results and\nnext action. Show the actual CAD view when available. Use\n`prepare-engineering-handoff` to regenerate deliveries. Distinguish the measured\ngeometry from unresolved manufacturing, structural and other physical checks.\n",{"name":5,"description":7},"main","6ab9f2066b527e6bc295f638c5b74553a4bf5e05","plugins\u002Fphysical-engineering\u002Fskills\u002Fengineer-subsystem",15,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins","https:\u002F\u002Fgithub.com\u002Fopenai","https:\u002F\u002Fopenai.com\u002F","2026-11-14 05:35:20",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add openai\u002Fcommunity-plugins --skill engineer-subsystem",{"tool":38,"command":39},"bunx","bunx skills add openai\u002Fcommunity-plugins --skill engineer-subsystem",{"tool":41,"command":42},"pnpm","pnpm dlx skills add openai\u002Fcommunity-plugins --skill engineer-subsystem","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fphysical-engineering\u002Fskills\u002Fengineer-subsystem\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",297,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fphysical-engineering\u002Fskills\u002Fengineer-subsystem\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M741V08QRD12ZRG78X6ZH6D3","verify-engineering-design","Measure a study's CAD exports against its saved requirements, preserving failed or unknown results and the source, checker and artifact provenance.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fphysical-engineering\u002Fskills\u002Fverify-engineering-design\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M741TWYZF1PEH77QR1AJC915","prepare-engineering-handoff","Regenerate a study's checked CAD, source, measurements and BOM, then rebuild the delivered package in a separate destination and compare the results.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fphysical-engineering\u002Fskills\u002Fprepare-engineering-handoff\u002FSKILL.md",[],[],{"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":19},"01M741TPJKGDYSWKJ834P9H7JY","revise-pcba-assembly","Preview and apply a bounded, revision-bound PCBA placement or population correction using explicit authoritative geometry, then regenerate and recheck the assembly package.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fpcba-engineering\u002Fskills\u002Frevise-pcba-assembly\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M741TKEG2QA7NY6ZF3NHTSWH","review-pcba-package","Review supplied PCB assembly BOM and placement data, reconcile population and geometry evidence, and create a persistent local PCBA project with an offline visual assembly guide.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fpcba-engineering\u002Fskills\u002Freview-pcba-package\u002FSKILL.md",[],[],{"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":19},"01M741TH8XA8DAQ9SYMGCK5RMS","prepare-pcba-handoff","Export a consistent PCBA project into an immutable offline assembly packet and independently re-read its BOM, placements, provenance and artifact hashes before delivery.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fpcba-engineering\u002Fskills\u002Fprepare-pcba-handoff\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":99},"01M6AC730FQT0TJT60GJ8GZ368","recommend-review-reference-architecture","Recommend a conservative shadow-only review reference architecture from valid offline evidence. Use only when the user explicitly asks for a reference-architecture recommendation or uses the bundled synthetic fixture.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freviewops-auditor-benchmark\u002Fskills\u002Frecommend-review-reference-architecture\u002FSKILL.md",[],[95,96,97,98],"recommend review reference architecture","architecture","review","valid","2026-11-10 10:12:30"]