Update to Media2URL

{
  "description": "Use when someone asks to update, replace, or restore an already published Media2URL asset or HTML page.",
  "included_files": [],
  "name": "update-live-version",
  "skill_md_contents": "---\nname: update-live-version\ndescription: Use when someone asks to update, replace, or restore an already published Media2URL asset or HTML page.\n---\n\n# Update the Live Version\n\n## Purpose\n\nChange an identified managed asset or HTML project while preserving its existing public URL where Media2URL supports that workflow. Treat an update as different from creating a new asset.\n\n## Trigger examples\n\n- “Update the live page with this new copy.”\n- “Replace the screenshot but keep the URL.”\n- “Publish this version instead.”\n- “Restore yesterday’s version.”\n\n## Do not trigger\n\n- The user wants a second, unrelated upload.\n- No immutable asset/project identifier or confirmed library result exists.\n- The user only wants a link copied or content edited in the conversation.\n\n## Allowed Media2URL App actions\n\n- Use `update_published_content` with the exact asset/project ID.\n- Use `replace_asset` for an authorized managed file replacement.\n- Use `rollback_version` only with an exact asset/project ID and version ID returned by the App.\n- Use the App upload UI for local binary replacement when it supports that flow.\n\n## Result interpretation\n\nConfirm the same public URL, the new version identifier, the previous version when returned, and the updated timestamp. If the App reports that the operation creates a new asset or new URL, say so plainly; never represent a new asset as a preserved URL.\n\n## Missing authorization\n\nRequire a connected Media2URL App account before reading private library details or changing hosted content. Ask the App to resolve the current workspace and ownership; do not accept a public URL alone as proof of control.\n\n## Plan or quota restriction\n\nFree accounts are capped at 90 uploads per month, roughly 3 per day. Explain errors such as `VERSIONING_REQUIRES_PLAN`, `FEATURE_REQUIRES_PLAN`, or `UPGRADE_REQUIRED`. A paid plan unlocks larger quotas and versioning controls; do not silently turn a request to preserve the URL into a new free upload.\n\n## Partial failure\n\nIf a replacement or publication fails after staging, report that the existing live version remains unchanged only when the App confirms that state. Never invent a version number, rollback entry, or recovery result.\n\n## Privacy and destructive actions\n\nOnly update assets in the authorized account/workspace. Rollback changes what recipients see and delete is destructive; keep those actions distinct and follow the App’s confirmation and permission requirements.\n\n## Natural-language examples\n\n“I found the managed project. I’ll use its update action so the same URL remains active, then report the new version that Media2URL confirms.”\n"
}