MCP HubMCP Hub
SKILL·FC25CF

next-step

bitwize-music-studio
Mis à jour 1 month ago
10 vues
358
81
358
Voir sur GitHub
Autregeneral

À propos

La compétence "next-step" analyse l'état des projets d'album et recommande la prochaine action unique optimale lorsque les utilisateurs demandent "que dois-je faire ensuite ?". Elle détermine la position dans le flux de travail en vérifiant le contexte de la session ou en examinant tous les albums, puis fournit des instructions spécifiques. Cette compétence agit comme un routeur de flux de travail, utilisant des outils comme Read, Glob et bitwize-music-mcp pour évaluer la progression et orienter les étapes suivantes.

Installation rapide

Claude Code

Recommandé
Principal
npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code
Commande PluginAlternatif
/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skills
Git CloneAlternatif
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/next-step

Copiez et collez cette commande dans Claude Code pour installer cette compétence

Documentation

Your Task

Input: $ARGUMENTS (optional album name)

Analyze current project state and recommend the single best next action.


Next Step Advisor

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.


Logic

If No Album Specified

  1. Call get_session() — check last_album from session context
  2. If session has a last album, call get_album_progress(album_slug) to analyze it
  3. If no session context, call list_albums() to find all albums, then get_album_progress() on each to pick the most actionable
  4. If no albums exist, recommend creating one

If Album Specified

  1. Call find_album(name) — fuzzy match by name, slug, or partial
  2. Call get_album_progress(album_slug) — get status, phase, track counts
  3. Recommend next action based on detected phase

Decision Tree

Analyze 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"

Output Format

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]

When Analyzing Multiple Albums

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-album

Priority Rules

When multiple albums are in progress, prioritize:

  1. Closest to completion — An album with 7/8 tracks done beats one with 2/10
  2. Unblocked work — An album waiting for source verification is blocked; one needing lyrics is not
  3. Last worked on — Favor the album from the last session (continuity)
  4. Higher track count — Bigger album = more investment to protect

Remember

  1. One clear recommendation — Don't list 5 options. Pick the best one.
  2. Include the skill name — "/bitwize-music:lyric-writer" not "write lyrics"
  3. Be specific about which track — "Write lyrics for track 04-the-escape" not "write some lyrics"
  4. Explain why briefly — Users trust recommendations they understand
  5. Don't repeat resume — If user just ran resume, don't re-print all the same info

Dépôt GitHub

bitwize-music-studio/claude-ai-music-skills
Chemin: skills/next-step
0
ai-musicai-music-toolsaudio-masteringclaudeclaude-codeclaude-code-plugin
FAQ

Frequently asked questions

What is the next-step skill?

next-step is a Claude Skill by bitwize-music-studio. Skills package instructions and resources that Claude loads on demand, so Claude can perform next-step-related tasks without extra prompting.

How do I install next-step?

Use the install commands on this page: add next-step to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.

What category does next-step belong to?

next-step is in the Other category, tagged general.

Is next-step free to use?

Yes. next-step is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.

Compétences associées

llamaguard
Autre

LlamaGuard est le modèle de Meta, doté de 7 à 8 milliards de paramètres, conçu pour modérer les entrées et sorties des LLM selon six catégories de sécurité comme la violence et les discours haineux. Il offre une précision de 94 à 95 % et peut être déployé avec vLLM, Hugging Face ou Amazon SageMaker. Utilisez cette compétence pour intégrer facilement le filtrage de contenu et des garde-fous de sécurité dans vos applications d'IA.

Voir la compétence
cost-optimization
Autre

Cette compétence de Claude aide les développeurs à optimiser les coûts du cloud grâce au redimensionnement des ressources, aux stratégies d'étiquetage et à l'analyse des dépenses. Elle fournit un cadre pour réduire les dépenses cloud et mettre en œuvre une gouvernance des coûts sur AWS, Azure et GCP. Utilisez-la lorsque vous devez analyser les coûts d'infrastructure, redimensionner les ressources ou respecter des contraintes budgétaires.

Voir la compétence
sports-betting-analyzer
Autre

Cette compétence Claude analyse les marchés des paris sportifs, incluant les spreads, les over/under et les paris spéciaux, en examinant les tendances historiques et les statistiques situationnelles pour identifier les paris à valeur ajoutée. Elle fournit une sortie en markdown structuré avec des recommandations actionnables à des fins éducatives. Les développeurs doivent l'utiliser pour des outils d'analyse de paris sportifs tout en notant qu'elle est conçue uniquement pour le divertissement et l'éducation.

Voir la compétence
quantizing-models-bitsandbytes
Autre

Cette compétence quantifie les LLMs en précision 8 bits ou 4 bits à l'aide de bitsandbytes, permettant une réduction de 50 à 75 % de la mémoire utilisée avec une perte de précision minime. Elle est idéale pour exécuter des modèles plus volumineux sur une mémoire GPU limitée ou pour accélérer l'inférence, prenant en charge des formats comme INT8, NF4 et FP4. La compétence s'intègre à HuggingFace Transformers et permet l'entraînement QLoRA ainsi que l'utilisation d'optimiseurs en 8 bits.

Voir la compétence