HomePod
PassAudited by ClawScan on May 1, 2026.
Overview
This is a coherent HomePod troubleshooting skill; the main things to review are its local memory files, optional device-control commands, and the external atvremote CLI it may use.
Before installing, decide whether you want persistent HomePod notes in ~/homepod/ and whether direct control through atvremote should be allowed. Confirm the exact device target before any playback, volume, streaming, or pairing action, and install any external CLI only from a trusted source.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If used carelessly, the agent could change playback, volume, or media routing on the wrong household device.
The skill documents commands that can change playback state or volume, but it also requires explicit user intent, a single target, and read-only checks first, making this purpose-aligned but still worth noticing.
Confirm the user explicitly wants command execution. ... Confirm one unambiguous target (`name`, `ip`, or `id`) before mutating playback state.
Only allow direct control after confirming the exact HomePod or Apple TV target, and prefer the documented read-only checks before any mutating command.
Pairing can create lasting control access to a household device until the user revokes or changes it.
Pairing may grant the local CLI authority to control a HomePod or Apple TV, though the skill appropriately says not to store pairing secrets.
If pairing is required: ```bash atvremote -n "<target>" pair ``` - Never store pairing secrets in skill memory.
Pair only intended devices, avoid saving pairing secrets in notes, and revoke device access if it is no longer needed.
Installing or using the wrong external command could introduce risk outside this instruction-only skill.
The skill relies on an external CLI for direct control, while the provided install metadata does not install or pin that dependency; users must source it safely themselves.
Confirm `atvremote` is available on PATH before issuing control commands.
If direct control is needed, install atvremote only from a trusted source and verify which executable is on PATH before using it.
Local notes may reveal household device layout and could mislead future sessions if they become stale or inaccurate.
The skill keeps persistent local household topology and control-boundary notes that can influence later troubleshooting and activation decisions.
Create `~/homepod/memory.md` ... ## Environment Snapshot - HomePod models: - Home hub: - Network topology: - Critical accessories: - Control boundaries: - Protected targets:
Keep the memory file concise, avoid personal content or voice transcripts, and periodically review or delete outdated entries.