Menu
Use when publishing or releasing openrouter-mcp to npm, or preparing a version for distribution with metadata and release checks
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when installing or repairing Claude Desktop or Claude Code MCP config, checking status, backing up config files, or fixing config drift in openrouter-mcp
Use when changing concurrency limits, quota rules, circuit breakers, cleanup behavior, or other high-risk resilience policies in the collective-intelligence paths
Use when handling API key setup, credential rotation or deletion, security-audit runs, shared-environment risk checks, or security-document hygiene in openrouter-mcp
Use when running tests, reproducing the repository's assurance gate locally, checking failures, or verifying coverage for openrouter-mcp
Use when checking code quality, running linting, formatting code, or verifying static analysis gates before PR or publish.
Use when the user asks to continue with additional tasks while keeping current work in progress, or needs parallel branch development, hotfix interruption handling, and review sandboxes without extra clones. Use when tasks involve `git worktree add/list/remove/prune/lock/repair`, resolving branch-in-use conflicts across worktrees, configuring per-worktree settings (`git config --worktree`, `extensions.worktreeConfig`), or writing scripts that must resolve worktree paths safely with `git rev-parse`.
| name | deploy |
| description | Use when publishing or releasing openrouter-mcp to npm, or preparing a version for distribution with metadata and release checks |
Target: npm registry (@physics91/openrouter-mcp). Always manual, intentional.
python3 for Python commands.python3 is unavailable but python exists, use python as fallback..venv.deploy owns release hygiene as well as publish commands. Do not treat metadata checks as optional.Run in order. Stop at first failure:
version in package.json is the intended release (semver).build skill in check mode. ruff, black, and isort must all pass.python3 run_tests.py assurance -v through the test skill.package.json fields:
authorhomepagerepositorybugsrg -n "yourusername|yourproject.com|your-domain-here|Your Name" package.json CHANGELOG.md README.md SECURITY.md docs
CHANGELOG.md version section and comparison links.npm pack --dry-run
README.md and docs/INSTALLATION.md.npm whoami. If not logged in, run npm login.npm publish --access public
git tag v<version>
git push origin v<version>
npm info @physics91/openrouter-mcp version
Defined by files field in package.json:
bin/, src/, requirements.txt, requirements-dev.txt, pytest.ini, docs/, README.md, CONTRIBUTING.md, LICENSE
prepublishOnly script is a no-op; pre-flight checks above are the guard.npm publish.