// Publish packages to npm registry. Use this skill when asked to publish, release, or deploy a package to npm. Handles granular access token creation, authentication, and publishing with 2FA bypass.
Manage Late.co social media scheduling API — list, reschedule, bulk delete, and sync scheduled posts. Use this skill when asked to manage scheduled posts, clean up the Late queue, reschedule posts, inspect Late API state, or troubleshoot Late API issues.
Review and inspect video files using Gemini AI vision. Use this skill when asked to inspect, review, analyze, describe, or understand what's happening in a video file. Supports custom prompts for targeted analysis.
Create a new version release for vidpipe. Use this skill when asked to release, version, tag, or create a new version. Handles version bump, changelog generation, GitHub release, and npm publishing.
| name | npm-publish |
| description | Publish packages to npm registry. Use this skill when asked to publish, release, or deploy a package to npm. Handles granular access token creation, authentication, and publishing with 2FA bypass. |
Complete workflow for publishing packages to the npm registry, including granular access token creation via the npmjs.com web UI.
npm run build) and tests passing (npm test)npm view <package-name> version
If the package/version already exists, bump the version in package.json before proceeding.
npm run build && npm test
Ensure there are no build errors and all tests pass before publishing.
If you don't have a valid token:
https://www.npmjs.com/settings/~/tokens using Playwright browser<package-name>-publishnpm_)npm config set //registry.npmjs.org/:_authToken=<TOKEN>
npm publish --access public
npm view <package-name> version
Confirm the published version matches what you expected.
npm config delete //registry.npmjs.org/:_authToken
This removes the token from your local .npmrc so it is not accidentally leaked.
.npmrc after publishing| Problem | Cause | Fix |
|---|---|---|
| E403 error | Token doesn't have bypass 2FA enabled, or expired | Regenerate token with bypass 2FA checked |
| "Must select at least one package" | "All packages" radio not actually selected | Click "All packages" radio button explicitly |
| Email OTP required | npm login requires email verification | User must check their email — cannot be automated |
| E404 on npm view | Package not yet published | This is expected for first-time publishes |
| Version conflict | Version already exists on registry | Bump version in package.json before publishing |