Sun to Spotify
ReviewAudited by ClawScan on May 14, 2026.
Overview
The skill is coherent, but it can automatically create and upload generated audio to a Spotify show before user review, while also requiring external installers and account tokens.
Install only if you are comfortable giving the workflow access to your Sun and Spotify accounts. Before allowing uploads, confirm the show name, visibility, and deletion options, and ask the agent to let you review generated audio before publishing or uploading it to Spotify.
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.
Unreviewed generated audio could be uploaded to Spotify, causing unwanted or incorrect content to appear in the user's podcast/show workflow.
The skill directs the agent to upload generated episodes to Spotify immediately as they finish, which can mutate a third-party account/show before the user has reviewed the completed audio.
As soon as episode 1 lands, start uploading to Spotify. Don't block on `SUCCESS` before kicking off Spotify uploads
Require explicit user confirmation before creating a Spotify show or uploading each episode, and clearly explain visibility, deletion, and rollback options.
Installing the CLI may execute external code from outside the skill package.
The recommended install path executes a remote installer, and the runnable installer code is not included in the reviewed artifacts.
curl -fsSL https://sunapp-ai.github.io/sun-to-spotify/install.sh | bash
Prefer isolated package-manager installs when possible, review the installer source, and pin trusted versions for repeatable installs.
Anyone who can read the credential file or API token may be able to act as the user for the Sun service.
The workflow uses account authentication and stores a refresh token locally; this is disclosed and purpose-aligned, but it is sensitive credential material.
The refresh token is persisted at `~/.config/sun/credentials.json` with mode `0600` on Unix.
Protect the credential file, avoid sharing it unnecessarily, use least-privilege tokens where available, and revoke tokens when no longer needed.
If a callback URL points to an untrusted endpoint, generated audio links and job metadata may be exposed there.
The optional webhook sends job metadata and signed audio URLs to a user-supplied external endpoint.
callback_url ... The server POSTs `{event, job_id, episode_id, episode_number, title, audio_url}` to this URL every time an episode finishes generating.Only use callback URLs you control and trust, and treat signed audio URLs as sensitive temporary access links.