Brother 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 the printer ready and supplied with the requested media, my authorization for the requested document, and the printer's configured authentication and TLS trust where required. Installing the file configures none of that. Install "Brother Printers" for me. It prints documents and inspects print jobs on a Brother printer that fresh discovery identifies as offering IPP — manufacturer/model matched with an advertised _ipp._tcp or _ipps._tcp service, never from a vendor prefix alone — using the discovered IPv4 address, port and resource path. It first queries Get-Printer-Attributes and reads printer-state, printer-state-reasons, printer-is-accepting-jobs, document-format-supported, media-supported, resolution and duplex capabilities, using an IPP client such as CUPS/ipptool. It prefers image/pwg-raster when advertised, generating PWG Raster with standard CUPS filters such as imagetoraster and rastertopwg. Media, printable area, resolution, colour and sides are matched to the advertised capabilities and the layout scaled for that resolution; a PDF or JPEG is not sent merely because another printer supports it. It then sends IPP Print-Job with the selected document-format and the document bytes through the authorized printer endpoint — the document goes to my own local printer only — preserves the returned job ID/URI and monitors the job with Get-Job-Attributes, resolving paper, media or authentication errors before considering another submission. A queued or processing job is not yet a printed page; if a submission times out, existing jobs are inspected before resending, to avoid duplicate prints. Limits: the PWG Raster path is documented for the MFC-J880DW, other models are checked individually; no printer configuration changes, no unsolicited pages, no cancelling unrelated jobs. Documents are prepared in the agent environment, not on Home Link. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-brother-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-brother-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 045bf00c385b447c2a6b4b3776a9efb501098bd6e0bc13ae32f390c2642f48a0 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,854 bytes). There is no script, no code and no configuration in it; at use time it works through an IPP client such as CUPS/ipptool via Muse Home Link against my own Brother printer at its discovered endpoint. 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, the only destination is my local printer: Get-Printer-Attributes reads come first, then one authorized Print-Job with the document bytes in an advertised format. The printer's configured authentication and TLS trust are used where required; the document is never sent to any cloud print service or third party. - The skill does not change printer configuration, does not print unsolicited pages and does not cancel unrelated jobs. The PWG Raster path is documented for the MFC-J880DW only; on other models the advertised formats and capabilities are checked individually, and a format is never sent merely because another printer supports it. - 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-brother-printers folder into the agent's skills directory, in a folder named exactly "gadget-brother-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-brother-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 Brother IPP/IPPS printer ready on my local network, supplied with the requested media; and authorize each document I want printed, with the printer's configured authentication/TLS in place where required; 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.