← FXI StudioCONTENT HISTORY
WHAT CHANGED
Update to FXI Studio
Snapshot Oct 24, 2026 · 13:35 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save FXI Studio and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when choosing an image or video model for a FXI Studio generation, or when the user asks about cost, speed, or quality. Teaches the cost/speed tiers, the fast defaults, and when a pricier model is actually worth it.",
"included_files": [],
"name": "pick-the-right-model",
"skill_md_contents": "---\nname: pick-the-right-model\ndescription: Use when choosing an image or video model for a FXI Studio generation, or when the user asks about cost, speed, or quality. Teaches the cost/speed tiers, the fast defaults, and when a pricier model is actually worth it.\n---\n\n1. Call `list_models` before picking a model you have not already confirmed with\n the user this conversation. Each entry returns `speed_tier` (fast, balanced, or\n quality), `credits`, `typical_seconds` when known, and `best_for`.\n2. Default to the fast, lowest-cost model unless the user names a different model\n or explicitly asks for higher detail:\n - Images default to `z-image-turbo`.\n - Video defaults to `p-video-2`.\n3. Do not upgrade to a pricier model just because the prompt reads as cinematic,\n premium, or photoreal. A fast model handles most drafts.\n4. For dialogue, multi-shot continuity, or complex camera moves, suggest\n `seedance-2-mini` and state its credit cost from `list_models` before switching\n — it costs more but is the right tool for those cases.\n5. When a higher-detail image option exists (for example `nano-banana-2` or\n `nano-banana-pro`), name it and its price from `list_models`, and only switch\n once the user agrees. An explicit model request from the user always runs\n exactly as asked, at its listed price — never silently downgrade it to save\n credits.\n6. Call `get_credits` before a generation if the user's balance might be close to\n the cost. If a call returns `insufficient_credits`, tell the user their actual\n balance and share the `next_step_url` from the result — don't just say the\n generation failed.\n7. State credit costs honestly. Never describe a generation as \"free\" when it\n spends credits, and never use manufactured urgency (\"only a few credits left!\")\n to push a purchase. Refused or failed generations are not charged — say so if\n one errors out, so the user isn't left thinking they lost credits.\n"
}SHA-256 of public snapshot: 655a553576c16a0f0cefbb799f0bc2bb8677c5b705f9b642553066b522977f84