Epson 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 actual service endpoints and any device authentication, and my permission for the document or the physical scan (with the document placed in the selected feeder or on the platen for a scan). Installing the file configures none of that. Install "Epson Printers" for me. It prints on a confirmed Epson printer that advertises IPP/IPPS, and scans only from an exact Epson multifunction model that exposes a documented eSCL scan service; printing and scanning are distinct advertised services — IPP does not imply a scanner, and sane-airscan compatibility does not mean every Epson device uses eSCL. For printing, with a binary IPP client it uses Get-Printer-Attributes to read supported formats, media, sides, resolution, operations and current state, submits a requested document with Print-Job in an advertised format, retains its job ID and monitors Get-Job-Attributes and printer reasons, resolving an uncertain submission before resending. For an advertised eSCL service, it reads ScannerCapabilities and ScannerStatus beneath the advertised base path and selects only a supported input source, size, resolution, colour mode and output format. With the document placed in the selected feeder or on the platen, it creates the requested ScanJobs job using eSCL XML, follows the returned job Location and retrieves NextDocument as the protocol requires — authorizing any changed network destination first — retrieves all requested pages, handles feeder-empty and job-complete responses, and closes or cancels that specific scan job if necessary, keeping scanned material in my approved storage. Verification: terminal print-job state, not only HTTP status; for scans, the retrieved media type, readability, page count and settings — an accepted scan job is not a retrieved scan. Limits: eSCL, duplex scanning and unauthenticated access are never promised for the whole family; WSD-only scanning, SNMP/UDP discovery or control, browser automation and firmware changes are outside this skill. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-epson-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-epson-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 8bf042c004074b801f903fcfc7b53b22567879742fe6be0986db1bf3aba1a889 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,773 bytes). There is no script, no code and no configuration in it; at use time printing works through a binary IPP client and scanning through an eSCL-capable client via Muse Home Link against my own Epson 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 document is printed and no scan is started during installation. - At use time, exchanges go only to my local Epson device: print documents are submitted by Print-Job in an advertised format to my own printer, and scan jobs are created on the device's advertised eSCL base path, with any device authentication the device is configured with. Scanned pages are retrieved from the device and kept in my approved storage; nothing is sent to any cloud or third party. - IPP alone does not establish scanning support: eSCL scanning happens only when the exact model advertises that service, and any changed network destination returned by the device is authorized before it is followed. The skill does no WSD-only scanning, no SNMP/UDP discovery or control, no browser automation and no firmware changes. - 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-epson-printers folder into the agent's skills directory, in a folder named exactly "gadget-epson-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-epson-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 an Epson printer advertising IPP/IPPS — or, for scanning, an exact model advertising eSCL — on my local network; and authorize each document or physical scan, keeping scanned material in my approved storage; 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.