Yi Cameras with Existing yi-hack Firmware

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 Yi camera already running a confirmed compatible yi-hack fork — modified community firmware that is already installed as a use prerequisite and is never flashed by this skill — with its local snapshot or RTSP service enabled, its existing HTTP/RTSP credentials, a credential-aware client using HomeLink, and my permission for the particular camera and requested image, view or recording. Access is read-only: snapshots or bounded streams only, kept in approved private storage. Installing the file configures none of that. Install "Yi Cameras with Existing yi-hack Firmware" for me. It retrieves snapshots or bounded streams from cameras already running compatible yi-hack firmware through Muse Home Link, using the installed fork's enabled HTTP or TCP-interleaved RTSP service; it is not stock-camera access, flashing or camera control. It is used when the camera already runs a confirmed compatible yi-hack fork with its local snapshot or RTSP service enabled: exact camera hardware, installed yi-hack fork/version and enabled interfaces are confirmed from existing configuration, and that fork's documented endpoint/path is used — not all Yi cameras or yi-hack forks share a snapshot URL or stream name. The firmware is already installed, with its existing HTTP/RTSP credentials, a credential-aware HTTP or RTSP client using HomeLink (RTSP media must support interleaved TCP), and my permission for the particular camera and requested image, view or recording. It selects the installed fork's documented HTTP snapshot endpoint or enabled RTSP stream, using only the current authorized host and service: for a still snapshot it makes the documented authenticated read and verifies the returned image type/content rather than saving an HTML error page; for RTSP it explicitly uses interleaved TCP for control and media, with no fallback to UDP, and decodes only the requested frame or bounded stream. It stores the result in my approved private location and closes the session after completing the request, and it checks that the image is fresh, decodable and from the requested camera, not cached content or a login response — an available web UI or open RTSP port is not proof of successful image capture. Limits: read-only snapshot/view/capture scope — no camera settings, firmware changes or arbitrary CGI operations; no stock-camera support, no automatic flashing and no claim that firmware changes are harmless or reversible; and no UDP streams, unsupported hardware/fork combinations, implicit recording or media sharing. Repository: https://github.com/facebookincubator/muse-gadget-sdk (the skill is the whole skills/gadget-yi-hack-cameras/ 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-yi-hack-cameras/ 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 8f88defc060df0b8ea60c60492135fe5f4812655adc799ba2f1f98a95ff73573 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 337 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 between my local Yi camera and my local client through HomeLink: the installed fork's documented authenticated HTTP snapshot read, or its RTSP stream over interleaved TCP, decoding only the frame or bounded stream I requested, with existing HTTP/RTSP credentials through a credential-aware client. Results are stored in my approved private location and the session is closed after the request. No settings change and no arbitrary CGI operation happens at use time. - The skill is read-only: it does no camera settings, firmware changes or arbitrary CGI operations, does not support stock cameras, never flashes firmware automatically and claims no firmware change is harmless or reversible, and it does no UDP streams, implicit recording or media sharing. - 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-yi-hack-cameras folder into the agent's skills directory, in a folder named exactly "gadget-yi-hack-cameras", 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-yi-hack-cameras), 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 Yi camera already running a confirmed compatible yi-hack fork (modified community firmware already installed — the skill never flashes it) with its snapshot or RTSP service enabled, keep its existing HTTP/RTSP credentials available, and give my permission for each camera and requested image or view; access is read-only and results stay in my approved private 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.