gcode
Transform 3D mesh geometry into production-ready G-code by leveraging local slicer engines. This skill bridges CAD design and machine execution, handling the critical conversion step that prepares models for CNC machining and additive manufacturing. Ideal for workflows requiring direct control over slicing parameters and output formats.
gcode transforms STL files into production-ready G-code by leveraging local slicer backends. The skill orchestrates available slicer CLI tools to process your 3D mesh geometry, applying printer profiles and slicing parameters to generate plain G-code output suitable for CNC machining and additive manufacturing workflows.
AI-generated summary based on this skill's SKILL.md
Install
earthtojake/text-to-cad/gcode · repository language: JavaScript
git clone https://github.com/earthtojake/text-to-cad
cp -r text-to-cad/skills/gcode ~/.claude/skills/gcodeFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does gcode convert STL to gcode?
gcode transforms STL files into production-ready G-code by leveraging local slicer backends. The skill orchestrates available slicer CLI tools to process your 3D mesh geometry, applying printer profiles and slicing parameters to generate plain G-code output suitable for CNC machining and additive manufacturing workflows.
Can gcode validate gcode before printing?
Yes. gcode includes validation and inspection capabilities to examine G-code output before handoff to your printer. This dry-run functionality lets you verify slicing operations against your printer profile, catching issues early and ensuring your mesh geometry is properly prepared for machine execution.
What mesh formats does gcode support?
gcode handles multiple mesh formats including STL, OBJ, GLB, GLTF, and PLY. The skill converts these formats to printer-ready G-code, giving you flexibility in your CAD design pipeline while maintaining direct control over slicing parameters and output formats.
How does gcode discover local slicer backends?
gcode automatically discovers and orchestrates available slicer CLI tools on your system. This backend discovery mechanism lets you leverage installed slicers like OrcaSlicer without manual configuration, streamlining the conversion from 3D model geometry to executable machine instructions.
Can I generate gcode with a custom printer profile?
Yes. gcode supports dry-run slicing operations using custom printer profiles. You can generate G-code tailored to your specific printer's capabilities and constraints, ensuring the output matches your machine's requirements before actual production execution.
What license does gcode use?
gcode is released under the MIT license, making it freely available for both commercial and personal use with minimal restrictions. This permissive licensing supports integration into diverse manufacturing workflows and development environments.
SKILL.md
rendered from the published skill — quoted content, verbatim
G-code
Provenance: maintained in earthtojake/text-to-cad. Use the installed local skill files as the runtime source of truth; the repository link is only for provenance and release review.
Use this skill for plain .gcode generation from mesh files. It is printer-agnostic and never uploads, starts, or packages print jobs.
Workflow
- Confirm the input is a supported mesh:
.stl,.obj, unsliced.3mf,.ply,.glb, or.gltf. - Require an explicit printer/profile wrapper JSON. Do not invent real-printer profiles.
- Discover slicer backends when the backend is unknown:
python scripts/gcode_tool.py discover
- Inspect the input:
```bash python scripts/gcode_tool.py inspect --input
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 6 files
skills/gcode/LICENSE
skills/gcode/SKILL.md
skills/gcode/agents/openai.yaml
skills/gcode/references/gcode-validation.md
skills/gcode/references/slicer-backends.md
skills/gcode/scripts/gcode_tool.py