Update to Plugin Creator

{
  "name": "update-plugin",
  "description": "Inspect, edit, or extend custom plugins the user owns or has permission to edit. Use when the user asks to change a plugin's instructions, skills, tools, app UI, Extensions, metadata, assets, or configuration, or asks about a previous version.",
  "included_files": [
    {
      "relative_path": "references/account-updates.md",
      "size_in_bytes": 5100
    },
    {
      "relative_path": "references/legacy-manifest-migration.md",
      "size_in_bytes": 6437
    }
  ],
  "skill_md_contents": "---\nname: update-plugin\ndescription: Inspect, edit, or extend custom plugins the user owns or has permission to edit. Use when the user asks to change a plugin's instructions, skills, tools, app UI, Extensions, metadata, assets, or configuration, or asks about a previous version.\n---\n\n# Update a plugin\n\nStart from the selected plugin and its current source. Preserve its identity,\ndata, hosting, and audience while making the requested change. A question about\nthe plugin or its history does not by itself call for an edit.\n\n## Find the source that owns the change\n\n| Plugin or change | Workflow |\n| --- | --- |\n| A Site's website, MCP tools, or Extensions | Edit the existing Site source and use [Sites MCP](../create-plugin/references/sites-mcp.md). Keep its project, App, and plugin IDs. |\n| A local plugin | Edit the selected directory and follow [local plugins](../create-plugin/references/local-plugins.md) to reload it when requested. |\n| A separately hosted MCP server or app | Change its server/UI repository and use its existing deployment process. Update the plugin package only if its files or connection configuration also change. |\n| A standalone plugin saved through Plugin Creator | Follow [account plugin updates](references/account-updates.md) to retrieve source and publish an eligible update. |\n| A Git-synced or otherwise managed plugin | Change its owning source and use that release process. The archive editor cannot update every installed plugin. |\n\nRead the [Extensions reference](../create-plugin/references/extensions.md) when\nchanging host integration. Use [package format](../create-plugin/references/plugin-packages.md)\nwhen changing manifests, skills, or packaged assets. Inspect existing files\nbefore replacing them; reuse the implementation where it still fits.\n\nFor an account plugin, use its verified backend ID and existing scope, not a\nsimilarly named result or the active account's scope. Prefer the source tools\nfor text edits. Download an archive only for history or content those tools\ncannot return. The account reference covers ownership, partial-file updates,\nand release-conflict handling.\n\n## Apply and verify\n\nHonor requests to save source without deploying. For a shared plugin, make\nthe effect on other users clear before publishing and obtain authorization\nif the conversation has not already provided it. Keep sharing and permissions\nunchanged unless the user requests otherwise through a supported workflow.\n\nTest the behavior affected by the change. For an MCP App, verify its tools and\nUI in the intended ChatGPT or Codex host when available. Return the plugin link\nor source changes, a brief account of what changed, and any unverified behavior.\nUse [prepare-plugin-submission](../prepare-plugin-submission/SKILL.md) for a\nrequested public submission, not for an ordinary private update.\n"
}