deploy-npm SKILL.md skillA
deploy-npm from kensaurus/cursor-kenji is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kensaurus/cursor-kenji/deploy-npm@git:20260923.cf348bdPins git:20260923.cf348bd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kensaurus/cursor-kenji
- Path
skills/deploy-npm/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260923.cf348bd, committed Sep 23, 2026
- First version recorded
- Jul 18, 2026
- Size
- 14,614 bytes
- Repository stars
- 9
- License
- MIT
Release an npm package: version, CHANGELOG, publish, verify. Use when "publish this package", "release to npm", or "ship a new npm version". Running-app production deploy → workflow-ship-and-observe.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# deploy-npm — Full release workflow **Degree of freedom: MIXED.** Semver/changeset judgment `[HIGH freedom]`; git/gh/npm publish steps `[LOW freedom — run exactly]`. Never `pnpm publish` locally when the repo uses Trusted Publisher. ## How to reason 1. **Observe** — branch, dirty tree, open PRs, pending changesets, release.yml trigger 2. **Interpret** — is this a changeset-ready release or a no-op? 3. **Classify** — proceed / stop-and-ask (dirty tree, conflicting PRs, no changeset) 4. **Severity** — publishing the wrong bump or skipping verify is a user-facing break ## Worked example > **Observe:** feature PR green; one minor changeset; Version PR opened by the bot; required checks never fired. > **Interpret:** GitHub anti-loop suppressed CI on the bot branch. > **Classify:** empty-commit to trigger CI (Phase 4), then merge Version PR. > **Verify:** `npm view` shows the new version; do not publish from the laptop. ## Self-critique before reporting - **Phase order** — no publish before version PR + green CI - **Verify** — `npm view` (and GH Release) ran after publish, not assumed - **No local publish** — Trusted Publisher path only …
Read the whole file at its exact version.
How to install
mdr add kensaurus/cursor-kenji/deploy-npm@sha256:404ceed66598d0f4The line at the top of this page pins the label git:20260923.cf348bd, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_n4oq3lbgxsmaa22z)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 18, 2026 and Sep 23, 2026, about one every 17 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.cf348bd latest | 2026-09-23 | cf348bd | 14,614 B | A | view · diff |
| git:20260821.2a41031 | 2026-08-21 | 2a41031 | 15,568 B | A | view · diff |
| git:20260820.950107c | 2026-08-20 | 950107c | 14,359 B | A | view · diff |
| git:20260817.5b93a21 | 2026-08-17 | 5b93a21 | 14,471 B | A | view · diff |
| git:20260718.724a1d5 | 2026-07-18 | 724a1d5 | 14,640 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14614 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kensaurus/cursor-kenji · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_n4oq3lbgxsmaa22z GET https://markdownregistry.com/api/v1/resolve?ref=kensaurus/cursor-kenji/deploy-npm GET https://markdownregistry.com/api/v1/blob/404ceed66598d0f431b4373056280ef5b02b6415a218daa4d94129af528a40c9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kensaurus/cursor-kenji
Every file in kensaurus/cursor-kenji