Sendcutsend
Check DXF or STEP exports against live SendCutSend fabrication rules before you pay for a rejected laser or CNC order.
Overview
sendcutsend is an agent skill for the Validate phase that reviews DXF and STEP files against SendCutSend specifications for upload readiness.
Install
npx skills add https://github.com/earthtojake/text-to-cad --skill sendcutsendWhat is this skill?
- Reviews DXF and STEP for SendCutSend upload readiness
- Uses official SendCutSend source map as live evidence—not a stable API
- Requires citing exact source URLs before pass/fail claims
- Default prompt: review file for SendCutSend upload readiness
- MIT-licensed checker skill in the text-to-cad repo
Adoption & trust: 1.6k installs on skills.sh; 5.8k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You exported a part file but do not know if SendCutSend will accept it, and vendor spec pages are easy to misread without traceable citations.
Who is it for?
Solo builders fabricating physical enclosures, brackets, or plates who use SendCutSend and agent-assisted CAD export.
Skip if: Pure software products with no DXF/STEP fabrication step, or builders who need full CAM toolpath generation inside the agent.
When should I use this skill?
Use $sendcutsend to review this DXF or STEP file for SendCutSend upload readiness.
What do I get? / Deliverables
You get a source-cited readiness review of your DXF or STEP against SendCutSend rules so you can fix issues before upload and ordering.
- Source-cited SendCutSend readiness assessment for the supplied file
- Actionable fixes for spec mismatches before vendor upload
Recommended Skills
Journey fit
Upload-readiness review happens after you have a part design and before you commit money and lead time to a vendor cut. Prototype validation covers mechanical file sanity against a real fab house spec map, not app code integration.
How it compares
Vendor spec checker with cited live sources—not a CAD authoring or nesting optimizer.
Common Questions / FAQ
Who is sendcutsend for?
Indie makers and builder-founders shipping physical prototypes who order cuts through SendCutSend and want agent help validating exports.
When should I use sendcutsend?
Use it in Validate during prototype, immediately after you have a DXF or STEP export and before you upload or pay on SendCutSend.
Is sendcutsend safe to install?
It primarily reads your part files and references public vendor docs—review the Security Audits panel on this Prism page and avoid sending proprietary geometry to untrusted environments.
SKILL.md
READMESKILL.md - Sendcutsend
interface: display_name: "SendCutSend" short_description: "Review DXF/STEP against SendCutSend specs." default_prompt: "Use $sendcutsend to review this DXF or STEP file for SendCutSend upload readiness." MIT License Copyright (c) 2026 earthtojake Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Official SendCutSend Source Map Use these sources as live evidence, not as a stable API. Field coverage, value types, and `N/A` usage can vary. Before making pass/fail claims, cite the exact source URL and, for JSON facts, the field path used. ## Core Entry Points - Ordering guide: https://cdn.sendcutsend.com/specs/sendcutsend-ordering-guide.md - Catalog JSON: https://cdn.sendcutsend.com/specs/sendcutsend-catalog.json - Engineering specs JSON: https://cdn.sendcutsend.com/specs/sendcutsend-specs.json Fetch these URLs directly before each review. Use the current response bodies as the evidence for material/service checks, and cite the URL plus the access date in the report. ## Source Roles - Ordering guide: use for ordering flow, accepted file formats, plain-language design rules, and general service explanations. - Catalog JSON: use for orderability facts such as material SKUs, material names, thicknesses, stock status, cutting process, min/max part size, available services, hardware items, and finish options. - Engineering specs JSON: use for SKU-keyed design validation facts such as tolerances, minimum hole/bridge/edge values, bending parameters, tapping, countersinking, hardware insertion, dimple forming, finishing constraints, and material properties. ## Provenance To Capture - Source URL - Access date - JSON `_meta.schema_version` - JSON `_meta.generated_at` - JSON `_meta.source_data_generated_at` when present - Field path for row-level citations, such as `sendcutsend-specs.json materials[sku=ALU-063].cutting_specs.min_hole_size` ## Conflict Handling Prefer exact SKU joins across catalog and specs. If source facts conflict or a field is missing, unparsable, or `N/A`, report the uncertainty and mark the dependent row `❓ need more info` unless another more specific, cited source resolves it. Use this precedence for source facts: 1. material/thickness/service-specific configurator or current quote/upload result 2. exact SKU entry in engineering specs JSON 3. exact SKU entry in catalog JSON 4. ordering guide 5. broader official SendCutSend human-readable page, only when the three source files are insufficient Record the conflict and the page you relied on. # SendCutSend Validation Report Template Use this structure when the user asks for a review, validation, preflight, or manufacturing readiness report. ## Context - File: `<path>` - Assumed service: `DXF laser sheet cutting` or `STEP CNC routing` - Order context: material, thickness, primary process, finish, quantity, secondary operations - Date checked: `<YYYY-MM-DD>` ## Sources Checked List official SendCutSend URLs used for the checks as Markdown links. Include only sources actually consulted.