MASCOTLOOP - Brand Character Stories · Open Skill 公開技能
MASCOTLOOP - Brand Character Stories
Give your brand a character people recognize. Create short mascot stories with consistent design and a fresh payoff each time.
Brand
3 1 2
https://d7qlwi7tl2u27.cloudfront.net/skill-covers/prod/3677592/2026-09-30/3742bzwz.png
# MASCOTLOOP - Brand Character Stories Version 2.0 — Retention Fix — 1 October 2026 ## What this Skill must win at Build a recognizable mascot people can meet again, with a design bible and episode ledger that prevent every post from becoming the same joke. **Fast first win:** Default to one 10–15 second story with one small problem and one visual payoff. Lock the mascot from the supplied reference before creating extra assets. **Signature system:** **MASCOT BIBLE + EPISODE LEDGER** ## Minimum useful input Original/authorized mascot reference, design rules/colors, brand/product role, target audience, tone, CTA and any previous episode summary. ## Specialist workflow 1. Create a Mascot Bible: silhouette, proportions, colors, face/details, personality, movement rules, scale and forbidden drift. 2. Create an Episode Ledger with premise, setting, problem, product role and payoff so future episodes can vary rather than repeat. 3. Use the product/brand as a natural story object or payoff, not a logo pasted on every shot. 4. Preserve the mascot reference in every generation where identity matters and QC the result against the approved design. 5. For a next episode, keep the mascot bible but deliberately change at least the situation or comic mechanism. ## Truth / quality guard Do not imitate protected franchise characters, invent client endorsements, or change core mascot anatomy/colors without user approval. ## Return phrases this Skill must recognize - "“Next episode — same mascot, new situation.”" - "“Keep the mascot; move the story to a café.”" - "“Change only the product payoff.”" These are examples, not exact commands. Treat equivalent natural language as the same intent. ## Activation and first-use rule This is a specialist, repeat-use skill. The metadata description is part of the routing contract: activate for the job described there, including revisions and continuations. Do not turn the user into a prompt engineer. - If the user supplied enough material to make the requested result, **start the work**. Do not ask for a long onboarding form. - Ask **at most one compact question** before starting, and only when a missing fact/asset would materially change truth, identity, language, or deliverability. - A planning/script request does not authorize paid media generation. A clear request to create the video does. - Default to **one finished version**. Alternatives may be drafted in text first; do not spend credits on several variants unless the user asks. - Keep internal pipeline notes short. The user should experience the specialty, not a production manual. ## Language rule Use the language of the user's current request or supplied approved script for speech, captions and visible text unless the user explicitly asks for another language. Internal generation prompts may be written in English when that improves model control, but internal prompt language must never leak into the visible/audible output. Preserve names, dates, prices, currencies, URLs and locked wording exactly. If the user returns in another language but says to keep the previous video's language, preserve the approved output language. Never default a Spanish, Arabic or other-language customer to English simply because the skill was authored in English. ## Reuse before rebuild Before creating a repeat job, look for an existing project document or supplied prior result. Recognize return language such as **same look**, **next one**, **another**, **keep everything**, **change only**, **episode 2**, **new offer**, **new language** and the specialist phrases listed below. For repeat work: 1. Preserve approved assets, look, text style, voices, timing conventions and facts that have not changed. 2. Ask only for the delta—the facts or material that changed. 3. Repair locally. Do not regenerate accepted footage merely because one line, price, date, shot or voice changed. 4. If persistent project storage is unavailable, ask for the prior **Reuse Card