[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79SCTEC6WPVYNJBZ1M53ZQZ":3,"skill-same:01M79SCTEC6WPVYNJBZ1M53ZQZ":63},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M79SCTEC6WPVYNJBZ1M53ZQZ","sendcutsend",null,"使用其订购指南、目录和规格查看 SendCutSend.com 订单的 DXF 和 STEP\u002FSTP 上传。仅用于 SendCutSend.com 预检报告，涵盖上传准备情况、所选材料\u002FSKU\u002F厚度\u002F服务可用性以及激光切割、CNC 铣削、弯曲、攻丝、埋头孔、硬件插入和精加工的特定服务检查。","zzz2929\u002Fskills-zh-CN","zzz2929","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145306978?v=4","01M79S11YZNA13C4SZEN9M9QH1","zxyzzz","01M79S1204VZEHJSESQE300A6N",0,"MIT","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fsendcutsend\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fsendcutsend\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sendcutsend\ndescription: 使用其订购指南、目录和规格查看 SendCutSend.com 订单的 DXF 和 STEP\u002FSTP 上传。仅用于 SendCutSend.com 预检报告，涵盖上传准备情况、所选材料\u002FSKU\u002F厚度\u002F服务可用性以及激光切割、CNC 铣削、弯曲、攻丝、埋头孔、硬件插入和精加工的特定服务检查。\n---\n# SendCutSend\n\nProvenance: maintained in [earthtojake\u002Ftext-to-cad](https:\u002F\u002Fgithub.com\u002Fearthtojake\u002Ftext-to-cad).\nUse the installed local skill files as the runtime source of truth; the\nrepository link is only for provenance and release review.\n\nUse this skill to produce conservative, evidence-backed SendCutSend preflight reports for DXF and STEP\u002FSTP files.\n\nTreat SendCutSend's ordering guide, catalog JSON, and specs JSON as evidence feeds, not stable APIs. Field names, types, and coverage may vary. Do not turn missing, unparsable, `N\u002FA`, or conflicting source data into a pass or fail. Fetch sources directly from official URLs and use local inspection code only to measure specific file facts; write the final report from explicit comparisons.\n\n## Geometry Inspection\n\nUse the active project Python environment for local geometry inspection code. If the `$cad` skill is available, use it first for STEP\u002FSTP\u002FDXF geometry inspection, measurement, and validation workflows, then add any SendCutSend-specific targeted measurements that are still missing. Use `build123d.import_step` for STEP\u002FSTP inspection and `build123d.ezdxf` for DXF inspection when geometry facts are required. Do not use raw text parsing or alternate geometry backends for geometry facts.\n\n## CAD Viewer Handoff\n\nAfter completing SendCutSend work that creates or modifies a `.dxf`, `.step`, or `.stp` upload candidate, you must ALWAYS hand the explicit file path(s) to `$cad-viewer` when that skill is installed. `$cad-viewer` must start CAD Viewer if it is not already running and return link(s) to the relevant created or updated file(s); if `$cad-viewer` is unavailable or startup fails, report that instead of silently omitting the handoff.\n\n## Official Sources\n\nBefore each review, fetch and inspect the current SendCutSend source documents directly from the official URLs listed in `references\u002Fofficial-sources.md`:\n\nUse the source URL, access date, and JSON `_meta` values in the source bibliography when helpful. If a source cannot be fetched, report that current SendCutSend sources were unavailable and avoid ready verdicts for dependent checks.\n\n## Workflow\n\n1. Collect order intent.\n   - Prefer DXF for laser sheet cutting and 2D sheet profiles.\n   - Prefer STEP\u002FSTP for CNC routing and 3D model upload workflows.\n   - Record file type, intended process, material\u002FSKU, thickness, quantity, services, finish, and hardware.\n   - If order context is missing or ambiguous, inspect enough source data to present concrete options, then ask the user to confirm before writing a readiness verdict. Include candidate SKUs\u002Fmaterials\u002Fthicknesses\u002Fservices with relevant source links; include `photo_url` images and `learn_more_url` links from the specs JSON when available.\n2. Read `references\u002Fofficial-sources.md`, fetch the official sources directly, then inspect the returned documents. Normalize source facts defensively: parse numeric strings, size strings, `N\u002FA`, missing fields, mixed types, and absent service arrays into explicit notes.\n3. Inspect the exact upload file with `$cad` when available and with targeted Python\u002F`build123d` for any missing facts. Do not inspect only the source generator, CAD model, or generator console summary.\n   - DXF: measure units, bounds, layers, entity types, open\u002Fduplicate geometry, unsupported annotations, candidate holes\u002Fcircles, linework stats, bend-line candidates, bend-to-cut distances, bend-adjacent cut geometry, local flange depths, and degenerate zero-area contours as needed for the selected service.\n   - STEP\u002FSTP: measure parseability, units hints, solid\u002Fsurface signals, bounding box, shell\u002Fbody signals, validity, sheet thickness where available, cylindrical bend-face radii where bending is in scope, and limitations as needed for the selected service.\n   - Keep each inspection helper fact-only. It may report measurements, parse errors, and limitations, but it must not emit pass\u002Ffail\u002Freadiness statuses.\n4. Select source records by evidence quality.\n   - Use exact SKU as the only authoritative catalog\u002Fspec join.\n   - If only material and thickness are provided, use a selected material only when the candidate match is unique and exact enough; otherwise list candidates with links\u002Fimages from the source records and ask the user to choose.\n   - Use the catalog JSON for orderability: stock, cutting process, available services, size limits, hardware, and finishes.\n   - Use the specs JSON for engineering values: tolerances, holes, bridges, bending, tapping, countersinking, hardware insertion, finishing, and material properties.\n   - Use the ordering guide for plain-language workflow and general file-format rules.\n\n## Comparison\n\nCompare only trustworthy pairs of evidence.\n\n- Determine whether a check applies.\n- Cite the source field path or guide section.\n- Cite the measured file fact.\n- Compare only when both the source requirement and measured file fact are available and trustworthy.\n- If a needed measurement is missing or risky, write a small targeted `build123d`\u002F`ezdxf` inspector for that specific geometry fact.\n- Treat every measured upload risk, manufacturability issue, or cited requirement violation as an error for now. Do not infer any alternate SendCutSend UI classification.\n- For DXF units, inspect `$INSUNITS`, header extents, measured bounds, and order context together. If `$INSUNITS` is missing, unsupported, or not one of the SendCutSend guide's expected DXF unit codes (`1` inches or `4` mm), report a unit\u002Fscale error and recommend re-exporting or confirming units before applying size-, flange-, or material-specific comparisons. Do not silently rescale geometry or use an uncertain scale to issue material-specific pass\u002Ffail checks.\n- For 2D files with bend lines, check flange length locally along every bend line. Measure the nearest cut\u002Ffree edge on both sides of each bend at each span or sample point, including notches, slots, gaps, split tabs, and cutouts that interrupt the bend span or create a local free edge. Compare the minimum local flange depth to the selected SKU's `bending_specs.min_flange_length_before_bend` and `bending_specs.min_flange_length_after_bend`. Do not apply flange-length limits to ordinary enclosed holes or interior cutouts unless a cited source gives a hole-to-bend or feature-to-bend rule for that service; report those separately with centerline-to-bend or edge-to-bend measurements as the cited rule requires. Do not treat nearby bend-adjacent cut geometry as only corner relief unless the remaining local flange still passes the flange-length minimum. If any local flange depth is below the SKU minimum, report `❌ fail`. Do not rely on aggregate source-level values when exported geometry has local cutouts, interrupted bends, split bend segments, reliefs, tabs, or unsupported regions.\n- Keep bend findings separate by physical cause. Do not collapse bend-adjacent geometry into a generic flange failure. Report distinct rows for minimum flange\u002Fcontact length errors, bend line or die-area geometry crossings, insufficient bend contact\u002Fsupport from nearby free edges or cutouts, bend lines that do not span the bent region, split\u002Fcommon-axis bend segments, and cut geometry touching or crossing bend lines. If a SendCutSend source does not expose the exact die-area\u002Fcontact threshold, cite the measured file fact as direct file inspection and mark the source-limited comparison explicitly.\n- For STEP\u002FSTP bent parts, inspect bend radii when the model contains sheet-metal bend geometry or the intended service includes bending. Extract cylindrical or toroidal bend faces and their radii with `$cad`\u002F`build123d`\u002FOCP where possible, group repeated bend radii, and compare them to the selected SKU's `bending_specs.effective_bend_radius` or `bending_specs.bend_radius`. If the selected material\u002FSKU is unknown, report the measured bend-radius set and ask for material\u002Fthickness before readiness verdicts. If measured radii conflict with the selected SKU tooling radius, report a bend-radius mismatch error.\n\nReport with restrained status labels:\n\n- `✅ pass`: the measured file fact satisfies the cited current requirement.\n- `❌ fail`: a measured upload risk, manufacturability issue, or direct measured violation of a cited current requirement.\n- `❓ need more info`: missing context, missing source evidence, unmeasured geometry, source conflicts, or tool limitations.\n\n## Diagnostic Images\n\nWhen findings would be easier to understand visually, produce a concise diagnostic diagram proactively if image-generation or image-editing capabilities are available. Use generated or edited images for callouts, legends, and before\u002Fafter explanations. Do this without waiting for the user to ask whenever there is a `❌ fail`, a spatially ambiguous geometry issue, or a geometry edit that needs a before\u002Fafter explanation. If image-generation tools are unavailable, state that limitation and describe the intended diagram in the report.\n\nBefore generating an image, run a layout preflight:\n\n- Choose the smallest set of callouts needed to explain the fix.\n- Estimate whether labels will crowd the geometry, overlap each other, or run outside the canvas. If crowding is likely, flag it before generation and switch to numbered markers plus a side legend, a larger canvas, or separate detail views.\n- Keep long measured values and rule text in the legend, not directly over dense geometry.\n- Include the measured failing distance, the cited minimum, and the proposed movement or clearance target.\n\nAfter generating an image, inspect the rendered image before delivery. If labels overlap, are clipped, are hard to read, or obscure the geometry, regenerate or revise the diagram before reporting it.\n\n## DXF Review\n\nFor laser sheet cutting, start from the refreshed sources and measured DXF geometry facts.\n\nCheck for:\n\n- single, uploadable DXF file with model geometry at 1:1 scale\n- units and overall part size; treat missing, unsupported, or unexpected `$INSUNITS` as a scale error until the user confirms units\n- closed cut profiles where the service requires closed contours\n- degenerate or zero-area closed contours, two-point closed polylines, and odd-degree cut endpoints\n- duplicate or overlapping cut geometry\n- unsupported annotation, text, dimensions, images, construction lines, or hidden instruction layers\n- layer\u002Fcolor\u002Flinework conventions from the ordering guide and upload workflow\n- bend-line entities, bend segment lengths, split\u002Fcommon-axis bends, local flange depth on both sides of each bend line, nearest non-bend cut edge or cutout distances, bend-line span coverage, insufficient bend contact\u002Fsupport, die-area or bend-adjacent cut geometry crossings, and cut geometry touching or crossing bend lines when bending is in scope\n- minimum holes, slots, web widths, interior geometry, part density, nesting, and spacing only when both source facts and measured file facts support a comparison\n- secondary-service requirements for bending, tapping, countersinking, hardware, finishing, or deburring when requested\n\n## STEP Review\n\nFor CNC routing or 3D model upload, start from the refreshed sources and measured STEP geometry facts.\n\nCheck for:\n\n- STEP\u002FSTP file readability and a solid body rather than loose curves or surfaces\n- units, scale, bounding box, thickness, and feature dimensions\n- sheet-metal bend radii when bending is in scope; compare measured cylindrical bend-face radii to the selected SKU's `bending_specs.effective_bend_radius` or `bending_specs.bend_radius`\n- sharp inside corners, small holes\u002Fslots, thin walls, islands, deep pockets, tool access, and tolerances only when the file inspection can measure the fact\n- whether geometry represents a sheet profile better served as DXF for laser cutting\n- material, thickness, finish, and secondary-service compatibility\n\n## Reporting\n\nInclude the file path, assumed service, material\u002Forder context, source files checked with access date, inspected geometry facts, findings ordered by practical impact, and specific next edits. In the findings table, include a `Rule source` column with Markdown links to the source URL plus the specific JSON field path or guide section used for that row. If a row is based only on direct file inspection and has no external rule, say `Direct file inspection`; do not leave the source blank. Do not call a file \"SendCutSend ready\" unless every required cited check either passes or is explicitly outside the selected service.\n\nUse `references\u002Freport-template.md` when a structured report would help.\n\n## References\n\n- Official source selection: `references\u002Fofficial-sources.md`\n- Report shape: `references\u002Freport-template.md`\n","# SendCutSend\n\nProvenance: maintained in [earthtojake\u002Ftext-to-cad](https:\u002F\u002Fgithub.com\u002Fearthtojake\u002Ftext-to-cad).\nUse the installed local skill files as the runtime source of truth; the\nrepository link is only for provenance and release review.\n\nUse this skill to produce conservative, evidence-backed SendCutSend preflight reports for DXF and STEP\u002FSTP files.\n\nTreat SendCutSend's ordering guide, catalog JSON, and specs JSON as evidence feeds, not stable APIs. Field names, types, and coverage may vary. Do not turn missing, unparsable, `N\u002FA`, or conflicting source data into a pass or fail. Fetch sources directly from official URLs and use local inspection code only to measure specific file facts; write the final report from explicit comparisons.\n\n## Geometry Inspection\n\nUse the active project Python environment for local geometry inspection code. If the `$cad` skill is available, use it first for STEP\u002FSTP\u002FDXF geometry inspection, measurement, and validation workflows, then add any SendCutSend-specific targeted measurements that are still missing. Use `build123d.import_step` for STEP\u002FSTP inspection and `build123d.ezdxf` for DXF inspection when geometry facts are required. Do not use raw text parsing or alternate geometry backends for geometry facts.\n\n## CAD Viewer Handoff\n\nAfter completing SendCutSend work that creates or modifies a `.dxf`, `.step`, or `.stp` upload candidate, you must ALWAYS hand the explicit file path(s) to `$cad-viewer` when that skill is installed. `$cad-viewer` must start CAD Viewer if it is not already running and return link(s) to the relevant created or updated file(s); if `$cad-viewer` is unavailable or startup fails, report that instead of silently omitting the handoff.\n\n## Official Sources\n\nBefore each review, fetch and inspect the current SendCutSend source documents directly from the official URLs listed in `references\u002Fofficial-sources.md`:\n\nUse the source URL, access date, and JSON `_meta` values in the source bibliography when helpful. If a source cannot be fetched, report that current SendCutSend sources were unavailable and avoid ready verdicts for dependent checks.\n\n## Workflow\n\n1. Collect order intent.\n   - Prefer DXF for laser sheet cutting and 2D sheet profiles.\n   - Prefer STEP\u002FSTP for CNC routing and 3D model upload workflows.\n   - Record file type, intended process, material\u002FSKU, thickness, quantity, services, finish, and hardware.\n   - If order context is missing or ambiguous, inspect enough source data to present concrete options, then ask the user to confirm before writing a readiness verdict. Include candidate SKUs\u002Fmaterials\u002Fthicknesses\u002Fservices with relevant source links; include `photo_url` images and `learn_more_url` links from the specs JSON when available.\n2. Read `references\u002Fofficial-sources.md`, fetch the official sources directly, then inspect the returned documents. Normalize source facts defensively: parse numeric strings, size strings, `N\u002FA`, missing fields, mixed types, and absent service arrays into explicit notes.\n3. Inspect the exact upload file with `$cad` when available and with targeted Python\u002F`build123d` for any missing facts. Do not inspect only the source generator, CAD model, or generator console summary.\n   - DXF: measure units, bounds, layers, entity types, open\u002Fduplicate geometry, unsupported annotations, candidate holes\u002Fcircles, linework stats, bend-line candidates, bend-to-cut distances, bend-adjacent cut geometry, local flange depths, and degenerate zero-area contours as needed for the selected service.\n   - STEP\u002FSTP: measure parseability, units hints, solid\u002Fsurface signals, bounding box, shell\u002Fbody signals, validity, sheet thickness where available, cylindrical bend-face radii where bending is in scope, and limitations as needed for the selected service.\n   - Keep each inspection helper fact-only. It may report measurements, parse errors, and limitations, but it must not emit pass\u002Ffail\u002Freadiness statuses.\n4. Select source records by evidence quality.\n   - Use exact SKU as the only authoritative catalog\u002Fspec join.\n   - If only material and thickness are provided, use a selected material only when the candidate match is unique and exact enough; otherwise list candidates with links\u002Fimages from the source records and ask the user to choose.\n   - Use the catalog JSON for orderability: stock, cutting process, available services, size limits, hardware, and finishes.\n   - Use the specs JSON for engineering values: tolerances, holes, bridges, bending, tapping, countersinking, hardware insertion, finishing, and material properties.\n   - Use the ordering guide for plain-language workflow and general file-format rules.\n\n## Comparison\n\nCompare only trustworthy pairs of evidence.\n\n- Determine whether a check applies.\n- Cite the source field path or guide section.\n- Cite the measured file fact.\n- Compare only when both the source requirement and measured file fact are available and trustworthy.\n- If a needed measurement is missing or risky, write a small targeted `build123d`\u002F`ezdxf` inspector for that specific geometry fact.\n- Treat every measured upload risk, manufacturability issue, or cited requirement violation as an error for now. Do not infer any alternate SendCutSend UI classification.\n- For DXF units, inspect `$INSUNITS`, header extents, measured bounds, and order context together. If `$INSUNITS` is missing, unsupported, or not one of the SendCutSend guide's expected DXF unit codes (`1` inches or `4` mm), report a unit\u002Fscale error and recommend re-exporting or confirming units before applying size-, flange-, or material-specific comparisons. Do not silently rescale geometry or use an uncertain scale to issue material-specific pass\u002Ffail checks.\n- For 2D files with bend lines, check flange length locally along every bend line. Measure the nearest cut\u002Ffree edge on both sides of each bend at each span or sample point, including notches, slots, gaps, split tabs, and cutouts that interrupt the bend span or create a local free edge. Compare the minimum local flange depth to the selected SKU's `bending_specs.min_flange_length_before_bend` and `bending_specs.min_flange_length_after_bend`. Do not apply flange-length limits to ordinary enclosed holes or interior cutouts unless a cited source gives a hole-to-bend or feature-to-bend rule for that service; report those separately with centerline-to-bend or edge-to-bend measurements as the cited rule requires. Do not treat nearby bend-adjacent cut geometry as only corner relief unless the remaining local flange still passes the flange-length minimum. If any local flange depth is below the SKU minimum, report `❌ fail`. Do not rely on aggregate source-level values when exported geometry has local cutouts, interrupted bends, split bend segments, reliefs, tabs, or unsupported regions.\n- Keep bend findings separate by physical cause. Do not collapse bend-adjacent geometry into a generic flange failure. Report distinct rows for minimum flange\u002Fcontact length errors, bend line or die-area geometry crossings, insufficient bend contact\u002Fsupport from nearby free edges or cutouts, bend lines that do not span the bent region, split\u002Fcommon-axis bend segments, and cut geometry touching or crossing bend lines. If a SendCutSend source does not expose the exact die-area\u002Fcontact threshold, cite the measured file fact as direct file inspection and mark the source-limited comparison explicitly.\n- For STEP\u002FSTP bent parts, inspect bend radii when the model contains sheet-metal bend geometry or the intended service includes bending. Extract cylindrical or toroidal bend faces and their radii with `$cad`\u002F`build123d`\u002FOCP where possible, group repeated bend radii, and compare them to the selected SKU's `bending_specs.effective_bend_radius` or `bending_specs.bend_radius`. If the selected material\u002FSKU is unknown, report the measured bend-radius set and ask for material\u002Fthickness before readiness verdicts. If measured radii conflict with the selected SKU tooling radius, report a bend-radius mismatch error.\n\nReport with restrained status labels:\n\n- `✅ pass`: the measured file fact satisfies the cited current requirement.\n- `❌ fail`: a measured upload risk, manufacturability issue, or direct measured violation of a cited current requirement.\n- `❓ need more info`: missing context, missing source evidence, unmeasured geometry, source conflicts, or tool limitations.\n\n## Diagnostic Images\n\nWhen findings would be easier to understand visually, produce a concise diagnostic diagram proactively if image-generation or image-editing capabilities are available. Use generated or edited images for callouts, legends, and before\u002Fafter explanations. Do this without waiting for the user to ask whenever there is a `❌ fail`, a spatially ambiguous geometry issue, or a geometry edit that needs a before\u002Fafter explanation. If image-generation tools are unavailable, state that limitation and describe the intended diagram in the report.\n\nBefore generating an image, run a layout preflight:\n\n- Choose the smallest set of callouts needed to explain the fix.\n- Estimate whether labels will crowd the geometry, overlap each other, or run outside the canvas. If crowding is likely, flag it before generation and switch to numbered markers plus a side legend, a larger canvas, or separate detail views.\n- Keep long measured values and rule text in the legend, not directly over dense geometry.\n- Include the measured failing distance, the cited minimum, and the proposed movement or clearance target.\n\nAfter generating an image, inspect the rendered image before delivery. If labels overlap, are clipped, are hard to read, or obscure the geometry, regenerate or revise the diagram before reporting it.\n\n## DXF Review\n\nFor laser sheet cutting, start from the refreshed sources and measured DXF geometry facts.\n\nCheck for:\n\n- single, uploadable DXF file with model geometry at 1:1 scale\n- units and overall part size; treat missing, unsupported, or unexpected `$INSUNITS` as a scale error until the user confirms units\n- closed cut profiles where the service requires closed contours\n- degenerate or zero-area closed contours, two-point closed polylines, and odd-degree cut endpoints\n- duplicate or overlapping cut geometry\n- unsupported annotation, text, dimensions, images, construction lines, or hidden instruction layers\n- layer\u002Fcolor\u002Flinework conventions from the ordering guide and upload workflow\n- bend-line entities, bend segment lengths, split\u002Fcommon-axis bends, local flange depth on both sides of each bend line, nearest non-bend cut edge or cutout distances, bend-line span coverage, insufficient bend contact\u002Fsupport, die-area or bend-adjacent cut geometry crossings, and cut geometry touching or crossing bend lines when bending is in scope\n- minimum holes, slots, web widths, interior geometry, part density, nesting, and spacing only when both source facts and measured file facts support a comparison\n- secondary-service requirements for bending, tapping, countersinking, hardware, finishing, or deburring when requested\n\n## STEP Review\n\nFor CNC routing or 3D model upload, start from the refreshed sources and measured STEP geometry facts.\n\nCheck for:\n\n- STEP\u002FSTP file readability and a solid body rather than loose curves or surfaces\n- units, scale, bounding box, thickness, and feature dimensions\n- sheet-metal bend radii when bending is in scope; compare measured cylindrical bend-face radii to the selected SKU's `bending_specs.effective_bend_radius` or `bending_specs.bend_radius`\n- sharp inside corners, small holes\u002Fslots, thin walls, islands, deep pockets, tool access, and tolerances only when the file inspection can measure the fact\n- whether geometry represents a sheet profile better served as DXF for laser cutting\n- material, thickness, finish, and secondary-service compatibility\n\n## Reporting\n\nInclude the file path, assumed service, material\u002Forder context, source files checked with access date, inspected geometry facts, findings ordered by practical impact, and specific next edits. In the findings table, include a `Rule source` column with Markdown links to the source URL plus the specific JSON field path or guide section used for that row. If a row is based only on direct file inspection and has no external rule, say `Direct file inspection`; do not leave the source blank. Do not call a file \"SendCutSend ready\" unless every required cited check either passes or is explicitly outside the selected service.\n\nUse `references\u002Freport-template.md` when a structured report would help.\n\n## References\n\n- Official source selection: `references\u002Fofficial-sources.md`\n- Report shape: `references\u002Freport-template.md`\n",{"name":5,"description":7},"main","9f046539cc7b77fcc2cdcc31dee08c104218a554","text-to-cad\u002Fsendcutsend","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN","https:\u002F\u002Fgithub.com\u002Fzzz2929","2026-09-29 15:32:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zzz2929\u002Fskills-zh-CN --skill sendcutsend",{"tool":37,"command":38},"bunx","bunx skills add zzz2929\u002Fskills-zh-CN --skill sendcutsend",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zzz2929\u002Fskills-zh-CN --skill sendcutsend","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fsendcutsend\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",210,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fsendcutsend\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":16},"LICENSE","许可证",1074,{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fofficial-sources.md",2212,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fsendcutsend\u002Freferences\u002Fofficial-sources.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Freport-template.md",3119,"https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Ftext-to-cad\u002Fsendcutsend\u002Freferences\u002Freport-template.md",[64,71,78,85,92,100],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":20},"01M79SG5BDV2ZDS4QA238B9ZCR","vercel-react-view-transitions","使用 React 的视图转换 API（`\u003CViewTransition>` 组件、`addTransitionType` 和 CSS 视图转换伪元素）实现流畅、原生感觉的动画的指南。每当用户想要添加页面转换、为路线更改设置动画、创建共享元素动画、为组件的进入\u002F退出设置动画、为列表重新排序设置动画、实现定向（向前\u002F向后）导航动画或在 Next.js 中集成视图转换时，请使用此技能。当用户提及视图转换、startViewTransition、ViewTransition、转换类型或询问有关在 React 中的 UI 状态之间设置动画而无需第三方动画库时也可使用。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fvercel-labs\u002Freact-view-transitions\u002FSKILL.md",[],[],{"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":20},"01M79SG04BFAVYZ2C3RQ7YX9C6","vercel-react-native-skills","React Native和Expo构建高性能移动应用程序的最佳实践。在构建React Native组件、优化列表性能、实现动画或使用本机模块时使用。涉及React Native、Expo、移动性能或本机平台API的任务的触发器。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fvercel-labs\u002Freact-native-skills\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":20},"01M79SFVFWYQKG0V95RXM3MEAW","vercel-react-best-practices","Vercel Engineering的React和Next.js性能优化指南。在编写、审查或重构React\u002FNext.js代码时，应使用此技能，以确保最佳性能模式。涉及React组件、Next.js页面、数据获取、捆绑优化或性能改进的任务的触发器。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fvercel-labs\u002Freact-best-practices\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":20},"01M79SFJXD83X39ZFV0SR8Z6TY","vercel-composition-patterns","可扩展的React组合模式。在重构具有布尔属性增殖的组件、构建灵活的组件库或设计可重用的API时使用。涉及复合组件、渲染道具、上下文提供者或组件架构的任务的触发器。包括React 19 API变更。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fvercel-labs\u002Fcomposition-patterns\u002FSKILL.md",[],[],{"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":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M79SEC8F4BW45HKSK7VSYQ1Y","ui-styling","使用 shadcn\u002Fui 组件（基于 Radix UI + Tailwind 构建）、Tailwind CSS 实用优先样式和基于画布的视觉设计创建美观、可访问的用户界面。在构建用户界面、实现设计系统、创建响应式布局、添加可访问组件（对话框、下拉菜单、表单、表格）、自定义主题和颜色、实现深色模式、生成视觉设计和海报或跨应用程序建立一致的样式模式时使用。","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fui-ux-pro-max\u002Fui-styling\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fui-ux-pro-max\u002Fui-styling\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M79SE0JWV6111HE4M0A5K6XW","design","“综合设计技能：品牌标识、设计标记、UI 样式、徽标生成（55 种样式、Gemini 或 Atlas Cloud AI）、企业形象程序（50 个可交付成果、CIP 模型）、HTML 演示文稿（Chart.js）、横幅设计（22 种样式、社交\u002F广告\u002F网页\u002F打印）、图标设计（15 种样式、SVG、Gemini 3.1 Pro）、社交照片（HTML→屏幕截图、多平台）。操作：设计徽标、创建 CIP、生成模型、构建幻灯片、设计横幅、生成图标、创建社交照片、社交媒体图像、品牌标识、设计系统：Facebook、Twitter、LinkedIn、YouTube、Instagram、Pinterest、TikTok、Threads、Google Ads。”","https:\u002F\u002Fgithub.com\u002Fzzz2929\u002Fskills-zh-CN\u002Fblob\u002Fmain\u002Fui-ux-pro-max\u002Fdesign\u002FSKILL.md",[],[]]