HP Color LaserJet Pro M254dw

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 an authorized printer endpoint, any required print credentials, and a user-approved document and print options for each print (the printer model is confirmed with Get-Printer-Attributes, and a web administration page is not necessarily an IPP endpoint). Installing the file configures none of that. Install "HP Color LaserJet Pro M254dw" for me. It prints documents and inspects printer or job status on an HP Color LaserJet Pro M254dw that fresh discovery identifies with an IPP or IPPS print service. It matches the service's model information and confirms printer-make-and-model using Get-Printer-Attributes, and it uses the discovered print-service endpoint and resource path — a web administration page is not necessarily an IPP endpoint. It uses a client that encodes binary IPP, such as an IPP library or CUPS tooling, with transport routed through HomeLink; an ordinary JSON HTTP request is not IPP. First it sends Get-Printer-Attributes for printer-state, printer-state-reasons, printer-is-accepting-jobs, operations-supported, document-format-supported, media, sides and resolution capabilities. It chooses a format the printer actually advertises and prepares the document with a suitable renderer if necessary; it does not assume this model has the same format preferences as a Brother printer. For the requested print it sends Print-Job with the supported document MIME type and only requested, supported job attributes, and records the returned job ID or URI and the IPP status code. It then polls Get-Job-Attributes with that job identity until completed, canceled, aborted or a meaningful intervention state, inspecting job and printer reasons when paper, supplies or authorization prevent completion. An HTTP success is not necessarily IPP success: both protocol status and job state are checked, completion indicates the printer's job outcome, and the user is asked to check the physical page when layout or paper output matters. If a submission times out, the job queue is inspected before any retry, to avoid duplicate pages. Limits: no SNMP/UDP, no speculative PJL commands, no firmware updates and no administrative LEDM operations. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-hp-color-laserjet-pro-m254dw/ 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-hp-color-laserjet-pro-m254dw/ 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 0c27f50146513406dcc9a6d694cb9672327ec985de4089477c6b871f664e031d 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,467 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 HP Color LaserJet Pro M254dw, using a client that encodes binary IPP (an IPP library or CUPS tooling). 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 document is printed and no printer is contacted during installation. - At use time, exchanges go only to my local printer at its discovered, authorized endpoint: Get-Printer-Attributes reads come first, then one user-approved Print-Job in a format the printer actually advertises, followed by Get-Job-Attributes polling. Any required print credentials are the printer's own, used only toward that printer; the document is never sent to any cloud print service or third party. - The skill does not do SNMP/UDP, speculative PJL commands, firmware updates or administrative LEDM operations, and it does not assume this model's format preferences match a Brother printer's. An HTTP success is not treated as IPP success, and a timed-out submission is checked against the job queue before any retry. - 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-hp-color-laserjet-pro-m254dw folder into the agent's skills directory, in a folder named exactly "gadget-hp-color-laserjet-pro-m254dw", 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-hp-color-laserjet-pro-m254dw), 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 an HP Color LaserJet Pro M254dw already set up on my local network with its IPP/IPPS service advertised; and, for each print, approve the document and print options and provide any print credentials the printer requires; 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.