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

92%

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-structured, executable skill body with a sequenced workflow, explicit validation/dry-run checkpoints, and clean one-level-deep references to real bundle files. Only minor conciseness gains remain in the handoff and backend sections.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes Claude's competence (no explanation of what G-code or slicing is), with executable commands and tight examples; minor padding in the review-pane handoff section and light redundancy in backend guidance keep it just below fully lean.	4 / 5
Actionability	Provides copy-paste-ready bash commands for all seven workflow steps plus two complete JSON profile examples, covering the common cases with no missing execution details.	5 / 5
Workflow Clarity	A clearly numbered seven-step sequence with an explicit dry-run checkpoint before execution and a dedicated validation step with --json output, satisfying the feedback-loop requirement for a slicing operation.	5 / 5
Progressive Disclosure	The body is a concise overview that defers detail to one-level-deep, clearly-signaled references ('Read references/slicer-backends.md when...', 'Read references/gcode-validation.md when...'), and both referenced files exist and hold the expected detail.	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, specific description with concrete actions, an explicit use-when trigger clause, and clear niche boundaries. Its only weakness is mild technical lean in trigger phrasing that could include a few more lay synonyms.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'generating, inspecting, dry-running, and validating' plain FDM .gcode 'with real slicer CLIs' — giving comprehensive coverage of the skill's capabilities rather than vague abstractions.	5 / 5
Completeness	Explicitly answers both 'what' (generate/inspect/dry-run/validate plain FDM .gcode with real slicer CLIs) and 'when' via a clear 'Use only when...' clause with concrete trigger conditions.	5 / 5
Trigger Term Quality	Includes natural trigger phrases ('asks Replicator to generate G-code', 'needs headless/reproducible slicing', 'cannot use a slicer UI') but leans technical and omits some common lay synonyms a user might say.	4 / 5
Distinctiveness Conflict Risk	Highly specific niche (plain FDM .gcode via real slicer CLIs, Replicator context) with explicit boundary against ordinary print-plate workflows, yielding minimal conflict with other 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: 1 day 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.