| name | deploy |
| description | Use when publishing or releasing openrouter-mcp to npm, or preparing a version for distribution with metadata and release checks |
Deploy Skill
Target: npm registry (@physics91/openrouter-mcp). Always manual, intentional.
Execution Baseline
- Prefer
python3 for Python commands.
- If
python3 is unavailable but python exists, use python as fallback.
- If pip installation is blocked by externally-managed environment (PEP 668), run quality/test gates in local
.venv.
deploy owns release hygiene as well as publish commands. Do not treat metadata checks as optional.
Pre-flight Checklist
Run in order. Stop at first failure:
- Version: Confirm
version in package.json is the intended release (semver).
- Build gate: Run
build skill in check mode. ruff, black, and isort must all pass.
- Assurance gate: Run
python3 run_tests.py assurance -v through the test skill.
- Metadata sanity: Check
package.json fields:
author
homepage
repository
bugs
- Placeholder scan: Run:
rg -n "yourusername|yourproject.com|your-domain-here|Your Name" package.json CHANGELOG.md README.md SECURITY.md docs
Release only when the results are understood and intentional.
- Release notes and links: Verify
CHANGELOG.md version section and comparison links.
- Package contents: Run:
npm pack --dry-run
Confirm the package includes the expected files and excludes junk.
- Install-doc consistency: Spot-check scoped package naming in
README.md and docs/INSTALLATION.md.
- npm auth: Run
npm whoami. If not logged in, run npm login.
- Manual confirmation: Confirm with the user before publish.
Publish
npm publish --access public
Post-publish
- Tag the release in git:
git tag v<version>
git push origin v<version>
- Verify registry version:
npm info @physics91/openrouter-mcp version
- If the package page or docs are part of the release checklist, verify them after publish.
Package Contents
Defined by files field in package.json:
bin/, src/, requirements.txt, requirements-dev.txt, pytest.ini, docs/, README.md, CONTRIBUTING.md, LICENSE
Notes
- No automated publish CI exists. This is always a deliberate manual action.
- The
prepublishOnly script is a no-op; pre-flight checks above are the guard.
- The assurance gate's Node security test runs only after the pytest gate succeeds.
- Always confirm with the user before running
npm publish.
- npm docs recommend proper package metadata and support trusted publishing/provenance; keep the skill ready for that transition even if the current release flow is manual.