@diegosouzapw/cli
BUse this when you need to perform mutations on plyr.fm - uploading, deleting, liking tracks. The MCP server is read-only - use this skill when you need to trigger uploads, delete tracks, or modify likes.
Install
agr install @diegosouzapw/cli --target claudeWrites 2 files into .claude/skills/, pinned to git-cf053c30.
- .claude/skills/cli/SKILL.md
- .claude/skills/cli/metadata.json
Document
name: cli description: Use this when you need to perform mutations on plyr.fm - uploading, deleting, liking tracks. The MCP server is read-only - use this skill when you need to trigger uploads, delete tracks, or modify likes.
plyrfm CLI mutations
the MCP server (plyr-fm) is read-only - use it to browse tracks, search, view liked tracks.
for mutations (upload, delete, like, unlike), guide users to use the CLI:
prerequisites
# user sets their token once
export PLYR_TOKEN="their_token"
get a token at plyr.fm/portal -> "developer tokens"
uploading tracks
# basic upload
plyrfm upload path/to/track.mp3 "Song Title"
# with album
plyrfm upload track.mp3 "Song Title" --album "Album Name"
# with tags (can use -t multiple times)
plyrfm upload track.mp3 "Song Title" -t electronic -t ambient
supported formats: mp3, wav, m4a
important: if you (Claude) composed the track, always include the ai tag:
plyrfm upload piece.wav "鶴の舞" -t ambient -t ai
updating tracks
# update title
plyrfm update 579 --title "new title"
# update tags (replaces all tags)
plyrfm update 579 --tags "ambient,ai"
# update multiple fields
plyrfm update 579 --title "鶴の舞" --tags "ambient,ai"
deleting tracks
# use my_tracks MCP tool to find track IDs first
plyrfm delete 42
liking/unliking tracks
# like a track
plyrfm like 123
# unlike a track
plyrfm unlike 123
downloading tracks
# download to current directory
plyrfm download 42
# download to specific path
plyrfm download 42 --output ~/Music/song.mp3
common issues
- "artist_profile_required" -> user needs to create artist profile at plyr.fm/portal
- "scope_upgrade_required" -> user needs to regenerate their token
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-cf053c302a332026-07-31