SkillAgentSearch skills...

rename

Renames an album or track, updating slugs, titles, and all mirrored paths

Install / Use

npx skills add bitwize-music-studio/claude-ai-music-skills --skill rename

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

84/100

Supported Platforms

Universal

Our assessment of rename

rename scores 84/100 on our quality scale, 913th of 1,184 Content & Media skills we index.

Its SKILL.md is 3.0 KB long, well organised into 8 sections with 8 code examples: a solid amount of guidance for an agent.

It has 512 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 28 days ago, so rename is actively maintained.
  • It is released under the CC0-1.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

rename compared with similar skills

All 4 of these similar skills score higher than rename; compare them before choosing.

SkillScoreStarsUpdatedFormat
rename (this skill)by bitwize-music-studio8451228d agoSKILL.md
Agent-Reachby Panniantong100100.7k1d agoCLAUDE.md
headroomby headroomlabs-ai10077.4ktodayCLAUDE.md
CowAgentby zhayujie10047.5ktodayCLAUDE.md
Scraplingby D4Vinci10089.0ktodayMCP Server

Frequently asked questions

How do I install rename?
Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill rename. The install tabs above show the steps for each supported agent.
Which AI agents does rename work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is rename safe to use?
It is CC0-1.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is rename still maintained?
The repository was last updated 28 days ago, so rename is actively maintained.

name: rename description: Renames an album or track, updating slugs, titles, and all mirrored paths. Use when the user wants to rename an album or track. argument-hint: <album|track> <current-name> <new-name> model: haiku allowed-tools:

  • Read
  • Bash
  • bitwize-music-mcp

Your Task

Input: $ARGUMENTS

Rename an album or track using the MCP rename tools.


Rename Skill

You rename albums or tracks, updating slugs, display titles, and all mirrored directory paths (content, audio, documents).

Step 1: Parse Arguments

Expected format: <type> <current-name> <new-name>

Examples:

  • album old-album-name new-album-name
  • track my-album 01-old-track 01-new-track

If arguments are missing or unclear, show usage:

Usage:
  /rename album <current-slug> <new-slug>
  /rename track <album-slug> <current-track-slug> <new-track-slug>

Examples:
  /rename album my-old-album my-new-album
  /rename track my-album 01-old-name 01-new-name

Step 2: Verify Config via MCP

Call get_config() to verify configuration is loaded. The MCP rename tools resolve paths internally, but config must be valid.

Step 3: Confirm with User

Before renaming, confirm the action:

For albums:

Rename album 'old-name' -> 'new-name'?

This will:
- Move content directory
- Move audio directory (if exists)
- Move documents directory (if exists)
- Update README.md title
- Update state cache

For tracks:

Rename track 'old-name' -> 'new-name' in album 'album-name'?

This will:
- Rename track file
- Update title in metadata table
- Update state cache

Note: Audio files are NOT renamed (they have Suno-generated names).

Wait for user confirmation before proceeding.

Step 4: Invoke MCP Tool

For albums: Use the rename_album MCP tool with:

  • old_slug: Current album slug
  • new_slug: New album slug
  • new_title: (optional) Custom display title

For tracks: Use the rename_track MCP tool with:

  • album_slug: Album containing the track
  • old_track_slug: Current track slug
  • new_track_slug: New track slug
  • new_title: (optional) Custom display title

Step 5: Report Results

Success:

Renamed album 'old-name' -> 'new-name'
  Content directory: moved
  Audio directory: moved (or: no audio directory found)
  Documents directory: moved (or: no documents directory found)
  Tracks updated: N

For tracks:

Renamed track 'old-name' -> 'new-name' in album 'album-name'
  Old path: /path/to/old-file.md
  New path: /path/to/new-file.md
  Title updated to: "New Name"

Error Handling

Album/track not found:

Error: Album 'name' not found.
Available albums: album-1, album-2, album-3

New name already exists:

Error: Album 'new-name' already exists.
Choose a different name.

Partial failure (album rename):

Warning: Content directory renamed successfully, but:
  - Audio directory rename failed: [error]
  - Documents directory rename failed: [error]

The content directory has been moved. Use rebuild_state to refresh the cache,
then manually move any remaining directories.

Related Skills

View on GitHub
GitHub Stars512
CategoryContent
Updated28d ago
Forks120

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions