find and control DLNA devices
v1.0.0Use when controlling DLNA/UPnP media renderers (smart TVs, speakers) on a local network - discovering devices, playing media URLs, controlling playback (play...
⭐ 0· 38·0 current·0 all-time
bydxs@dxsdyhm
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description align with the content: the SKILL.md describes SSDP discovery and AVTransport control using async_upnp_client and related libraries. Required capabilities (network access to LAN devices) are appropriate for DLNA control.
Instruction Scope
Runtime instructions focus on network discovery and SOAP control of MediaRenderer devices (discover, SetAVTransportURI, Play, Pause, etc.). They do not ask to read unrelated files, access unrelated environment variables, or contact third-party endpoints outside normal DLNA flows.
Install Mechanism
This is an instruction-only skill with no install spec or code files. The declared Python dependencies (async_upnp_client, httpx, click) are reasonable and proportional to the task; there is no arbitrary download or extract step.
Credentials
No environment variables, credentials, or config paths are requested. The skill's need for local network access (SSDP/UDP 1900 and HTTP to devices) is expected for DLNA control.
Persistence & Privilege
Skill does not request persistent/always-on privileges and is user-invocable only. It does not modify other skills or system-wide configs.
Assessment
This skill appears coherent and focused on DLNA/UPnP control, but consider the following before installing: (1) It requires local network access—SSDP discovery will probe the LAN (UDP 1900); run it only on trusted networks. (2) Playing arbitrary media URLs causes your devices to fetch external content; avoid untrusted URLs to prevent exposing device/network metadata or serving malicious content. (3) The SKILL.md lists Python dependencies but includes no install automation—verify and pin dependency versions before installing. (4) If you need stronger isolation, run the code in a restricted environment or network segment that limits access to sensitive devices. If you want extra assurance, request the actual implementation code (not just instructions) and review it for unexpected network calls or file access.Like a lobster shell, security has layers — review code before you run it.
latestvk975twfpaajtvk2c6vary69zsx84vhme
License
MIT-0
Free to use, modify, and redistribute. No attribution required.