Amateur Radio DX Monitor
PassAudited by ClawScan on May 1, 2026.
Overview
This ham-radio DX monitor is coherent and purpose-aligned, but users should notice that it can run recurring checks, contact public DX cluster servers, and store station/profile details locally or in agent context.
This looks appropriate for a ham-radio DX monitoring skill. Before installing, decide whether you are comfortable sending your callsign to public DX cluster nodes, storing station/QTH details in config or TOOLS.md, and creating any recurring cron jobs. Run it as a normal user, not root, and note that the code uses `/tmp/dx-monitor-state.json` for monitor state.
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 enabled, monitoring will continue on a schedule and may keep invoking the agent until the cron job is removed.
The skill recommends creating a recurring OpenClaw cron job that periodically triggers the agent to check DX clusters.
cron add --name "DX Monitor" --schedule "*/5 * * * *" --payload 'systemEvent:Check DX cluster for rare spots' --sessionTarget main
Only add the cron job if you want ongoing alerts, review the schedule, and know how to disable or delete the job later.
Your callsign and cluster activity may be visible to the selected public DX cluster service.
The script connects to external DX cluster hosts over telnet-style sockets and sends the selected callsign as the login identifier.
self.sock.connect((self.host, self.port)) ... self.sock.sendall(f"{self.callsign}\n".encode())Use only callsigns and station details you are comfortable sending to public DX cluster nodes.
Callsign, approximate location, station power, antenna details, and DXCC interests may become persistent agent context or local config data.
The AI-mode documentation suggests storing station profile details in persistent OpenClaw tool/context documentation, and the included config also stores QTH and station preferences.
**Your station:** - Callsign: W5??? - QTH: Fort Worth, TX (EM12) - Power: 100W - Needed DXCC: VP8, VK0, 3Y0, ZL, VK, ZS, P5, BS7
Review `dx-ai-config.json` and any TOOLS.md additions before sharing them; omit exact location or callsign if that information is privacy-sensitive.
Users may look in the wrong place for state or assume it is kept in their home directory when it is actually stored in a temporary path.
The documentation gives inconsistent state-file locations, and the code defines the state file under `/tmp`.
State is saved to `~/dx-monitor-state.json` (in your home directory, not /tmp). ... **State Tracking:** `/tmp/dx-monitor-state.json`
Treat `/tmp/dx-monitor-state.json` as the effective state path unless the skill is updated; consider moving the state file if you want it under your home directory.