ワンクリックでManusで任意のスキルを実行

npm-doctor

スター0

フォーク0

更新日2026年4月19日 05:22

Read-only diagnosis of npm ↔ 1Password ↔ GitHub Actions credential drift for a package. Reports what's stale and what to do. Side-effect free.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

capitalthought

capitalthought/npm-helper

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

npm-doctor

Tell the user exactly where their credentials are out of sync. Never writes anything — recommendations only.

Checks

npm whoami — which account is the CLI logged in as? Does it match state?
npm profile get — what's the account 2FA level? (disabled, auth-only, auth-and-writes)
npm token list — which tokens currently exist? Cross-ref against state's token_id.
Package publishing access — npm access get @scope/pkg (or scrape /access page) — is the package set to require granular+bypass or accept automation tokens?
1Password — does the Npmjs item's password field hash match what npm accepts? Test with curl -X PUT .../-/user/org.couchdb.user:<user> (401 = stale).
GitHub Actions secret — secret exists? (can't read value, only list.) Last-updated timestamp recent?
Vercel envs (if configured) — same check.

Output

Print a per-package table:

@capitalthought/highfives-mcp · doctor

  npm account:        capitalthought                     ✅
  account 2FA:        disabled                           ✅ (publishes bypass OTP)
  package policy:     granular+bypass required           ⚠ current NPM_TOKEN is classic automation → E403
  1Password pw:       stale (401 from registry)          ❌ reset at npmjs.com/settings/capitalthought/account
  1Password token:    sha256:abc… (last rotated 2 hr)    ✅
  GH secret NPM_TOKEN: set, updated 2 hr ago              ✅
  Vercel mirror:      not configured                     —

Recommendation: rotate to granular+bypass token (/npm-rotate-token),
reset the npm password (human-in-browser), then re-run /npm-publish.

Rules

Every row has one of four states: ✅ ok · ⚠ drift but publishable · ❌ blocks publish · — not configured.
Never output noise — if everything is green, say "no drift" and stop.
Don't recommend commands that won't help. If password is stale, rotating the token won't unblock token-creation flows.

このリポジトリの他の Skills

同じリポジトリ

npm-register

capitalthought/npm-helper

One-time per-package setup — writes an entry in `~/.config/npm-helper/state.json` mapping a package to its 1Password item, GitHub repo, publish workflow, GH secret, and optional Vercel mirrors. Run this once before `/npm-publish` will work on a new package.

2026-04-190

npm-publish

capitalthought/npm-helper

One-shot npm publish — detects package, syncs credentials, bumps version, tags, pushes, tails the workflow, classifies failures, recovers automatically where possible. Use when the user says "publish this", "ship it", "release npm", or similar.

2026-04-190

npm-rotate-token

capitalthought/npm-helper

Rotate the npm publish token for a package to a fresh granular+bypass-2fa token, update 1Password and the GitHub Actions secret. Use when publishes hit E403/EOTP and /npm-doctor says the token needs replacing.

2026-04-190

npm-set-2fa

capitalthought/npm-helper

Change the npm account 2FA level between disabled, auth-only, and auth-and-writes. Use when /npm-doctor reports account 2FA is blocking automation tokens.

2026-04-190

npm-unstick

capitalthought/npm-helper

Invoked after a failed npm publish to classify the failure, take the right recovery action, and retry once. Called automatically by the PostToolUse hook — the user rarely invokes this directly.

2026-04-190

npm-doctor

Tell the user exactly where their credentials are out of sync. Never writes anything — recommendations only.

Checks

npm whoami — which account is the CLI logged in as? Does it match state?

npm profile get — what's the account 2FA level? (disabled, auth-only, auth-and-writes)

npm token list — which tokens currently exist? Cross-ref against state's token_id.

Package publishing access — npm access get @scope/pkg (or scrape /access page) — is the package set to require granular+bypass or accept automation tokens?

1Password — does the Npmjs item's password field hash match what npm accepts? Test with curl -X PUT .../-/user/org.couchdb.user:<user> (401 = stale).

GitHub Actions secret — secret exists? (can't read value, only list.) Last-updated timestamp recent?

Vercel envs (if configured) — same check.

Output

Print a per-package table:

@capitalthought/highfives-mcp · doctor npm account: capitalthought ✅ account 2FA: disabled ✅ (publishes bypass OTP) package policy: granular+bypass required ⚠ current NPM_TOKEN is classic automation → E403 1Password pw: stale (401 from registry) ❌ reset at npmjs.com/settings/capitalthought/account 1Password token: sha256:abc… (last rotated 2 hr) ✅ GH secret NPM_TOKEN: set, updated 2 hr ago ✅ Vercel mirror: not configured — Recommendation: rotate to granular+bypass token (/npm-rotate-token), reset the npm password (human-in-browser), then re-run /npm-publish.

Rules

Every row has one of four states: ✅ ok · ⚠ drift but publishable · ❌ blocks publish · — not configured.

Never output noise — if everything is green, say "no drift" and stop.

Don't recommend commands that won't help. If password is stale, rotating the token won't unblock token-creation flows.

name	npm-doctor
description	Read-only diagnosis of npm ↔ 1Password ↔ GitHub Actions credential drift for a package. Reports what's stale and what to do. Side-effect free.