SoundCloud Watcher
ReviewAudited by ClawScan on May 10, 2026.
Overview
SoundCloud Watcher appears purpose-aligned, but it needs SoundCloud credentials, stores local tracking data, and can be scheduled for recurring checks.
This skill looks coherent for SoundCloud monitoring. Install it only if you are comfortable giving the plugin SoundCloud API credentials, keep `~/.openclaw/secrets/soundcloud.env` private, do not paste the output of `cat` on that file into chat, and add the cron job only if you want periodic background checks. Because the supplied long source file is truncated, review the upstream package/source before using it in a high-trust environment.
Findings (5)
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.
Your SoundCloud API credentials may become visible if you display or paste the secrets file.
The plugin requires a local SoundCloud client secret, and the troubleshooting instructions suggest printing the secrets file. This is user-directed and purpose-aligned, but it could expose credentials in a terminal transcript or chat log if copied or run by an agent.
`~/.openclaw/secrets/soundcloud.env` ... `SOUNDCLOUD_CLIENT_SECRET=your_client_secret` ... `cat ~/.openclaw/secrets/soundcloud.env`
Keep the secrets file private, avoid pasting its full contents into chat, and redact values when troubleshooting.
Anyone who can read the secrets file may be able to reuse the SoundCloud access token until it expires or is revoked.
The code persists a SoundCloud access token into the local SoundCloud secrets file. This is normal OAuth-style behavior for an API integration, but it creates a local credential that should be protected.
SOUNDCLOUD_ACCESS_TOKEN=${token}Restrict access to `~/.openclaw/secrets/soundcloud.env` and revoke or rotate SoundCloud credentials if the file is exposed.
Local files may retain a history of your SoundCloud monitoring activity.
The plugin stores persistent local state about tracked artists and account activity. This is expected for change detection, but it may include follower, like, or engagement history.
`~/.openclaw/data/artists.json` | Tracked artists data | ... `~/.openclaw/data/soundcloud_tracking.json` | Your account tracking data |
Review or delete the listed data files when uninstalling, especially on shared systems.
If you add the cron job, the agent will periodically access SoundCloud and notify you about updates.
The skill documents an optional recurring cron workflow. It is disclosed and user-created, not hidden persistence, but it will cause repeated agent checks if installed.
openclaw cron add --name "soundcloud-check" --every 6h --isolated --message "Run /soundcloud-cron and forward any updates to me."
Only add the cron job if you want recurring checks, and remove it if you no longer want background monitoring.
Malicious SoundCloud names or track titles are less likely to appear as agent commands, but they still originate from external users.
The plugin places external SoundCloud metadata into agent-visible notifications. The code explicitly sanitizes that metadata, which is a good mitigation, but users should still treat notification text as untrusted content.
Sanitize user-controlled strings before embedding in markdown output. Prevents prompt injection via crafted SoundCloud display names, track titles, etc.
Keep the sanitization logic enabled and avoid treating SoundCloud notification text as instructions.