Tiangong Music AI Composer

Problem

Music generation skills often break on operational details: asking users to log in before understanding the request, inventing failure explanations, ending with status logs instead of a playable result page, or leaving audio links that cannot be played in sandboxed frontends. This skill turns the flow into a constrained execution chain: confirm creative requirements, check login state, submit, poll, render results, and keep user-facing errors to fixed, plain-language templates.

How it works

The core rule is to use only the documented HTTP REST endpoints under the fixed base URL https://ai.growingth.com/api. The typical path includes parsing lyrics, style, and intent; reading MIAOYIN_API_TOKEN from config.json in the skill directory; if not logged in, guiding the user first and creating a QR-code session only after an explicit login intent; after submission, polling every 10s and reporting both status and elapsed progress; and after completion, generating an HTML result page opened in an embedded browser. If the sandbox server hosts the page, its Content-Security-Policy response header must allow https://file.growingth.com for media-src, img-src, and connect-src, while clickable rewritten audio links are still provided in the chat.

Boundaries: avoid MCP, WebSocket, web fetching, endpoint guessing, token-format validation, fabricated responses, extra advice, or manual workarounds. Errors such as insufficient balance, copyright protection, and expired login should use fixed templates instead of exposing internal technical terms to the user.