← Viggle AICONTENT HISTORY

Update to Viggle AI

Snapshot Nov 14, 2026 · 06:08 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Viggle AI and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Create a character-motion Mix with Viggle, browse official Viggle motions, or check, recover and download an existing Mix. Use when a user wants a person, creature, avatar, illustration, or other character to reproduce motion from a driving video or an official Viggle motion. Do not use for generic text-to-video tasks without both character and motion intent.",
  "included_files": [
    {
      "relative_path": "references/local-file-upload.md",
      "size_in_bytes": 1135
    }
  ],
  "name": "viggle-mix",
  "skill_md_contents": "---\nname: viggle-mix\ndescription: Create a character-motion Mix with Viggle, browse official Viggle motions, or check, recover and download an existing Mix. Use when a user wants a person, creature, avatar, illustration, or other character to reproduce motion from a driving video or an official Viggle motion. Do not use for generic text-to-video tasks without both character and motion intent.\n---\n\n# Viggle Mix\n\nA Mix is `viggle_prepare_mix` → upload → `viggle_create_mix` →\n`viggle_wait_mix`. The tool descriptions carry the details; this skill covers\nwhat only the host can decide.\n\n## Follow next_action\n\nEvery Viggle result carries `next_action`. Call its `tool`, honour its\n`retry_after_ms`, and relay its `message` to the user as given. The server owns\nevery account, plan, quota, limit and error rule, and its wording changes with\nthe product; do not restate those rules from memory or infer state from prose.\n\n## Account and secrets\n\nLet the host run Viggle OAuth. Never ask for, create, store or print an API\nkey, access token, refresh token, cookie or authorization header: each one is\na credential for the user's account.\n\n## client_context\n\nSend `client_context` with every Viggle tool call so the server can tell an\noutdated plugin:\n\n```json\n{ \"client_context\": { \"host\": \"<actual client id, e.g. claude-code>\", \"plugin_version\": \"1.0.0\" } }\n```\n\nIf a result carries `client_update`, tell the user an update is available. Run\nits `install_command` only in a host that can run a shell, and only after the\nuser agrees: it installs software on their machine.\n\n## Choose the source\n\nTake the first that applies, for the character and for the motion:\n\n1. The host has put a chat attachment into `character_file` / `motion_file`:\n   pass that object as given. Never build a `file_id` yourself.\n2. The host can read a file the user named and make HTTPS PUT requests: follow\n   [references/local-file-upload.md](references/local-file-upload.md).\n3. The user gave a Viggle asset ID, or picked an official Viggle motion: pass\n   it as `viggle_asset_id` or `official_motion_id`.\n4. Otherwise explain that this host cannot send the file, and suggest a host\n   that can attach files or read local ones.\n\nUse only files the user supplied or authorized. Never put a local path, raw\nbytes or base64 in MCP arguments: the server is remote and cannot read them.\n"
}

SHA-256 of public snapshot: bda4931b3a3dd3c68bfbc56a30e7257cecbe425ee9724d7a7b06a7c1c78bd8a8