Publishing cursor-kenji

How maintainers ship a new npm version. Consumers only need npx skills add kensaurus/cursor-kenji.

Prerequisites

• Write access to kensaurus/cursor-kenji
• npm package @kensaurus/cursor-kenji with Trusted Publisher configured:
  • Repo: kensaurus/cursor-kenji
  • Workflow: npm-publish.yml
  • Permission: npm publish

No long-lived NPM_TOKEN is required when OIDC is configured.

Pre-release checklist

1. Bump version in package.json and .cursor-plugin/plugin.json (keep in sync)
2. Add a [x.y.z] section to CHANGELOG.md
3. Run the full gate:

npm test

This runs skill spec validation, count sync, README skill-index sync, secret-scanner self-test, MCP pin check, completion-gate tests, and install smoke test.

4. Update derived counts if needed: npm run fix:skills

Ship

# Tag must match package.json version
gh release create v1.4.2 --title "v1.4.2" --notes "$(cat <<'EOF'
## Summary
- …

## Install
npx skills add kensaurus/cursor-kenji
EOF
)"

Creating the release triggers .github/workflows/npm-publish.yml, which:

1. Validates skills + counts + MCP pins
2. Publishes to npm with --provenance via OIDC

Verify

npm view @kensaurus/cursor-kenji version
npm view @kensaurus/cursor-kenji bin

Confirm the GitHub Actions publish run succeeded.

Emergency local publish

Only if CI is broken. Requires a granular npm token with publish access (never commit it):

npm test
npm publish --access public --//registry.npmjs.org/:_authToken="$NPM_TOKEN"

Prefer fixing CI + OIDC over local publishes.

Optional: Cursor Marketplace

Official marketplace submission uses the same repo — .cursor-plugin/plugin.json at the root. Submit at https://cursor.com/marketplace/publish after each meaningful release; Cursor reviews manually.