Skip to content
Agentmart
Submit a tool

point-latest-at-rc

Point npm `latest` at the current `@rc` versions using local interactive npm auth (no GitHub `NPM_TOKEN`).

Skill by Yam Borodetsky

IndexedMIT★ 147
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/yamcodes-point-latest-at-rc

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Point npm `latest` at the current `@rc` versions using local interactive npm auth (no GitHub `NPM_TOKEN`). Use when promoting RC to latest after publish, when CI promote_rc_to_latest 403s, when package Publishing access disallows tokens, or when the user asks to retag latest / run point-latest-at-rc without a CI token.

Use cases: devops, security

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/point-latest-at-rc

What's inside

Skill name
point-latest-at-rc
Description
Point npm `latest` at the current `@rc` versions using local interactive npm auth (no GitHub `NPM_TOKEN`). Use when promoting RC to latest after publish, when CI promote_rc_to_latest 403s, when package Publishing access disallows tokens, or when the user asks to retag latest / run point-latest-at-rc without a CI token.
License
MIT
Metadata
author: Yam Borodetsky · version: 1.0.0 · internal: true
Instructions
76 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Point npm `latest` at `@rc` (local / no CI token)

Maintainer **break-glass** alternative to the release workflow’s
`NPM_TOKEN` path. The root script `pnpm point-latest-at-rc` runs
`scripts/point-latest-at-rc.js --from-rc --local` so `npm dist-tag` uses
your logged-in session. Write commands inherit stdin/stdout so npm can
prompt for OTP when 2FA is on auth-and-writes (run from a real TTY).
**Prefer a single OTP for the whole run** via `--otp <code>` or
`NPM_CONFIG_OTP` — otherwise npm prompts once per package (~12 times).
Trusted Publishing still covers **publish**; this skill only covers
**dist-tag**.

Do **not** remove or disable the CI promote job. Prefer CI
`promote_rc_to_latest` when `secrets.NPM_TOKEN` works; use this only when
CI cannot (or as emergency retag).

## Preconditions

1. Repo root on a branch with `.changeset/pre.json` →
   `"mode": "pre"`, `"tag": "rc"` (same gate as CI).
2. Packages already published under `@rc` (e.g. `1.0.0-rc.1`).
3. npm user who can write dist-tags on `@arkenv/*` and `arkenv`
   (`npm login` if needed).

## Steps

```bash
# 1. Confirm auth
npm whoami

# 2. Optional dry-run (lists dist-tag commands; still resolves @rc)
pnpm point-latest-at-rc --dry-run

# 3. Retag (no NPM_TOKEN) — preferred: one OTP for all packages
pnpm point-latest-at-rc -- --otp <code-from-authenticator>
# or: NPM_CONFIG_OTP=<code> pnpm point-latest-at-rc
```

Without `--otp` / `NPM_CONFIG_OTP`, run from a real TTY and expect one
interactive OTP prompt per package.

## Verify

```bash
npm view arkenv dist-tags
npm view @arkenv/core dist-tags
npm view @arkenv/agent-plugin dist-tags
```

Expect `latest` and `rc` both at the same `1.0.0-rc.n`.

## Smoke (after retag)

- Bare `npx arkenv init`
- `@arkenv/core` + arktype in a fresh Node app
- One framework example if time allows

## Failures

| Symptom | Likely cause |
| --- | --- |
| Soft-skip without `--local` | Missing `NPM_TOKEN` — use `pnpm point-latest-at-rc` for this path |
| `Local mode requires npm auth` | Not logged in — `npm login` |
| `EOTP` / no OTP prompt | Not a TTY (piped/non-interactive) — pass `--otp` / `NPM_CONFIG_OTP`, or run from a real terminal |
| OTP prompt per package | Expected without `--otp` / `NPM_CONFIG_OTP` — pass one code for the whole run |
| `E403` on dist-tag | User lacks write on that package |
| Gate skip (`pre.json` / not `rc`) | Not in RC pre mode — do not force |

## Related

- Docs: `docs/RC_CHECKLIST.md` §C (CI primary; local break-glass)
- CI: `.github/workflows/release.yml` → `promote_rc_to_latest` (needs
  `NPM_TOKEN`; leave in place — primary path)
- Script help: `node scripts/point-latest-at-rc.js --help`

From yamcodes/arkenv, MIT.

More from yamcodes/arkenv

Signals

Stars
147
Forks
6
Open issues
6
Last commit (this folder)
Sep 20, 2026 (1 month ago)
Last release
Sep 25, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.0.0
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from Yam Borodetsky

Cite this page

point-latest-at-rc skill. Agent Mart. https://agentmart.dev/skills/yamcodes-point-latest-at-rc (last updated 2026-10-24)