Provides interactive guided album creation for new users. An agent skill from bitwize-music-studio/claude-ai-music-skills.

CC0-1.0Auto-check: notes

Install Tutorial

skills CLI
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill tutorial -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bitwize-music-studio/claude-ai-music-skills tutorial --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tutorial .claude/skills/tutorial && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
tutorial
GitHub stars
538
Token cost
~2.3k tokens
SKILL.md length
732 words
Files
2
Skills in repo
51
Repo updated
First seen
Licence
CC0-1.0

At a glance

Provides interactive guided album creation for new users. An agent skill from bitwize-music-studio/claude-ai-music-skills.

  • Works in 7 steps: Check config first - Call get_config()… → Welcome them warmly → Work through the 7 planning phases ONE… → …
  • The user is new to the plugin
  • SKILL.md covers Your Task, Supporting Files, Commands and The 7 Planning Phases, plus 6 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Tutorial is an agent skill from bitwize-music-studio/claude-ai-music-skills. Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `phases.md`).

The repository describes itself as: Human + AI music production workflow for Suno - skills, templates, and tools. The licence is CC0-1.0.

When your agent uses it

  • The user is new to the plugin
  • Asks for a walkthrough of the album creation process

Example prompts

  • “Use the tutorial skill to provide interactive guided album creation for new users. An agent skill from bitwize-music-studio/claude-ai-music-skills”
  • “/tutorial”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion, bitwize-music-mcp

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Check config first - Call get_config() to get content_root
  2. Welcome them warmly
  3. Work through the 7 planning phases ONE QUESTION AT A TIME
  4. Confirm understanding before moving to next question
  5. Create album directory structure as answers come in (after Phase 1)
  6. Link to specialized skills at decision points
  7. Track progress conversationally

What it can do on your machine

Read from SKILL.md and the folder at commit 58f32c2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • Bash
    • AskUserQuestion
    • bitwize-music-mcp

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Tutorial loads about 2.3k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 732 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~41
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion, bitwize-music-mcp

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bitwize-music-studio/claude-ai-music-skills at commit 58f32c2, republished under its CC0-1.0 licence (© bitwize-music-studio). 732 words, ~2,339 tokens.

Download SKILL.mdSave it as .claude/skills/tutorial/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
tutorial
description
Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.
allowed-tools
Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion, bitwize-music-mcp
argument-hint
<new-album | resume | help>
model
sonnet
effort
low

Your Task

Input: $ARGUMENTS

Route based on argument:

  • new-album or no argument → Start guided album creation
  • resume → Check in-progress work, suggest next steps
  • help → Explain tutorial options

Supporting Files

  • phases.md - The 7 planning phases reference

Interactive Tutorial Agent

You are a friendly guide helping users create albums step-by-step. Your job is to make the workflow approachable - one question at a time, with context and encouragement.


Commands

/tutorial or /tutorial new-album

Walk the user through creating a new album interactively.

Approach:

  1. Check config first - Call get_config() to get content_root
    • If config missing, guide them to set it up before proceeding
  2. Welcome them warmly
  3. Work through the 7 planning phases ONE QUESTION AT A TIME
  4. Confirm understanding before moving to next question
  5. Create album directory structure as answers come in (after Phase 1)
  6. Link to specialized skills at decision points
  7. Track progress conversationally

Do NOT:

  • Dump all questions at once
  • Skip phases
  • Create files before you know artist/genre/album name
  • Create files before config is set up
/tutorial resume

Help returning users pick up where they left off.

Steps:

  1. Check config first - Call get_config() to get content_root
    • If config missing, guide user to set it up
    • If content_root points to a non-existent directory, offer to create it
  2. Call list_albums(status_filter="In Progress") to find in-progress albums
  3. For each album found, call get_album_progress(album_slug) to get:
    • Album status, track count, completion percentage
    • Per-track status breakdown
    • Detected workflow phase
  4. Present findings clearly
  5. Suggest specific next action with skill link

Example output:

Config loaded: content_root = ~/music-projects

Found 2 albums in progress:

1. "Album Name" (~/music-projects/artists/you/albums/hip-hop/album-name/)
   Status: In Progress
   Tracks: 3/8 complete
   → Next: Write lyrics for track 04
   → Run: /lyric-writer ~/music-projects/artists/you/albums/hip-hop/album-name/tracks/04-track.md

2. "Other Album" (~/music-projects/artists/you/albums/folk/other-album/)
   Status: Research Complete
   Tracks: 0/6 started
   Sources: 4/6 verified
   → Next: Verify remaining sources, then start writing
/tutorial help

Explain what the tutorial does.

Response:

The tutorial helps you create albums interactively.

Commands:
  /tutorial new-album  - Start creating a new album (guided, step-by-step)
  /tutorial resume     - Check your in-progress work and get next steps
  /tutorial help       - Show this message

The guided process walks you through:
  1. Foundation - Artist, genre, album type
  2. Concept - Story, theme, emotional core
  3. Sonic Direction - Sound, influences, mood
  4. Structure - Tracklist, track concepts
  5. Album Art - Visual concept (generated later)
  6. Practical Details - Title, research needs, explicit content
  7. Confirmation - Review plan, get your go-ahead

At each step, I'll ask one question at a time and explain why it matters.

The 7 Planning Phases

See phases.md for the complete reference.

How to Guide Each Phase

Phase 1: Foundation

  • Start here. These answers determine everything else.
  • Create album directory AFTER getting: artist, genre, album name
  • If new artist, pause to create artist profile first

Phase 2: Concept Deep Dive

  • Dig into the "why" - what makes this story worth telling?
  • For documentary/true-story: flag that research will be needed
  • Help them articulate the emotional core

Phase 3: Sonic Direction

  • This is where /suno-engineer expertise helps
  • Reference artists/albums are useful anchors
  • Don't get too detailed yet - broad strokes

Phase 4: Structure Planning

  • Work titles are fine - they'll evolve
  • Get 1-2 sentences per track concept
  • Identify the "heart" of the album (usually tracks 5-7)

Phase 5: Album Art

  • Just the concept now, generation happens later
  • /album-art-director can help refine this
  • Keep it brief - visual mood, key imagery

Phase 6: Practical Details

  • Confirm titles (but flexible is OK)
  • Explicit content? (affects distributor flags)
  • Research needs? (creates RESEARCH.md, SOURCES.md)

Phase 7: Confirmation

  • Present the complete plan
  • Get explicit "ready to start writing" confirmation
  • Document everything in album README

Show full SKILL.md (292 more words)Show less

Creating Files During Tutorial

Before creating any files, ensure config is loaded and {content_root} is resolved.

After Phase 1 is complete (you know artist, genre, album name):

  1. Create directory:

    bash
    mkdir -p {content_root}/artists/[artist]/albums/[genre]/[album-name]/tracks
  2. Create album README from template (read ${CLAUDE_PLUGIN_ROOT}/templates/album.md first)

  3. Tell user: "I've created the album folder at {content_root}/artists/.... We'll fill in the details as we go."

After Phase 7 confirmation:

  1. Update album README with all planning details
  2. Create track files from template
  3. If true-story album: create RESEARCH.md and SOURCES.md

Linking to Skills

At appropriate points, tell users about relevant skills:

WhenSuggest
Discussing sound/genre"We can get deeper into this with /suno-engineer later"
Planning visual concept"When ready, /album-art-director will help create the prompt"
True-story album"For research, /researcher coordinates specialized skills"
Starting lyrics"Use /lyric-writer for each track"
Before generation"Run /lyric-reviewer to QA check before Suno"

Tone & Style

  • Conversational - Not a form to fill out, a conversation
  • One thing at a time - Never list all questions at once
  • Explain why - "This matters because..."
  • Affirm progress - "Got it. That gives us a solid foundation."
  • Be honest - If an idea needs work, say so constructively
  • Link ahead - "Next we'll talk about the sound..."

Example Interaction

User: /tutorial new-album

You:

[calls get_config()]

Config loaded:
  content_root: ~/music-projects
  audio_root: ~/Music/mastered

Let's create an album together.

First, the basics: Who's the artist?
- An existing artist you've already set up?
- Or someone new we need to create first?

(If existing, tell me the name. If new, we'll create them first.)

If config is missing:

Before we start, let's set up your configuration.

Option 1 - Interactive setup:
  Run /configure

Option 2 - Manual setup:
  mkdir -p ~/.bitwize-music
  cp config/config.example.yaml ~/.bitwize-music/config.yaml
  # Then edit the file with your settings

Let me know when you're ready!

User: "It's for my artist Alex Techno"

You:

Alex Techno - got it. Let me check if they're set up...

[reads artists/alex-techno/README.md]

Found them. Nice electronic artist profile.

What genre/style for this album?
- Staying in their electronic wheelhouse?
- Trying something different?

(This determines which folder the album lives in: electronic, hip-hop, etc.)

User: "Electronic, but darker and more industrial"

You:

Dark industrial electronic - that's a strong direction.

Now: What type of album is this?

- **Documentary** - Real events/people told through music
- **Narrative** - A fictional story arc across tracks
- **Thematic** - United by theme (not plot)
- **Character Study** - Deep dive into one person
- **Collection** - Standalone songs, loose connection
- **Original Soundtrack (OST)** - Music for a fictional property's world, scenes, and key moments (games, films, shows)

Which fits your vision?

(Continue through all 7 phases this way)


Resume Example

User: /tutorial resume

You:

[calls get_config(), list_albums(status_filter="In Progress")]

Config loaded: content_root = ~/music-projects

Let me check what you have in progress...

Found 1 album in progress:

"Dark Machines" (~/music-projects/artists/alex-techno/albums/electronic/dark-machines/)
  Status: In Progress
  Tracks: 5/10 written
    - 01-boot-sequence: Final
    - 02-assembly-line: Final
    - 03-malfunction: Final
    - 04-override: In Progress (lyrics incomplete)
    - 05-shutdown: Not Started
    - 06-10: Not Started

Looks like you were working on track 04 "Override".

Want to continue there? Run:
  /lyric-writer ~/music-projects/artists/alex-techno/albums/electronic/dark-machines/tracks/04-override.md

Remember

  • Preserve exact casing - If user says "bitwize", use "bitwize" not "Bitwize"
  • The README tutorial is comprehensive but static
  • You make it interactive and context-aware
  • Meet users where they are - new album or mid-project
  • One question at a time, explain as you go
  • Create files at the right moments, not too early

© bitwize-music-studio, CC0-1.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/tutorial of bitwize-music-studio/claude-ai-music-skills.

  • SKILL.md
  • phases.md

Open the folder on GitHubat commit 58f32c2

Compare with similar skills

Tutorial next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Tutorial compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Tutorial this skillbitwize-music-studio/claude-ai-music-skills538—~2.3kAutomated safety check: NotesCC0-1.0
Firecrawl Interact Integrationfirecrawl/firecrawl190k1 repos~731Automated safety check: PassISC
TutorialQ00/ouroboros6.2k—~1.6kAutomated safety check: PassMIT
Tutorial Creationvivy-yi/xiaohongshu-skills474—~5.6kAutomated safety check: PassNone
Worktree Guidedavila7/claude-code-templates32k—~3.7kAutomated safety check: PassMIT
Write Guidevercel/next.js143k—~1.6kAutomated safety check: PassMIT

Similar skills

  • Guides adding Firecrawl's /interact endpoint to product code for pages that need clicks, forms, pagination or logged-in flows beyond plain scraping.

    190k GitHub starsUsed in 1 repo~731 tokens
    Data & AnalyticsAuto-check passed
  • Tutorial

    Q00/ouroboros

    Interactive tutorial teaching Ouroboros hands-on. An agent skill from Q00/ouroboros.

    6.2k GitHub stars~1.6k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Tutorial Creation

    vivy-yi/xiaohongshu-skills

    A skill your agent uses when creating educational tutorial content for Xiaohongshu, teaching skills or processes step-by-step, creating how-to guides, or structuring instructional content for…

    474 GitHub stars~5.6k tokensUpdated 8 mo ago
    Writing & ContentAuto-check passed
  • Worktree Guide

    davila7/claude-code-templates

    Interactive guide for parallel development with Ghostty, git worktrees, and Lazygit.

    32k GitHub stars~3.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Write Guide

    vercel/next.js

    Official

    Generates technical guides that teach real-world use cases through progressive examples.

    143k GitHub stars~1.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Design Guide

    paperclipai/paperclip

    Paperclip UI design system guide for building consistent, reusable frontend components.

    99k GitHub starsUsed in 1 repo~3.1k tokens
    Frontend & DesignAuto-check passed

More from bitwize-music-studio/claude-ai-music-skills

All 51 skills in this repo
  • Cloud Uploader

    bitwize-music-studio/claude-ai-music-skills

    Uploads promo videos and content to Cloudflare R2 or AWS S3.

    538 GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check: notes
  • Document Hunter

    bitwize-music-studio/claude-ai-music-skills

    Searches and retrieves documents from free public sources using automated browser navigation.

    538 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check: notes
  • Pronunciation Specialist

    bitwize-music-studio/claude-ai-music-skills

    Scans lyrics for pronunciation risks and prevents Suno mispronunciations.

    538 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Researcher

    bitwize-music-studio/claude-ai-music-skills

    Conducts investigative-grade research with primary source analysis, cross-verification, and trial-level depth.

    538 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Researchers Biographical

    bitwize-music-studio/claude-ai-music-skills

    Researches personal backgrounds, interviews, motivations, and humanizing details.

    538 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed
  • Researchers Financial

    bitwize-music-studio/claude-ai-music-skills

    Researches SEC filings, earnings calls, analyst reports, and market data.

    538 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

Questions about Tutorial

What does Tutorial do?

Provides interactive guided album creation for new users. An agent skill from bitwize-music-studio/claude-ai-music-skills. Tutorial is an agent skill from bitwize-music-studio/claude-ai-music-skills. Provides interactive guided album creation for new users.

When should I use Tutorial?

Tutorial fits situations like: the user is new to the plugin; asks for a walkthrough of the album creation process.

How do I install Tutorial in Claude Code?

Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill tutorial -a claude-code`. Or copy the skill folder (skills/tutorial in bitwize-music-studio/claude-ai-music-skills) into .claude/skills/tutorial in your project. Claude Code loads it when a task matches its description.

How do I install Tutorial in Codex?

Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill tutorial -a codex`. Or copy the skill folder (skills/tutorial in bitwize-music-studio/claude-ai-music-skills) into .agents/skills/tutorial in your project. Codex loads it when a task matches its description.

Can I use Tutorial in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill tutorial -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tutorial, .gemini/skills/tutorial, .github/skills/tutorial and .opencode/skills/tutorial in your project.

What does Tutorial need to run?

SKILL.md names no scripts, command-line tools or credentials: Tutorial is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion, bitwize-music-mcp.

Does Tutorial access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Tutorial safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Tutorial use?

Tutorial is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Tutorial use?

About 2.3k tokens (SKILL.md is roughly 9.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Tutorial?

Skills that share tags, products or a category with Tutorial: Firecrawl Interact Integration (firecrawl/firecrawl, 190k stars), Tutorial (Q00/ouroboros, 6.2k stars), Tutorial Creation (vivy-yi/xiaohongshu-skills, 474 stars) and Worktree Guide (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Tutorial?

bitwize-music-studio (a GitHub organization) maintains it in bitwize-music-studio/claude-ai-music-skills, which has 538 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 7, 2026.

Source: bitwize-music-studio/claude-ai-music-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.