motion-sticker-pack
Create an animated sticker pack from a supplied character image or a text-defined character by collecting a style and Emoji or short reaction descriptions, generating and approving a static sheet, then routing video generation, cleanup, splitting, and packaging. Also process existing static sheets or grid videos. Use for animated emoji or sticker-pack production, not for designing a separate character identity artifact or general video editing.
kobingogo · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add kobingogo/motion-sticker-pack --skill motion-sticker-packAbout this skill
name: motion-sticker-pack description: Create an animated sticker pack from a supplied character image or a text-defined character by collecting a style and Emoji or short reaction descriptions, generating and approving a static sheet, then routing video generation, cleanup, splitting, and packaging. Also process existing static sheets or grid videos. Use for animated emoji or sticker-pack production, not for designing a separate character identity artifact or general video editing.
Motion Sticker Pack|动态表情包制作器
Create a usable animated sticker pack, not merely a video preview. Preserve the supplied character identity and produce independently looping stickers, transparent first frames, a machine-readable report, and a ZIP.
IP identity and prompt principles
- Before writing a generation prompt, inspect the supplied image and derive the IP's visible identity features: face, hair or fur, silhouette and proportions, colors, clothing, accessories, existing props, pose language, scene cues, and overall mood.
- Build the prompt from those observed features plus the user's selected style and reactions. Preserve the supplied IP's appearance and source-specific details by default; change them only when the user asks for a change.
- Unless the user requests another presentation, use the default static-sheet treatment: a 3×3 illustrated reaction-card grid with no white border or heavy outline, subtle local background accents in each cell, and a consistent overall color tone. This changes the visual treatment, not the transparent-alpha and cell-isolation requirements.
- Interpret each Emoji or text reaction semantically. Offer a compact choice for short reaction text: default to avoiding text, while allowing the user to opt in. This is a preference, not a rejection gate—if the model adds text despite the default, keep the sheet eligible for review and let the user decide whether to keep it. When it helps the expression read clearly, add a small number of matching decorative accents—such as hearts, music notes, sparkles, tears, blush marks, sweat drops, motion lines, or stars—using the selected style's visual language. Use them selectively rather than forcing the same accents into every cell, and do not turn them into unrelated large props.
- Do not add unsolicited moral, modesty, sexualization, age, wardrobe, pose-cleanup, or scene-removal instructions. In particular, do not insert wording such as “改成得体、日常、非性感化的简化服装” or “不要保留汽车、夜景、原照片背景或暧昧姿势” unless the user explicitly requests that transformation.
- Keep the source reference label neutral (for example,
所附图像or附件中的角色参考图). Do not encode an unrequested redesign intoreference_label. - A transparent sticker sheet may require removing the source background as a technical canvas operation, but do not otherwise remove existing clothing, props, setting cues, or pose characteristics unless requested. If the user wants the original scene retained, preserve it within each cell where technically feasible.
Pre-generation fidelity check
Before writing a prompt or an intake/confirmation message, explicitly check that no unrequested transformation has been introduced. Remove any wording or instruction that asks to make the character more “得体、日常、非露骨、非性感化”, to simplify or replace clothing, clean up the pose, remove scene cues, or make the result “适合公开分享”. These are not defaults. Preserve the supplied character's observed appearance, clothing, pose language, props, setting cues, and mood unless the user requests a change or a higher-priority platform safety rule requires one. If a safety-driven change is required, state only the necessary constraint and do not broaden it into an aesthetic redesign.
Ambiguous-request confirmation
- When the user supplies a character image but does not specify a style, reactions, or both, do not generate immediately. First present a concise confirmation card with the proposed defaults:
3D 卡通风, the illustrated reaction-card treatment, a practical set of nine chat reactions (开心、喜欢、委屈、惊讶、亲亲、谢谢、加油、困困、点赞), and the default3×3layout. - When no character image is supplied, accept a named or text-defined character and use the same intake defaults when style or reactions are missing. After confirmation, generate the complete static sheet directly. Do not insert a separate single-character concept image, identity card, or character-approval stage.
- State that the prompt will be derived from the image's observed IP features and the selected style, with the character's appearance and source details preserved by default. Do not add redesign or moralizing constraints.
- Accept either an explicit confirmation (
确认/开始生成) or a revision such as风格改为写实还原or表情改为 🎸😍🥹😘🥰. After a revision, show the updated summary and wait for confirmation again. Once confirmed, generate the static sheet directly, then follow the normal layout inspection and static-review gate before any video generation. - If the user already supplied both a clear style and reactions, skip this intake confirmation and proceed to static generation. The post-generation static-review approval before video remains mandatory.
Non-negotiable invariants
- Treat the image model's requested grid as a preference, not observed fact. After image generation, inspect the returned sheet and write
detected_layout; every later stage must use that result. - Compile every static request with
image_generation_request.arguments.backgroundandimage_generation_request.arguments.output_format. Use a transparent-first, locally verified two-stage policy for both reference-image and text-only generation. Pass those exact fields when the callableimage_genschema exposes them; when it does not, omit only the unsupported fields, record them instatic-generation.json, and still make the first attempt with the real-Alpha prompt. Missing schema fields do not prove that prompt-driven transparency is unavailable and must never select the green fallback