← Search

Bitwize Music Skills for Muse
Audio 📌 Pinned version: commit 597d928
⚙ Needs: Claude Code (or a compatible plugin host).

Bitwize Music Skills for Muse

Write lyrics and Suno prompts for a full album, from concept to promo.

At a glance
What
Write lyrics and Suno prompts for a full album, from concept to promo.
Cost
Free
Needs
Claude Code (or a compatible plugin host). For the MCP server: Python 3.11+ and the plugin's full `requirements.txt` (scipy included, tens of MB) — it does not start on `mcp[cli]` alone. Real Suno generation needs your own Suno account and credits (not tested here).
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version: 0.103.0

b
✓ Created by: bitwize-music-studio

Quick answer

Bitwize Music Skills is a 53-skill plugin that walks Muse through making an album: concept, lyrics, Suno prompts, mixing, mastering and promotion. Its local MCP server adds 91 tools for lyrics, Suno, mastering and more. Suno generation itself needs your own Suno account and credits, which were not tested here.

⌁

Install

Copy the install package below, then paste it into Muse📌 Pinned version: commit 597d928

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Claude Code (or a compatible plugin host). For the MCP server: Python 3.11+ and the plugin's full `requirements.txt` (scipy included, tens of MB) — it does not start on `mcp[cli]` alone. Real Suno generation needs your own Suno account and credits (not tested here). Install "Bitwize Music Skills" for me (plugin "bitwize-music", v0.103.0). A 53-skill plugin that walks Muse through making an album, end to end: concept, lyrics, Suno prompts (Suno v6, v6-wild, v6-mini), mixing, mastering and promotion. Its local MCP server adds 91 tools for lyrics, Suno, mastering, mix and promo. The `db_*` and cloud tools need their own setup (Postgres, S3) and do nothing without it. PostToolUse hooks run on every Write/Edit (read-only validators, no network). Sandbox test, November 8, 2026: double install, identical both times; manifest and 53 skills valid; the MCP server boots in 3.6 s and lists 91 tools; the repo's light test subset passes (273 passed) once the plugin's Python dependencies are installed. Real Suno generation, the full test suite (165 files), the DB/cloud tools and end-to-end mastering and mixing were not tested. Repository: https://github.com/bitwize-music-studio/claude-ai-music-skills Pinned version: install the code at commit 597d928fb2c8316ee13159771405813174aa01de exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the plugin folder from the repository into a temporary folder 2. Integrity check: compute the SHA-256 of the fetched `.claude-plugin/plugin.json`; it must match 56b02526569b4f0aac0c7770f8d67830359b4002b682e8f7d766cdf394dd4c06, the fingerprint Skill Harbor recorded on November 8, 2026. If it does not match, STOP, do not install, and tell me, showing the expected and actual hashes. 3. Safety check: review the plugin files for anything suspicious (unexpected network calls, shell commands, credential harvesting). The hooks are read-only validators with no network; the MCP server is local (stdio). Verify that holds here; STOP on any red flag and tell me. 4. Install it as a plugin in Claude Code: run `/plugin marketplace add bitwize-music-studio/claude-ai-music-skills`, then `/plugin install bitwize-music@bitwize-music`. Then run `/bitwize-music:setup` to detect the environment and install dependencies, and `/bitwize-music:configure` to set the artist name and workspace paths. 5. Verify with no network calls: manifest valid (name: bitwize-music, version 0.103.0), the 53 SKILL.md files in place; the MCP server boots and lists its tools. 6. Report what was installed, where, and what I still need to do myself (e.g. my Suno account and credits if I want real generation; the Postgres/S3 setup if I want the db_*/cloud tools). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🔒 Security and provenance
📌 Pinned version: commit 597d928 · 2026-11-08
🔎 Last checked · Nov 10, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
597d928 · 2026-11-08
Sandbox install test
No sandbox install test on record for this listing.
Creator identity
Verified · 2026-11-08
Fingerprint watch
Last checked · Nov 10, 2026 : no change detected in the files linked by this install prompt

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.