bambu-labs

Explicit advanced workflow to inspect status, upload, or cautiously start/control local Bambu Lab printers through LAN FTPS/MQTT after validated G-code exists. Use only when the user asks for printer communication or physical print control.

Quality

89%

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

85%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: executable commands with safety gating flags, a clearly sequenced workflow with explicit validation checkpoints and stop conditions, and clean one-level-deep progressive disclosure into real reference files. Remaining polish is minor: deduplicate the live-start rules and show the dry-run/upload-only command lines.

Dimension	Reasoning	Score
Conciseness	Mostly lean: terse safety bullets, concrete commands, and details pushed to reference files. Minor trimmable redundancy remains — the live-start authorization bullet in Safety Rules substantially restates workflow step 4, and the Replicator handoff paragraph repeats the skill name three times awkwardly. Not 5 for these minor over-explanations; well above the verbose midpoints.	4 / 5
Actionability	Gives copy-paste-ready commands with exact flags ('config set --printer a1-mini --host ... --access-code ...', 'status --push-all --wait-seconds 10', 'upload-start --execute --confirm-start-print') plus a JSON shape and an install fallback. Not 5 because the dry-run and upload-only invocations are named in prose without their full command lines. Not 3 — nothing is pseudocode and the common path is executable.	4 / 5
Workflow Clarity	Numbered 1-4 sequence with hard validation gates for a physically risky operation: validate G-code first, read status before live work, dry-run and inspect the JSON payload, upload-only, and 'Only after upload succeeds should you run upload-start', with explicit stop conditions per user intent. Includes an error-recovery loop (install OrcaSlicer and retry if no slicer). This matches the destructive-operation-with-explicit-checkpoints anchor despite the general cap concern — validation is thoroughly present.	5 / 5
Progressive Disclosure	The body is a genuine overview; four real reference files are clearly signaled with per-topic purposes ('Read references/handoff-and-debugging.md when choosing a handoff mode, debugging LAN/FTPS/MQTT behavior...'), one level deep, and all referenced paths exist in the bundle. Navigation is easy and content is appropriately split.	5 / 5
	Total	18 / 20 Passed

Description

87%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, an explicit scoped 'Use only when' trigger clause, and a distinct niche with a stated precondition (validated G-code). The only gaps are unmentioned pause/cancel controls and a few missing natural trigger synonyms (model names, file extensions).

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('inspect status, upload, or cautiously start/control local Bambu Lab printers through LAN FTPS/MQTT after validated G-code exists') with protocol and precondition detail. Not 5 because pause/cancel controls — a real capability of the skill — are omitted from the action list.	4 / 5
Completeness	Explicitly answers both what ('inspect status, upload, or cautiously start/control local Bambu Lab printers through LAN FTPS/MQTT') and when ('Use only when the user asks for printer communication or physical print control') with a concrete trigger clause plus a precondition. Fits the anchor-5 example pattern exactly; 4 would require the when-clause to be weaker or merely implied.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('printer communication', 'physical print control', status/upload/start), which a user asking about their Bambu printer would plausibly say. A few natural terms are missing, such as printer model names (A1, P1, X1C) and file extensions (.gcode, .3mf).	4 / 5
Distinctiveness Conflict Risk	'local Bambu Lab printers through LAN FTPS/MQTT' carves out a clear niche with distinct triggers, and the 'Use only when' clause scopes activation away from generic slicing/CAD skills. Minimal conflict risk.	5 / 5
	Total	18 / 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/bambu-labs/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.