agentleFS
facebookincubatorfacebookincubator/muse-gadget-sdk/skills/gadget-wyze-rtsp-cameras/SKILL.md

gadget-wyze-rtsp-cameras

Skill2.8k starsChanged 26 days agoApache-2.0View on GitHub

View or capture frames and bounded recordings from compatible Wyze Cam v2, Cam v3, or Pan v1 through Muse Home Link. Use only when legacy RTSP firmware is already installed and enabled with TCP media transport; not firmware installation or stock-camera access.

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

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when an exact compatible Wyze Cam v2, Cam v3 or Cam Pan v1 already runs an enabled RTSP build.

    line 11
  2. Distinctive:

    Use the existing configured RTSP endpoint/path and its current address.

    line 16
  3. Very specific:

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

    line 20
  4. Distinctive:

    Check timestamps, codec errors and requested duration.

    line 36
  5. Distinctive:

    If the stream requires UDP or authentication cannot be satisfied securely, stop and report the limitation.

    line 37
  6. Distinctive:

    Read-only camera access: no PTZ, siren, settings or firmware changes.

    line 41
  7. Distinctive:

    No stock-camera support, firmware sourcing/flashing, cloud bridge deployment or universal Wyze coverage.

    line 42
  8. Distinctive:

    Treat every frame and audio track as sensitive.

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Wyze Cameras with Existing RTSP Firmware

Use this skill when an exact compatible Wyze Cam v2, Cam v3 or Cam Pan v1 already runs an enabled RTSP build.

Identify the Device

  • Confirm the camera model and installed firmware with the user or existing device configuration. A vendor prefix or open port alone cannot establish the firmware.
  • Use the existing configured RTSP endpoint/path and its current address. Do not infer support for stock cameras or other generations.

Prerequisites

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

  • An already-installed, enabled and working RTSP build with supplied stream credentials.
  • An RTSP/media client configured for interleaved TCP for both control and media, with all sockets routed through HomeLink.
  • Explicit permission for the requested view, frame or bounded recording, and approved private storage.

Workflow

  1. Tell the user that these legacy RTSP builds are discontinued and may lack later security patches or app features. This skill does not recommend installing them.
  2. Connect to the configured stream with credentials supplied through a credential-aware client, not a command-line URL or logged argument.
  3. Explicitly request RTP/RTCP interleaved over the RTSP TCP connection. For an FFmpeg-based client the relevant transport option is rtsp_transport=tcp; do not allow fallback to UDP.
  4. Inspect the media description, authenticate and decode the requested live view, single frame or bounded recording. Stop the session once the request is satisfied.

Verify the Result

  • Confirm a fresh decodable frame from the intended camera; an RTSP login or stream description is not image delivery.
  • Check timestamps, codec errors and requested duration. Do not present a cached frame as current.
  • If the stream requires UDP or authentication cannot be satisfied securely, stop and report the limitation.

Limits

  • Read-only camera access: no PTZ, siren, settings or firmware changes.
  • No stock-camera support, firmware sourcing/flashing, cloud bridge deployment or universal Wyze coverage.
  • Treat every frame and audio track as sensitive; no background recording, third-party upload or broader sharing.

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.