Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Analyzes album state and recommends the optimal next action.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill next-step -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills next-step --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/next-step .claude/skills/next-step && rm -rf skills-srcUse ~/.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/
Install the "next-step" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/next-step into .claude/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/next-stepType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill next-step -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills next-step --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/next-step .agents/skills/next-step && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "next-step" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/next-step into .agents/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill next-step -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills next-step --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/next-step .cursor/skills/next-step && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "next-step" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/next-step into .cursor/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills.git --path skills/next-step--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill next-step -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills next-step --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/next-step .gemini/skills/next-step && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "next-step" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/next-step into .gemini/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install bitwize-music-studio/claude-ai-music-skills next-stepInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill next-step -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/next-step .github/skills/next-step && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "next-step" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/next-step into .github/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill next-step -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install bitwize-music-studio/claude-ai-music-skills next-step --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/next-step .opencode/skills/next-step && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "next-step" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/next-step into .opencode/skills/next-step/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "next-step", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
next-stepAnalyzes album state and recommends the optimal next action.
Next Step is an agent skill from bitwize-music-studio/claude-ai-music-skills. Analyzes album state and recommends the optimal next action. Use when the user asks "what should I do next?" or "what's left to do?"
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Human + AI music production workflow for Suno - skills, templates, and tools. The licence is CC0-1.0.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 58f32c2. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepbitwize-music-mcpFrom allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Next Step loads about 1.6k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 320 words of instructions outside code blocks.
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.
The automated check found no risky patterns in SKILL.md.
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.
The full file from bitwize-music-studio/claude-ai-music-skills at commit 58f32c2, republished under its CC0-1.0 licence (© bitwize-music-studio). 320 words, ~1,631 tokens.
.claude/skills/next-step/SKILL.md (or your agent's skills folder).Input: $ARGUMENTS (optional album name)
Analyze current project state and recommend the single best next action.
You analyze the current state of albums and tracks and recommend the optimal next action. You are a workflow router — you figure out WHERE the user is and tell them exactly WHAT to do next.
get_session() — check last_album from session contextget_album_progress(album_slug) to analyze itlist_albums() to find all albums, then get_album_progress() on each to pick the most actionablefind_album(name) — fuzzy match by name, slug, or partialget_album_progress(album_slug) — get status, phase, track countsAnalyze album and track statuses to determine the optimal next action.
Instrumental detection: Check each track's frontmatter for instrumental: true or Track Details table for **Instrumental** | Yes. Instrumental tracks bypass the lyrics workflow (lyric-writer, pronunciation-specialist, lyric-reviewer) and go directly to /bitwize-music:suno-engineer for Style Box creation.
Album Status = "Concept"
→ "Define the album concept. Run the 7 Planning Phases with /bitwize-music:album-conceptualizer"
Album Status = "Research Complete"
→ Any tracks Sources Pending?
YES → "Sources need verification. Review SOURCES.md and verify each source."
NO → First "Not Started" track instrumental?
YES → "Create Style Box for instrumental track [name]. Use /bitwize-music:suno-engineer"
NO → "Ready to write! Pick a track and use /bitwize-music:lyric-writer"
Album has tracks with status "Not Started"
→ First not-started track instrumental?
YES → "Create Style Box for instrumental track [name]. Use /bitwize-music:suno-engineer directly"
NO → "Write lyrics for track [first not-started track]. Use /bitwize-music:lyric-writer"
Album has tracks with status "In Progress" (lyrics partially written)
→ "Finish lyrics for track [first in-progress track]. Use /bitwize-music:lyric-writer"
Album has tracks with status "Sources Pending"
→ "Verify sources for track [name]. Check SOURCES.md, then update sources_verified field."
All tracks have lyrics (or Style Box for instrumentals), none generated
→ Has vocal tracks?
YES → "Run /bitwize-music:pronunciation-specialist on vocal tracks, then /bitwize-music:lyric-reviewer for final QC, then /bitwize-music:pre-generation-check to validate all gates (instrumental tracks auto-skip lyrics gates)."
NO (all instrumental) → "All Style Boxes ready! Run /bitwize-music:pre-generation-check to validate gates before generating on Suno."
Some tracks generated, some not
→ Any Generated tracks without ✓ in Generation Log Rating?
YES → "Track [name] needs review. Listen and approve (mark ✓ in Generation Log) or regenerate.
Style issue → /bitwize-music:suno-engineer to revise Style Box, then regenerate
Lyrics issue → /bitwize-music:lyric-writer to fix lyrics, then regenerate
Bad luck → Regenerate on Suno (non-deterministic, same settings may give better result)"
NO → "Generate track [first un-generated track] on Suno. Use /bitwize-music:suno-engineer"
All tracks generated, none Final
→ "All tracks generated! Review each track:
Mark keepers with ✓ in Generation Log, regenerate rejected ones.
Once all approved, batch-approve:
Use update_track_field(album_slug, track_slug, 'status', 'Final') for each.
Once all Final, album advances to Complete."
All tracks generated, some Final
→ Any Generated (non-Final) without ✓?
YES → "Review track [name] — approve (✓) or regenerate"
NO → "All reviewed! Batch-approve remaining: update_track_field(album_slug, track_slug, 'status', 'Final') for each.
Then import audio with /bitwize-music:import-audio, then master with /bitwize-music:mastering-engineer"
All tracks Final
→ "All tracks approved! Import audio with /bitwize-music:import-audio, then master with /bitwize-music:mastering-engineer"
Album Status = "Complete"
→ "Album is complete! Release with /bitwize-music:release-director"
Album Status = "Released"
→ "This album is released! Consider promotional content with /bitwize-music:promo-director"
→ Also suggest: "Start a new album? Check your ideas with /bitwize-music:album-ideas list"NEXT STEP
=========
Album: [name] ([genre]) — [status]
Progress: [X/Y tracks complete]
RECOMMENDED ACTION:
[Clear, specific instruction with skill name]
WHY:
[One sentence explaining why this is the right next step]
AFTER THAT:
[Brief mention of what comes after this step]If no album specified and multiple exist:
NEXT STEP
=========
You have X albums. Here's the most actionable:
PRIORITY 1: [album-name] ([genre])
Status: [status] | Progress: [X/Y tracks]
→ [Recommended action]
Also in progress:
- [album-2] — [brief status]
- [album-3] — [brief status]
Or start something new:
- /bitwize-music:album-ideas list (X ideas pending)
- /bitwize-music:new-albumWhen multiple albums are in progress, prioritize:
© 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
Just SKILL.md in skills/next-step of bitwize-music-studio/claude-ai-music-skills.
Open the folder on GitHubat commit 58f32c2
Next Step 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Next Step this skillbitwize-music-studio/claude-ai-music-skills | 540 | — | ~1.6k | Automated safety check: Pass | CC0-1.0 | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| Cost Optimizeruvnet/ruflo | 74k | — | ~997 | Automated safety check: Notes | MIT | |
| Cost Optimization Analyzerjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~576 | Automated safety check: Pass | MIT | |
| SQL Optimizationgithub/awesome-copilot | 40k | 2 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Prompt Optimizeraffaan-m/ECC | 276k | 5 repos | ~3.8k | Automated safety check: Pass | MIT |
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
ruvnet/ruflo
Analyze token usage patterns and recommend cost optimizations with estimated savings
jeremylongshore/tons-of-skills-marketplace
Analyze cost optimization analyzer operations. An agent skill from jeremylongshore/tons-of-skills-marketplace.
github/awesome-copilot
Universal SQL performance optimization assistant for comprehensive query tuning, indexing strategies, and database performance analysis across all SQL databases (MySQL, PostgreSQL, SQL Server…
affaan-m/ECC
Analyze draft prompts, detect intent and missing context, match ECC commands, skills, and agents, and output a ready-to-paste optimized prompt with diagnosis and rationale — advisory only, never…
ruvnet/ruflo
Agent skill for performance-optimizer - invoke with $agent-performance-optimizer
bitwize-music-studio/claude-ai-music-skills
Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases.
bitwize-music-studio/claude-ai-music-skills
Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown.
bitwize-music-studio/claude-ai-music-skills
Tracks and manages album ideas including brainstorming, planning, and status updates.
bitwize-music-studio/claude-ai-music-skills
Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard.
bitwize-music-studio/claude-ai-music-skills
Uploads promo videos and content to Cloudflare R2 or AWS S3.
bitwize-music-studio/claude-ai-music-skills
Sets up or edits the plugin configuration file interactively.
Analyzes album state and recommends the optimal next action. Next Step is an agent skill from bitwize-music-studio/claude-ai-music-skills. Analyzes album state and recommends the optimal next action.
Next Step fits situations like: the user asks what should I do next?; whats left to do?.
Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill next-step -a claude-code`. Or copy the skill folder (skills/next-step in bitwize-music-studio/claude-ai-music-skills) into .claude/skills/next-step in your project. Claude Code loads it when a task matches its description.
Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill next-step -a codex`. Or copy the skill folder (skills/next-step in bitwize-music-studio/claude-ai-music-skills) into .agents/skills/next-step in your project. Codex loads it when a task matches its description.
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 next-step -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/next-step, .gemini/skills/next-step, .github/skills/next-step and .opencode/skills/next-step in your project.
SKILL.md names no scripts, command-line tools or credentials: Next Step is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep, bitwize-music-mcp.
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.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Next Step 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.
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Next Step: Analyze GitHub Action Logs (withastro/astro, 63k stars), Cost Optimize (ruvnet/ruflo, 74k stars), Cost Optimization Analyzer (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and SQL Optimization (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
bitwize-music-studio (a GitHub organization) maintains it in bitwize-music-studio/claude-ai-music-skills, which has 540 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.