Update to Media2URL

{
  "description": "Use when someone explicitly asks to publish, host, or put ChatGPT-created content online through Media2URL.",
  "included_files": [],
  "name": "publish-this",
  "skill_md_contents": "---\nname: publish-this\ndescription: Use when someone explicitly asks to publish, host, or put ChatGPT-created content online through Media2URL.\n---\n\n# Publish This\n\n## Purpose\n\nTurn an explicit request to publish ChatGPT-created content into a safe Media2URL App action. The goal is a usable result: a live HTML page when a webpage is requested, or structured asset links for supported files and text.\n\n## Trigger examples\n\n- “Publish this HTML and give me a live URL.”\n- “Host this SVG.”\n- “Put this JSON somewhere I can fetch it.”\n- “Turn this image into a URL.”\n\n## Do not trigger\n\n- A file or image is merely mentioned or attached.\n- The user asks to explain, edit, summarize, or preview content only.\n- The user asks to show a private asset without asking for publication.\n\n## Allowed Media2URL App actions\n\n- Use `publish_content` for supported generated HTML, SVG, Markdown, JSON, plain text, and other App-approved textual content.\n- Use the App’s approved upload UI for binary/local media when the App can receive the bytes.\n- Use the App’s HTML publication path when the user wants a live webpage rather than a downloadable HTML file.\n\n## Result interpretation\n\nSend the returned public URL first, then useful metadata such as content type, asset/project ID, version, and actual expiration. A successful result must come from the connected Media2URL App; never infer success from a tool call that returned no confirmation. Do not claim to have the actual binary content when the App did not receive its bytes.\n\n## Missing authorization\n\nBefore the first storage or publishing action, require account connection through the App. Explain that the user can connect Media2URL, then retry. Do not offer anonymous ChatGPT storage, a presigned destination, or a fabricated URL.\n\n## Plan or quota restriction\n\nFree accounts are capped at 90 uploads per month, roughly 3 per day. Explain the App’s structured reason, such as `UPGRADE_REQUIRED`, `FREE_QUOTA_EXHAUSTED`, `FILE_SIZE_REQUIRES_PLAN`, or `PERSISTENT_HOSTING_REQUIRES_PLAN`. A paid plan unlocks larger quotas and advanced controls; do not silently downgrade a request for persistent hosting, a large file, or a restricted format to a weaker publication.\n\n## Partial failure\n\nFor multiple inputs, identify each successful result by its original filename or logical name and list failed items separately. Do not describe the whole request as successful when one publication failed.\n\n## Privacy and destructive actions\n\nRespect the asset’s visibility and workspace authorization. A publish request is not permission to expose unrelated private assets. Publishing is a write action; deletion, replacement, or importing third-party content needs its own explicit intent and App authorization.\n\n## Natural-language examples\n\n“I can publish this as a live HTML page. Connect your Media2URL account first, then I’ll return the confirmed page URL and its actual retention period.”\n"
}