Update to Media2URL

{
  "description": "Use when someone explicitly asks to publish several files or prepare multiple hosted assets together.",
  "included_files": [],
  "name": "batch-publish",
  "skill_md_contents": "---\nname: batch-publish\ndescription: Use when someone explicitly asks to publish several files or prepare multiple hosted assets together.\n---\n\n# Batch Publish\n\n## Purpose\n\nPublish several authorized assets while keeping deterministic input ordering and an honest per-item result map. Batch publication is a workflow, not permission to bypass limits or validation.\n\n## Trigger examples\n\n- “Host these ten screenshots.”\n- “Give me URLs for all these images.”\n- “Create a Markdown gallery from these files.”\n- “Publish this folder of assets in filename order.”\n\n## Do not trigger\n\n- The user mentions several files but does not ask to host, publish, or link them.\n- The App cannot receive the binary bytes or identify authorized library assets.\n- The user asks for a bulk action that would silently replace or delete existing assets.\n\n## Allowed Media2URL App actions\n\n- Use repeated `publish_content` calls or the App’s approved multi-file upload flow.\n- Use `get_asset_links` for confirmed output URLs.\n- Use `search_assets` only when the user explicitly refers to existing library assets.\n\n## Result interpretation\n\nPreserve input order and map each result to its original filename or logical identifier. Return direct URLs for code and embed output, share pages for human sharing, and structured Markdown/HTML/CSS/JSON only from confirmed results.\n\n## Missing authorization\n\nRequire a Media2URL account connection before the first storage action. Do not offer anonymous ChatGPT uploads, presigned destinations, or a batch result before the App confirms each publication.\n\n## Plan or quota restriction\n\nFree accounts are capped at 90 uploads per month, roughly 3 per day. Explain `BATCH_REQUIRES_PLAN`, `FREE_QUOTA_EXHAUSTED`, `FILE_SIZE_REQUIRES_PLAN`, or the App’s actual entitlement error. A paid plan unlocks larger quotas and batch controls. Do not silently publish only some items or downgrade a batch into unrelated individual behavior without telling the user.\n\n## Partial failure\n\nReport successful and failed items separately, preserving input order and source names. A failed item must not receive another item’s URL, and the batch must not be described as fully successful. Do not retry indefinitely.\n\n## Privacy and destructive actions\n\nEvery item must pass the App’s workspace, file, abuse, and plan checks. Batch publication does not authorize private-asset exposure, third-party importing, replacement, rollback, or deletion; those are separate actions.\n\n## Natural-language examples\n\n“Three files were published and two were rejected by Media2URL. I’ll return the three confirmed URLs in the original order and list the two failures separately.”\n"
}