Retail New Year Pack

Turn already-written new-year store mood notes into a labeled playlist of original instrumentals. The normal delivery is 8 to 15 beds, not one song.

Scope and adjacent routes

Use this Skill when a retail floor needs a reusable set of original instrumentals for a new-year selling window.

Route a daytime office or coworking playlist to coworking-day-pack. Route a livestream, night shift, or live-commerce playlist to livestream-bgm-pack. Route a brand jingle or sung ad to brand-jingle-studio. Route a song with lyrics to beatra-ai-music-creator.

Collect the floor

Hard inputs are:

• where the music will play (boutique, mall kiosk, supermarket aisle, or another named retail floor);
• how many tracks the pack should contain, or permission to use the default of 10;
• the new-year mood the seller already wrote down.

Reuse already-known hours, talk-over needs, and exclusions. Ask only for a missing hard input. A count outside 8 to 15 is still doable: confirm that pack size and its live cost instead of treating it as impossible.

Do not invent a promo date, a sale price, a brand slogan, or lyrics.

Plan the free track list

Write a labeled new-year track list before any paid music. Default ten slots unless the seller names another count in 8 to 15: doors-open, browse, try-on or pick-up, midday, late afternoon, and close, then fill remaining slots as quiet seasonal resets. Each slot records use, mood, tempo feel, instruments, energy, and intended length written as prompt direction.

That list is the free visible result. Planning is not approval.

Safe defaults:

• instrumental: true with lyrics absent.
• model: "suno-5.5". Never omit the model and never silently use auto.
• There is no duration field on beatra.music.generate. Write length only in the prompt. Do not add a duration argument. Read the actual returned duration.

Confirm generate

Before any billable track, read the current beatra.models.list card for text_to_music. Show one current generate production card for the frozen pack and wait:

1. Work — one new-year instrumental per named slot, a generate call (beatra.music.generate).
2. Credits — the live text_to_music price just read, times the slot count. Do not reuse a remembered number.
3. Count — one paid call per slot. Do not batch tracks into one submit.
4. Identity — one new opaque client_request_id per slot. A changed prompt, title, model, or count mints a new ID for the changed slots.
5. If we stop here — the labeled track list remains usable.
6. If the balance is insufficient — relay the official message and its top-up URL exactly. Translate the prose; keep the URL. Do not retry until the seller says they have topped up.

Submit each slot once through bundled scripts/mcp_client.py. Poll beatra.tasks.get. Deliver actual bytes, actual duration, and billing.net_charged_credits.

Review, deliver, and recover

Review each bed for seasonal fit and talk-over room. Report only what the host can actually hear. Do not promise a seamless loop or exact seconds.

After a returned task_id, poll that task. If the create response is lost, search with beatra.tasks.list and verify with beatra.tasks.get before replay. Reuse an ID only with byte-identical arguments. Cancel only when the seller asks.

Execution

Invoke every remote Beatra operation only through this package's bundled scripts/mcp_client.py. Put the MCP tool name after call and send one JSON object on standard input.

python3 scripts/mcp_client.py call beatra.models.list

{"capability": "text_to_music"}

printf '%s' '{"model":"suno-5.5","prompt":"Warm new-year retail browse bed, light bells and soft strings, no vocals, about 90 seconds.","instrumental":true,"title":"Browse 01","client_request_id":"opaque-ny-browse-01"}' | python3 scripts/mcp_client.py call beatra.music.generate

Do not configure or call a host Beatra Connector, and do not use REST/OpenAPI as a fallback.

Account balance

When the user asks how many credits remain or whether a live estimate fits, call beatra.wallet.get. When they ask what was charged, call beatra.wallet.ledger. Both are read-only. Do not invent an account-balance or top-up tool. Do not make wallet.get a required step before every paid submit.

When a model card comes back carrying a top_up block, relay its tiers as the card lists them and in that order. Do not rank them, do not talk one down, and do not pick one for the user. Which tier suits them is their call, made on the wallet page with the whole list in front of them. Never quote a tier from memory.

References by task

• For slot lists, payloads, and recovery, read New-year playlist workflow.
• For authorization and the non-billable registration step, read installation and authentication and installation registration.
• For shared task, billing, and connection details, read tasks and results, billing, errors, and recovery, and Bundled MCP Client diagnostics.
• For update guarantees and controls, read automatic updates and safety. For removal, read uninstall and disconnect.

Runtime and safe automatic updates

The bundled client silently checks for a newer release at most once every 24 hours per installation. When a newer version is available, it installs automatically without separate confirmation. It downloads only from the fixed official Beatra discovery and immutable CDN paths for this package, channel, and locale, verifies discovery data, archive, manifest, and every packaged file, and replaces only package-owned files.

Update checks, downloads, verification, replacement, rollback, and recovery fail open: the current installation remains usable and the original command continues. An update failure never authorizes retrying a paid music request. The setting persists for this installation. See automatic updates and safety.

python3 scripts/mcp_client.py update --auto off
python3 scripts/mcp_client.py update --auto on
python3 scripts/mcp_client.py update --check