[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AC61ACZ2TDR2RE1G2PVQV5":3,"skill-same:01M6AC61ACZ2TDR2RE1G2PVQV5":58},{"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":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M6AC61ACZ2TDR2RE1G2PVQV5","handoff-fusion-engineering",null,"Prepare a traceable local Fusion engineering review draft with source identities, artifacts and unresolved assurance gates. Not for sending, publication or release approval.","openai\u002Fcommunity-plugins","openai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14957082?v=4","01M6AC29YGCR4S2NTJFV0G8B81","OpenAI","01M6AC5WQR6C9PX4PQWD6S1KTD",20,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fautodesk-fusion\u002Fskills\u002Fhandoff-fusion-engineering\u002FSKILL.md",[],[19,20,21,22,23,24],"handoff","handoff fusion engineering","review","prepare","release","artifacts","2026-11-10 10:12:30",false,"---\nname: handoff-fusion-engineering\ndescription: Prepare a traceable local Fusion engineering review draft with source identities, artifacts and unresolved assurance gates. Not for sending, publication or release approval.\n---\n\nUse `fusion_handoff_prepare` to assemble the user's review evidence, and `fusion_handoff_inspect` to check an existing draft against current source and stored receipt state. Read [the handoff contract](..\u002F..\u002Fdocs\u002Fhandoffs.md) when composing structured checks or interpreting freshness failures.\n\nThe accepted fields are `title`, `plan_ids`, `document_ids`, `requirements`, `assumptions`, `reviewers`, `checks` and `external_evidence`. Only the title is required; missing requirements, sources and checks stay explicit. Select actual producing plans to retain artifact and pending\u002Funcertain job evidence. Do not invent unsupported `job_ids`, solver-result fields or approval flags.\n\nDiscover the active operation schemas and inspect the actual response before choosing check pointers. Automated handoff checks are limited to `document.inspect`, `parameters.list`, `geometry.measure`, `geometry.check` and `cam.inspect`. Numeric ranges require a value pointer and an exact observed unit pointer\u002Fstring; there is no implicit unit conversion. Use identity assertions alongside array positions when the measured parameter or entity matters. Do not select credential fields or infer equality from redaction placeholders; rejected or redaction-altered comparisons cannot establish a result. Fixture values and response shapes do not qualify a live Fusion check.\n\nLink requirements and reviewer IDs explicitly. Use manual procedures for unavailable solver, simulation, drawing, ECAD or engineering review work; they remain `not_run`. External evidence references and reported hashes are unfetched, unverified metadata. Reviewer assignments do not authenticate reviewers, notify them or record approval.\n\nKnown `freshness_gaps`, malformed coverage, changed source states and missing fingerprints prevent current use of dependent checks. A linked artifact must match its exact producing plan, document, preparation\u002Fcompletion source and implementation contract; an old-source or legacy receipt remains historical. Keep failed, pending and unknown plan outcomes visible. Do not rewrite a stored draft, drop unresolved evidence or refresh a stale assertion into a pass. Collect new observations into a new draft when the task calls for current evidence, keeping the original for comparison.\n\nReturn the local draft reference, its evidence scope and the unresolved decisions with their practical impact. A met criterion, screenshot, generated toolpath, setup sheet or provider success is not engineering, machine-collision or regulatory proof. These tools do not send the draft, publish artifacts, update enterprise systems or advance a release. Such actions require their own destination authority and qualified adapter; preparing an already authorized local draft does not require repetitive permission requests.\n","Use `fusion_handoff_prepare` to assemble the user's review evidence, and `fusion_handoff_inspect` to check an existing draft against current source and stored receipt state. Read [the handoff contract](..\u002F..\u002Fdocs\u002Fhandoffs.md) when composing structured checks or interpreting freshness failures.\n\nThe accepted fields are `title`, `plan_ids`, `document_ids`, `requirements`, `assumptions`, `reviewers`, `checks` and `external_evidence`. Only the title is required; missing requirements, sources and checks stay explicit. Select actual producing plans to retain artifact and pending\u002Funcertain job evidence. Do not invent unsupported `job_ids`, solver-result fields or approval flags.\n\nDiscover the active operation schemas and inspect the actual response before choosing check pointers. Automated handoff checks are limited to `document.inspect`, `parameters.list`, `geometry.measure`, `geometry.check` and `cam.inspect`. Numeric ranges require a value pointer and an exact observed unit pointer\u002Fstring; there is no implicit unit conversion. Use identity assertions alongside array positions when the measured parameter or entity matters. Do not select credential fields or infer equality from redaction placeholders; rejected or redaction-altered comparisons cannot establish a result. Fixture values and response shapes do not qualify a live Fusion check.\n\nLink requirements and reviewer IDs explicitly. Use manual procedures for unavailable solver, simulation, drawing, ECAD or engineering review work; they remain `not_run`. External evidence references and reported hashes are unfetched, unverified metadata. Reviewer assignments do not authenticate reviewers, notify them or record approval.\n\nKnown `freshness_gaps`, malformed coverage, changed source states and missing fingerprints prevent current use of dependent checks. A linked artifact must match its exact producing plan, document, preparation\u002Fcompletion source and implementation contract; an old-source or legacy receipt remains historical. Keep failed, pending and unknown plan outcomes visible. Do not rewrite a stored draft, drop unresolved evidence or refresh a stale assertion into a pass. Collect new observations into a new draft when the task calls for current evidence, keeping the original for comparison.\n\nReturn the local draft reference, its evidence scope and the unresolved decisions with their practical impact. A met criterion, screenshot, generated toolpath, setup sheet or provider success is not engineering, machine-collision or regulatory proof. These tools do not send the draft, publish artifacts, update enterprise systems or advance a release. Such actions require their own destination authority and qualified adapter; preparing an already authorized local draft does not require repetitive permission requests.\n",{"name":5,"description":7},"main","62844ca1cd865b76c7fed7180fc1ffef16e9167b","plugins\u002Fautodesk-fusion\u002Fskills\u002Fhandoff-fusion-engineering",14,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins","https:\u002F\u002Fgithub.com\u002Fopenai","https:\u002F\u002Fopenai.com\u002F","2026-11-11 07:06:15",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add openai\u002Fcommunity-plugins --skill handoff-fusion-engineering",{"tool":44,"command":45},"bunx","bunx skills add openai\u002Fcommunity-plugins --skill handoff-fusion-engineering",{"tool":47,"command":48},"pnpm","pnpm dlx skills add openai\u002Fcommunity-plugins --skill handoff-fusion-engineering","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fautodesk-fusion\u002Fskills\u002Fhandoff-fusion-engineering\u002FSKILL.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"agents\u002Fopenai.yaml","REFERENCE","参考文档",221,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fautodesk-fusion\u002Fskills\u002Fhandoff-fusion-engineering\u002Fagents\u002Fopenai.yaml",[59,69,79,88,97,110],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":25},"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",[],[66,67,21,68],"recommend review reference architecture","architecture","valid",{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":25},"01M6AC70XH1PBTCTMM65PBTGGQ","normalize-review-runs","Validate and normalize declared local review-run exports into a bounded canonical summary. Use only when the user explicitly asks to normalize review runs or use the bundled synthetic fixture.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freviewops-auditor-benchmark\u002Fskills\u002Fnormalize-review-runs\u002FSKILL.md",[],[76,21,77,78],"normalize review runs","validate","run",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":25},"01M6AC6ZAD4YMQVGM0KD5EEVX1","benchmark-review-configs","Deterministically score comparable imported review-run lanes with root-cause metrics and uncertainty. Use only when the user explicitly asks to benchmark normalized local review runs or use the bundled synthetic fixture.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freviewops-auditor-benchmark\u002Fskills\u002Fbenchmark-review-configs\u002FSKILL.md",[],[86,87,21,78],"benchmark review configs","benchmark",{"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":25},"01M6AC6X72JX5E4T3GRX8G63CR","audit-review-eval-validity","Audit whether a declared local review evaluation can support fair quality claims. Use only when the user explicitly asks to audit review-eval validity or use the bundled synthetic fixture.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freviewops-auditor-benchmark\u002Fskills\u002Faudit-review-eval-validity\u002FSKILL.md",[],[95,21,96],"audit review eval validity","support",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":108,"publishedAt":25},"01M6AC6VQ2RRQG8Y8B7G6XCC5A","verify-swiftui-parity","Verify one approved SwiftUI feature slice against its behavioral parity contract with deterministic and conditional Apple-platform checks.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freact-native-to-swiftui\u002Fskills\u002Fverify-swiftui-parity\u002FSKILL.md",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[109],"verify swiftui parity",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":122,"publishedAt":25},"01M6AC6SYEBFZJ2DVM44HEP64N","port-react-native-slice","Port one explicitly approved React Native or Expo feature slice into a declared SwiftUI target while preserving its parity contract.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fcommunity-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Freact-native-to-swiftui\u002Fskills\u002Fport-react-native-slice\u002FSKILL.md",[116,121],{"categoryNo":117,"categoryName":118,"taxonomyType":119,"taxonomyTypeDesc":120},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},[123,124],"react","port react native slice"]