MCP HubMCP Hub
Volver a habilidades

next-step

bitwize-music-studio
Actualizado 2 days ago
8 vistas
209
37
209
Ver en GitHub
Otrogeneral

Acerca de

La habilidad de siguiente paso analiza los estados de los proyectos de álbumes y recomienda la siguiente acción única óptima cuando los usuarios preguntan "¿qué debería hacer ahora?". Determina la posición en el flujo de trabajo verificando el contexto de la sesión o escaneando todos los álbumes, luego proporciona orientación específica. Esta habilidad actúa como un enrutador de flujos de trabajo, utilizando herramientas como Read, Glob y bitwize-music-mcp para evaluar el progreso y dirigir los siguientes pasos.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skills
Git CloneAlternativo
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/next-step

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

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

Repositorio GitHub

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

Habilidades relacionadas

llamaguard

Otro

LlamaGuard es el modelo de Meta de 7-8B parámetros para moderar las entradas y salidas de LLM en seis categorías de seguridad como violencia y discurso de odio. Ofrece una precisión del 94-95% y puede implementarse usando vLLM, Hugging Face o Amazon SageMaker. Utiliza esta skill para integrar fácilmente filtrado de contenido y barreras de seguridad en tus aplicaciones de IA.

Ver habilidad

cost-optimization

Otro

Esta Skill de Claude ayuda a los desarrolladores a optimizar los costes en la nube mediante el ajuste de tamaño de recursos, estrategias de etiquetado y análisis de gastos. Proporciona un marco para reducir los gastos en la nube e implementar una gobernanza de costes en AWS, Azure y GCP. Úsala cuando necesites analizar los costes de infraestructura, ajustar el tamaño de los recursos o cumplir con restricciones presupuestarias.

Ver habilidad

quantizing-models-bitsandbytes

Otro

Esta habilidad cuantiza LLMs a precisión de 8 o 4 bits utilizando bitsandbytes, logrando una reducción de memoria del 50-75% con pérdida mínima de precisión. Es ideal para ejecutar modelos más grandes en memoria GPU limitada o para acelerar la inferencia, admitiendo formatos como INT8, NF4 y FP4. La habilidad se integra con HuggingFace Transformers y permite entrenamiento QLoRA y optimizadores de 8 bits.

Ver habilidad

dispatching-parallel-agents

Otro

Esta Skill de Claude despliega múltiples agentes para investigar y solucionar 3 o más problemas independientes de forma concurrente. Está diseñada para escenarios que involucran fallos no relacionados que pueden resolverse sin estado compartido o dependencias. Su capacidad principal es la resolución paralela de problemas, asignando un agente por cada dominio problemático independiente para maximizar la eficiencia.

Ver habilidad