sendcutsend

SendCutSend Use this skill to produce conservative, evidence-backed SendCutSend preflight reports for DXF and STEP/STP files. Treat 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/A , or conflicting source data into a pass or fail. Use scripts only to fetch source files or measure specific file facts; write the final report from explicit comparisons. Geometry Inspection Use the active project Python environment for local inspection scripts. If the $cad skill is available, use it first for STEP/STP/DXF geometry inspection, measurement, and validation workflows, then add any SendCutSend-specific targeted measurements that are still missing. Use build123d.import_step for STEP/STP 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. Source Refresh Before each review, download or refresh the three SendCutSend source files: python scripts/download_sources.py The downloader writes references/generated/sendcutsend-ordering-guide.md , references/generated/sendcutsend-catalog.json , references/generated/sendcutsend-specs.json , and references/generated/sources-manifest.json . The cache is fresh for 24 hours. If the user explicitly asks to skip cache, force a fresh fetch: Show more