orcaslicer

Slice STL meshes with OrcaSlicer profiles and inspect G-code layers, travel, and speeds.

465|41|Updated Aug 4, 2026
One-click install
npx skills add https://github.com/autonomous-ai/openharness --skill orcaslicer-autonomous-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orcaslicer
Source: https://github.com/autonomous-ai/openharness/tree/main/store/agents/orca-slicer/skills/orcaslicer
Command: npx skills add https://github.com/autonomous-ai/openharness --skill orcaslicer-autonomous-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Slicing a 3D model produces G-code that is hard to verify before printing, and blindly trusting slicer output risks failed prints or unsafe machine behavior. This Skill runs a real OrcaSlicer build with explicit JSON profiles and renders the actual toolpaths so you can inspect exactly what the printer would do. ## Core Features & Use Cases - Deterministic slicing: Runs OrcaSlicer 2.4.2 from the CLI with explicit printer, process, and filament JSON profiles, resolving profile inheritance chains and failing closed on errors. - Interactive G-code inspection: Generates a local preview.html toolpath viewer with layer scrubbing, feature and speed coloring, travel move toggles, and isometric or top projections. - Honest verification reporting: Writes verdict.json, slice.json, resolved profiles, and slice.log to .harness/, clearly labeling slicer estimates as estimates rather than print-safety certificates. - Use Case: You have an STL of a fluted vessel and want to check first-layer travel, per-layer extrusion, and feature breakdown before committing to a print. Configure slice-config.json, run the slice script, and scrub through the parsed layers in the preview. ## Quick Start Ask the agent to slice the STL model in this workspace using the OrcaSlicer skill and open the generated preview to inspect the layers.

Frequently Asked Questions about orcaslicer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I slice an STL file with OrcaSlicer from the command line?

Set slice-config.json with mode, model, printer, process, and filament profile keys, then run scripts/slice-part.sh. The build invokes OrcaSlicer with --slice, flattened profiles, and arc fitting disabled, producing part.gcode and preview.html.

How do I inspect G-code layers and toolpaths before 3D printing?

Open the generated preview.html in a browser to scrub through extrusion layers, isolate a single layer, toggle travel and custom moves, and color segments by feature or speed. The viewer parses actual G0/G1 moves from the sliced G-code.

Can I use PrusaSlicer instead of OrcaSlicer for CLI slicing?

No, PrusaSlicer is not a compatible fallback for this workflow. The build requires OrcaSlicer 2.4.2, located via the ORCA_BIN environment variable or a standard install path, and fails if it is not found.

What G-code features are not supported by the toolpath preview?

The parser handles only linear G0/G1 moves with G20/G21, G90/G91, M82/M83, and G92. Arc moves (G2/G3/G5), multiple tools, firmware retraction, bed leveling, and collisions are rejected or not simulated, with a 250,000-move and 32 MiB limit.

Does a successful slice mean the G-code is safe to print?

No. A ready verdict means the file was sliced and parsed, not that it is print-safe. The workflow does not establish watertightness, support adequacy, or printer compatibility, and requires reviewing the G-code in OrcaSlicer before any print.