baseball-trend
baseball-trend
15-second ESPN-style broadcast cutaway of a user, sitting behind home plate at a fake Yankees vs Red Sox ALCS Game 3 game at Fenway Park, with two announcers naming them on air.
Fixed-recipe skill — the prompts below are calibrated. Substitute the username and keep the marked anchors intact.
Cost transparency gate
Before any paid MCP call, call identity_balance({verbose: true}) once. Surface the current balance, recent burn rate, and remaining runway, then gate the run with this exact message:
Estimated cost: about 3,000-5,500 credits (~$30-$55) for the GPT-image-2 broadcast still, one or two Kling v3-omni pro 15s renders (includes one Step 2 corrective retry with a changed payload), and post-flight analyze_media QA. This exceeds $5, so Reply
proceedto continue orcancelto stop.
Do not call any paid MCP tool until the user replies proceed. If the user replies cancel, stop without generating. This is the only yes/no gate; after proceed, the pipeline runs end-to-end.
Voice selection note
This skill uses Kling-omni's native broadcast commentary: two male announcers, matching MLB broadcast convention. The identity_voice setting is NOT consumed because this fixed recipe does not use agent-side TTS or custom voice IDs.
If the user wants a female-coded announcer or any custom voice, baseball-trend is the wrong skill. Route them to /pika:podcast with a baseball framing, which has an agent-side voice path and can honor explicit voice choices.