---
name: update-openrouter-plugin
description: Check the bundled OpenRouter integration against the latest official OpenRouterTeam/skills repository and safely apply compatible upstream skill updates. Use when asked to update, refresh, audit, or synchronize the OpenRouter plugin, or to check whether its official skill snapshot is current.
---

# Update OpenRouter Plugin

Update the official skill snapshot conservatively. The remote MCP is hosted by OpenRouter and updates independently; never replace it with a local proxy.

## Locate and compare

1. Locate the installed plugin source and read `OFFICIAL_SOURCES.md` for the pinned commit and compatibility patches.
2. Fetch `https://github.com/OpenRouterTeam/skills` into a temporary directory and compare only its `skills/` directory with the bundled official skills.
3. Preserve these integration skills exactly: `use-openrouter`, `openrouter-key-management`, `run-openrouter-experiment`, and `update-openrouter-plugin`.
4. Report the old commit, new commit, added skills, removed skills, and changed file classes before applying anything.

## Apply only safe updates automatically

Automatic updates may add or modify only declarative skill content: `SKILL.md`, `README.md`, `references/**`, `metadata.json`, `agents/openai.yaml`, and static assets. They must not delete or rename files or skills, add executables or dependencies, or change the integration skills.

Pause and obtain explicit approval when a diff includes any of the following:

- A deleted or renamed skill or file.
- `scripts/**`, samples, package manifests, lock files, executable files, or generated code.
- Plugin manifest, MCP, authentication, billing, account, API-key, organization, workspace, budget, or other administrative behavior.
- A new compatibility transformation, validation failure, unclear provenance, or any change not covered by the automatic allowlist.

For an approved safe update, replace the affected official files, update the pinned commit in `OFFICIAL_SOURCES.md`, and apply only the documented compatibility transformations:

- Remove unsupported `version` and `compatibility` keys from skill frontmatter.
- Replace angle-bracket placeholders in the `spawn-ori-eval` description with equivalent plain text.

If another transformation is required, stop and ask rather than silently changing upstream behavior.

## Validate and publish

Before publishing or reinstalling:

1. Run `quick_validate.py` on every bundled skill.
2. Run Codex `validate_plugin.py` on the plugin root.
3. Run `claude plugin validate` on the Claude marketplace root and plugin root when Claude Code is available.
4. Confirm every plugin file intended for users is English and `.mcp.json` still points only to `https://mcp.openrouter.ai/mcp`.
5. For a repository release, bump the matching version in both platform manifests, validate both marketplaces, and commit the source. For local Codex iteration, use the plugin-creator cachebuster and reinstall flow instead.
6. Tell Codex users to start a new task. Tell Claude Code users to update the marketplace and run `/reload-plugins`.

Do not create a scheduled updater unless the user explicitly requests a schedule. An update check may be run at any time with a natural-language request such as “Update the OpenRouter plugin safely.”