gcode

Explicit advanced workflow for generating, inspecting, dry-running, and validating plain FDM `.gcode` with real slicer CLIs. Use only when the user asks Replicator to generate G-code, needs headless/reproducible slicing, or cannot use a slicer UI.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered skill body: fully executable commands, a dry-run/validate-gated workflow, and exemplary progressive disclosure via conditionally-triggered references. The sole weakness is moderate redundancy in the profile examples and a wordy handoff paragraph.

Dimension	Reasoning	Score
Conciseness	The body is command- and contract-dominated with no explanations of concepts Claude already knows, but the second OrcaSlicer JSON example repeats the machine/filament blocks of the first (~15 duplicated lines) and the review-pane handoff paragraph is wordy, giving more than minor trimming opportunities.	4 / 5
Actionability	Every workflow step has a copy-paste-ready command with concrete flags (discover, inspect --json, slice --dry-run/--execute, validate), the wrapper profile is given as complete executable JSON, and edge cases are handled concretely (brew install --cask orcaslicer, trimesh fallback, explicit accepted/rejected extensions).	5 / 5
Workflow Clarity	The numbered 1-7 sequence has explicit checkpoints: dry-run before execution (step 5), an explicit execution gate ('Execute only after the dry-run command and profile are appropriate'), and post-slice validation (step 7), with failure interpretation delegated to a clearly signaled reference.	5 / 5
Progressive Disclosure	SKILL.md is a clean overview; both referenced files (references/slicer-backends.md, references/gcode-validation.md) exist, are one level deep, and are signaled with conditional read triggers tied to concrete needs, and the helper script (scripts/gcode_tool.py) is present.	5 / 5
	Total	19 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete multi-action capability statement paired with an explicit, well-scoped trigger clause. The only weakness is trigger coverage that leans on environment-specific terminology ('Replicator') and omits a couple of natural user phrasings like 'slice this STL'.

Dimension	Reasoning	Score
Specificity	The description lists four concrete actions ('generating, inspecting, dry-running, and validating plain FDM .gcode with real slicer CLIs') covering the full workflow scope, with the tooling constraint ('real slicer CLIs') making the capability set comprehensive rather than gapped.	5 / 5
Completeness	It explicitly answers both what ('Explicit advanced workflow for generating, inspecting, dry-running, and validating plain FDM .gcode with real slicer CLIs') and when ('Use only when the user asks Replicator to generate G-code, needs headless/reproducible slicing, or cannot use a slicer UI') with three concrete trigger conditions.	5 / 5
Trigger Term Quality	Natural trigger phrases and the file extension are present ('generate G-code', '.gcode', 'FDM', 'headless/reproducible slicing', 'cannot use a slicer UI'), but a few common user phrasings (e.g., 'slice this model/STL') are missing and 'Replicator' is environment-specific jargon rather than a term a generic user would say.	4 / 5
Distinctiveness Conflict Risk	The 'Use only when' clause carves out a clear niche (headless, reproducible plain-G-code generation) and explicitly excludes ordinary slicer-UI printing, minimizing overlap with generic printing or CAD-export skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: JimmyPang02/open-replicator
Path: skills/gcode/SKILL.md
Commit: 18436cc

Reviewed: 18 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.