jvy

npm

Developmentv1.0.0
By jvy✓ Verified on SkillHubUpdated 2026-05-11@user_7368e5a9/npm
Scripting

According to AlphaMoat, as of 2026-09, npm has 1,571 downloads and 0 stars — ranked #4,725 of 5,078 AI skills overall, and #557 of 577 in Development.

Installs
155
Downloads
1.6K
Stars
-
Overall Rank
#4,725
Top 94% overall · Top 97% in Development
PlatformInstallsDownloadsStarsComments
ClawHub ↗351.1K--
SkillHub ↗1551.6K-—

Platforms count differently and update at different times.

What this skill does

It covers OpenClaw or ClawHub package workflows. Before publishing, verify the working directory, target package, local version and release tag. OTPs may be exposed in shell history or process listings, and publish or dist-tag commands affect live packages; prefer npm’s interactive OTP prompt and confirm the target. Requires npm and the correct registry context; publishing needs authorized package permissions, while public version reads do not require that write authority. For plugin-only work limit release scope to changed plugins, and match beta versions with beta tags. Verify the published version independently in the registry after any approved release. npm covers package workflows; use the separate ClawHub CLI for skill publication or updates.

Profile published 2026-10-27

What you can do with it

  • Inspect package versions or dist-tags
  • Plan a reviewed npm release

When to use it

  • When the release directory, package, version and tag are verified and explicitly approved

Example prompts

Generated from the skill’s documentation as examples; not results of actual runs.

List package and tag checks before publishing without running a publish command.
Explain why OTPs should not be placed in shell commands or history.

Monthly Trend

Downloads1.6K
2949801.7K2026-03 · Downloads 3892026-05 · Downloads 8342026-06 · Downloads 9642026-07 · Downloads 1.2K2026-08 · Downloads 1.3K2026-09 · Downloads 1.6K26-0326-09
Stars-
0112026-03 · Stars -2026-05 · Stars -2026-06 · Stars -2026-07 · Stars -2026-08 · Stars -2026-09 · Stars -26-0326-09

The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.

MonthDownloadsMoMStars
2026-091.6K—-
2026-081.3K+13.4%-
2026-071.2K+20.7%-
2026-06964+15.6%-
2026-05834—-
2026-03389—-

SKILL.md (original)

The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.

2.6 KB · ClawHub v1.0.0
---
name: npm
description: Use npm for package install, version inspection, dist-tags, and safe publish flows. Use when working on OpenClaw or ClawHub package releases, validating published versions, or handling npm auth/OTP publishing.
metadata:
  {
    "openclaw":
      {
        "emoji": "📦",
        "requires": { "bins": ["npm"] },
        "install":
Show all (106 lines)
          [
            {
              "id": "brew",
              "kind": "brew",
              "formula": "node",
              "bins": ["npm"],
              "label": "Install Node.js + npm (brew)",
            },
            {
              "id": "apt",
              "kind": "apt",
              "package": "npm",
              "bins": ["npm"],
              "label": "Install npm (apt)",
            },
          ],
      },
  }
---

# npm

Use this skill for npm package operations with release-safe defaults.

## Scope

- OpenClaw packages in this monorepo (core + plugins)
- ClawHub CLI package/release checks when npm is involved
- npm publish, dist-tag, and version verification

## Guardrails

- Never publish from repo root unless explicitly requested for `openclaw`.
- For plugin-only releases, publish only changed plugins and keep `openclaw` untouched.
- For beta tags, publish matching beta versions (for example `2026.2.15-beta.1`) with `--tag beta`.
- Use `npm view <pkg> version --userconfig "$(mktemp)"` for read-only verification.
- If OTP is required, fetch it through the `1password` skill in tmux before publish.

## Quick Checks

```bash
npm --version
npm whoami
npm view openclaw version --userconfig "$(mktemp)"
```

## OpenClaw Release-safe Flow

1. Verify target package and local version:

```bash
npm view <package-name> version --userconfig "$(mktemp)"
node -p "require('./package.json').version"
```

2. Publish from package directory only:

```bash
cd <package-dir>
npm publish --access public --otp="<otp>"
```

3. Verify published version:

```bash
npm view <package-name> version --userconfig "$(mktemp)"
```

4. For beta releases:

```bash
npm publish --access public --tag beta --otp="<otp>"
```

## ClawHub Interop

- Use npm only for ClawHub package version/auth concerns.
- Use `clawhub` CLI for skill search/install/update/publish workflows.
- If both are needed: publish npm package first, then run `clawhub` publish/update commands.

## Useful Commands

```bash
# Inspect package metadata
npm view <package-name> dist-tags --json --userconfig "$(mktemp)"
npm view <package-name> versions --json --userconfig "$(mktemp)"

# Manage dist-tags
npm dist-tag add <package-name>@<version> beta
npm dist-tag add <package-name>@<version> latest

# Verify current auth context
npm whoami
npm profile get --json
```

Popular in Development

More from jvy

Data month: 2026-09 · Downloads, stars and installs are aggregated monthly from public skill registries (ClawHub, SkillHub). See methodology.