OpenParable
Skip to content
← Back to skills

NPM Trustme

Apps & Automation
npm-trustme

NPM Trustme is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Automate npm Trusted Publisher setup via the npm-trustme CLI. Use when configuring or verifying npm Trusted Publishers for GitHub Actions with npx npm-trustme, including browser automation and WebAuthn passkey approval.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/development/npm-trustme-regenrek-npm-trustme-2cd13e64/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/npm-trustme, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

npm-trustme

Overview

Automate npm Trusted Publisher setup in the npm web UI. Requires a one-time WebAuthn approval in a real browser session (passkey or security key).

CLI Quick Start

  • One-time if browsers are missing: npx playwright install
  • Ensure (create if missing): npx npm-trustme ensure --yes ...
  • Check only: npx npm-trustme check ...
  • Generate workflow: npx npm-trustme workflow init
  • Doctor: npx npm-trustme doctor

Required Target Inputs

  • Required: --package, --owner, --repo, --workflow
  • Optional: --publishing-access, --environment, --maintainer

Default inference:

  • package: package.json#name
  • owner/repo: git remote origin
  • workflow: .github/workflows/npm-release.yml or the only workflow file

Examples

Check:

npx npm-trustme check \
  --package <PACKAGE_NAME> \
  --owner <GITHUB_OWNER> \
  --repo <GITHUB_REPO> \
  --workflow <WORKFLOW_FILE> \
  --publishing-access <PUBLISHING_ACCESS>

Ensure (create if missing):

npx npm-trustme ensure \
  --package <PACKAGE_NAME> \
  --owner <GITHUB_OWNER> \
  --repo <GITHUB_REPO> \
  --workflow <WORKFLOW_FILE> \
  --publishing-access <PUBLISHING_ACCESS> \
  --yes

Dedicated Chrome (keeps main browser open):

npx npm-trustme chrome start
npx npm-trustme ensure --yes

Notes

  • --env-file can load a specific .env path.
  • --storage can persist Playwright storage state for faster re-runs.
  • Inline cookies (Sweet Cookie format) are supported: --inline-cookies-json, --inline-cookies-base64, or --inline-cookies-file.
  • Requires Node >= 22 (Sweet Cookie uses node:sqlite).
  • Chrome profile reuse (manual session): --chrome-profile / --chrome-profile-dir / --chrome-user-data-dir / --chrome-path.
  • Connect to an existing Chrome: --chrome-cdp-url or --chrome-debug-port (Chrome must be launched with remote debugging).
  • Cookie import: --import-cookies (default true) to copy npm cookies from your main Chrome profile.
  • npm-trustme ensure prompts for confirmation; use --yes in automated/agent runs.