amcs-prompt-composer

Merge style, lyrics, and production notes into a render-ready prompt.

1|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/miethe/MeatyMusic --skill amcs-prompt-composer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: amcs-prompt-composer
Source: https://github.com/miethe/MeatyMusic/tree/main/.claude/skills/workflow/compose
Command: npx skills add https://github.com/miethe/MeatyMusic --skill amcs-prompt-composer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the construction of a render-ready prompt for music rendering engines, ensuring compliance with engine limits, tag formatting, and policy constraints.

Core Features & Use Cases

  • Meta header generation: Build a render-ready header containing Title, Genre/Style, BPM, and Mood.
  • Tag orchestration: Assemble and format influences, genres, instrumentation, and vocal profiles within engine limits.
  • Policy-aware normalization: Normalize living artist influences when required by policy settings.
  • Structure & Lyrics formatting: Produce structured Prompt sections (Intro/Verse/Chorus, etc.) and embed lyrics with section tags.
  • Quick Start Validation: Validate input against engine_limits and produce an issues list for any violations.

Quick Start

Provide validated style, lyrics, producer notes, engine_limits, and seed. Run this skill to produce a composed_prompt and an issues list ready for the next VALIDATE step.

Frequently Asked Questions about amcs-prompt-composer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compose a render-ready prompt for music rendering engines?

Compose a render-ready prompt by merging validated style specifications, lyrics, and production notes into a single prompt that adheres to engine-specific character limits and policy constraints. The Skill automatically assembles meta headers, formats tags, normalizes influences, and embeds lyrics with section tags, then validates against engine limits before output.

What happens when my prompt exceeds engine character limits?

The Skill enforces character limits and logs constraint violations in an issues list. If your composed prompt exceeds engine limits, the issues list identifies which sections violated constraints so you can adjust inputs before passing to the render stage.

How does policy compliance work with living artist influences in prompts?

Policy-aware normalization automatically handles living artist influences according to your policy settings. The Skill applies the required transformations during composition, ensuring your final prompt complies with policy constraints before validation and rendering.

Can I format prompts with custom section tags for different song structures?

Yes. The Skill produces structured prompt sections tagged by song part—Intro, Verse, Chorus, Bridge, Outro—and embeds lyrics with required section tags. Custom tag formatting normalizes across engine expectations and policy requirements during composition.

What input do I need to have ready before composing a prompt?

Provide validated style specifications, lyrics, production notes, engine limits, and a seed value. The Skill processes these as inputs after STYLE, LYRICS, and PRODUCER nodes are complete, then outputs a composed prompt and issues list ready for validation.

How does the Skill resolve conflicts between genre tags, influences, and instrumentation?

Tag orchestration assembles influences, genres, and instrumentation while resolving conflicts to fit within engine limits. The Skill normalizes overlapping tags and prioritizes them according to engine specifications, producing a conflict-free tag set in the final prompt.