agentleFS
Sign inStart free
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-moonraker-3d-printers/SKILL.md

gadget-moonraker-3d-printers

Skill2.6k starsChanged 24 days agoApache-2.0View on GitHub

Read 3D-printer status and manage requested print jobs through an existing Moonraker service using Muse Home Link. Use for a commissioned printer and existing print files; not arbitrary G-code, firmware setup, or configuration changes.

1 other project uses a version of this, 1 of them edited.

Trending

More talk lately.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 13 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the facebookincubator/muse-gadget-sdk repository that our weekly crawl found: only 14 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about facebookincubator/muse-gadget-sdk

The biggest 5 of 14 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 14

Talked about on GitHub, Bluesky and Hacker News (14 times).

On GitHub · 11

6 more on GitHub

On Hacker News · 1

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when current discovery or a user-confirmed endpoint identifies an existing Moonraker service attached to the intended …

    line 11
  2. Very specific:

    Read /server/info and /printer/info using the authorized endpoint and credentials.

    line 15
  3. Very specific:

    Use /printer/objects/list and documented object queries to discover available state, rather than assuming every printer has the same …

    line 16
  4. Very specific:

    Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.

    line 20
  5. Very specific:

    Read server/printer readiness and query relevant objects such as print_stats, virtual_sdcard, pause_resume, and the actual heater/tool …

    line 27
  6. Distinctive:

    If a start request is uncertain, inspect the current job before resubmission.

    line 35
  7. Distinctive:

    No new server/firmware installation, arbitrary G-code, configuration changes or bypassing thermal/motion protections.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Moonraker 3D Printers

Use this skill when current discovery or a user-confirmed endpoint identifies an existing Moonraker service attached to the intended printer.

Identify the Device

  • Read /server/info and /printer/info using the authorized endpoint and credentials. Confirm Moonraker/Klipper versions, connection state and printer identity.
  • Use /printer/objects/list and documented object queries to discover available state, rather than assuming every printer has the same heaters, tools or sensors.

Prerequisites

Read and follow the Home Link networking and safety rules in ~/docs/devices/home_link.md.

  • A commissioned printer with Moonraker already installed and any required API key or access token stored securely.
  • For print operations, an explicitly selected file already available to the printer, plus confirmation that the build area and printer are ready. Do not substitute an arbitrary local file.

Workflow

  1. Read server/printer readiness and query relevant objects such as print_stats, virtual_sdcard, pause_resume, and the actual heater/tool objects present.
  2. For status requests, report current job, progress, temperatures and error state from those objects. Handle disconnected or shutdown states as unavailable, not idle.
  3. For an authorized job, use the documented HTTP request or equivalent JSON-RPC method for /printer/print/start, /printer/print/pause, /printer/print/resume or /printer/print/cancel. Provide the exact existing filename for start; URL-encode parameters correctly.
  4. Monitor job state and temperatures after the action. Use an outbound WebSocket subscription if supported by the client, otherwise poll the documented object query endpoint.

Verify the Result

  • A successful API call is not proof that printing or pausing completed. Check print_stats, pause state and relevant errors.
  • If a start request is uncertain, inspect the current job before resubmission; do not restart a running print.

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 the user's request. Do not treat a generic API key as permission for all administrative endpoints.

Sources

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free