Moonraker 3D Printers

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — Muse Home Link and a compatible physical device are required to USE this skill, not to install it: installing the skill file itself needs no account, no key and no device, and this install does NOT set up Home Link, pair anything or ask for any credential. But the skill is instructions only. To use it I must read and follow ~/docs/devices/home_link.md in my Muse environment, have the compatible physical device named below already set up on my local network, and have a commissioned 3D printer with Moonraker already installed on my local network, identified by current discovery or an endpoint I confirm, any required Moonraker API key or access token stored securely, and, for print operations, an explicitly selected file already available to the printer plus my confirmation that the build area and printer are ready (an arbitrary local file is never substituted). Installing the file configures none of that. Install "Moonraker 3D Printers" for me. It reads 3D-printer status and manages requested print jobs through an existing Moonraker service using Muse Home Link, for a commissioned printer and existing print files; it is not arbitrary G-code, firmware setup or configuration changes. It is used when current discovery or an endpoint I confirm identifies an existing Moonraker service attached to the intended printer: it reads /server/info and /printer/info using the authorized endpoint and credentials and confirms Moonraker/Klipper versions, connection state and printer identity, and it uses /printer/objects/list and documented object queries to discover available state rather than assuming every printer has the same heaters, tools or sensors. The printer is commissioned with Moonraker already installed and any required API key or access token is stored securely; for print operations, an explicitly selected file already available to the printer is used, plus my confirmation that the build area and printer are ready — an arbitrary local file is never substituted. It reads server/printer readiness and queries relevant objects such as print_stats, virtual_sdcard, pause_resume and the actual heater/tool objects present; for status requests it reports current job, progress, temperatures and error state from those objects, handling disconnected or shutdown states as unavailable, not idle. For an authorized job it uses the documented HTTP request or equivalent JSON-RPC method for /printer/print/start, /printer/print/pause, /printer/print/resume or /printer/print/cancel, providing the exact existing filename for start and URL-encoding parameters correctly, then monitors job state and temperatures after the action, using an outbound WebSocket subscription if supported by the client, otherwise polling the documented object query endpoint. A successful API call is not proof that printing or pausing completed: print_stats, pause state and relevant errors are checked, and if a start request is uncertain the current job is inspected before resubmission — a running print is never restarted. Limits: no new server/firmware installation, arbitrary G-code, configuration changes or bypassing thermal/motion protections; canceling a job or moving hardware is a physical action and requires my request, and a generic API key is not treated as permission for all administrative endpoints. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-moonraker-3d-printers/ folder at the pinned commit: SKILL.md only, 1 file) Pinned version: install the code at commit e6fe5174092702ffddae6f90759a38d55a4ebae1 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/facebookincubator/muse-gadget-sdk into a temporary folder, check out commit e6fe5174092702ffddae6f90759a38d55a4ebae1, and copy the skills/gadget-moonraker-3d-printers/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 6bd0386e478ebc97ec72228f6a0e55bf828cbd4b1a93f6ff91c17670f13a207d If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (2 798 bytes). There is no script, no code and no configuration in it; the procedure runs at use time through Muse Home Link against my own local device. It has no dependency on any other gadget skill in this lot. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit. No device is contacted, no pairing is started and no key is asked for during installation. - At use time, exchanges go only to my existing local Moonraker service: authorized reads of /server/info, /printer/info and printer objects, and the documented print start/pause/resume/cancel methods for a job I authorized, using my securely stored API key or access token only where that service requires it. No arbitrary G-code or configuration change happens at use time. - The skill does not install a new server or firmware, send arbitrary G-code, change configuration or bypass thermal/motion protections, and canceling a job or moving hardware always requires my request. - Do not pair any device, do not ask for or set any credential, do not run any control, print, scan or playback action, and do not use the skill in any way during this install: Home Link setup, pairing and use are my decisions, later, when I actually ask for them. 3. When I say "yes, install", install it as a skill: copy the whole gadget-moonraker-3d-printers folder into the agent's skills directory, in a folder named exactly "gadget-moonraker-3d-printers", keeping its 1 file (SKILL.md at its root). The exact folder name matters: relative links between sibling gadget skills depend on these exact names. 4. Verify with no network calls: frontmatter valid (name: gadget-moonraker-3d-printers), the 1 file in place with matching fingerprint. Do not run anything and do not connect to any device to verify. 5. Report what was installed, where, and what I still need to do myself (for example: read ~/docs/devices/home_link.md in my Muse environment and follow its Home Link rules; have a commissioned printer with Moonraker already installed, keep any required API key or access token stored securely, and, for a print start, select a file already on the printer and confirm the build area and printer are ready; using the skill is a separate step that only starts when I ask for it, and the use-time exchanges disclosed above happen only then). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.