name: npm-registry description: npm-registry should become a local, searchable operational workspace, not only an endpoint wrapper. Use for 2 operation/source entries against https://registry.npmjs.org. metadata: version: "1.0.0"

npm-registry

Generated by Gutenberg. Use this skill to call the npm-registry API through the local npm-registry CLI.

When to use

• The user asks for data exposed by npm-registry (-, express).
• An agent task needs structured JSON from https://registry.npmjs.org.
• You need to perform a write/destructive operation on npm-registry — always preview first, run with --yes only on explicit user confirmation.

How to invoke

The skill assumes the generated CLI is on PATH (or invoke via scripts/use-go.sh run ./cmd/npm-registry from the project directory).

npm-registry operations
npm-registry call getExpress --json
npm-registry sync --json
npm-registry search "<keyword>" --json

Authentication

No authentication required.

Operations index

• getExpress (GET /express) — read — GET /express
• getSearch (GET /-/v1/search) — read — GET /-/v1/search

Output contract

• All commands accept --json and emit machine-readable output.
• call returns { dryRun, operation, request, response }. dryRun: true means the call was not executed (write op without --yes).
• search returns cached records. sync populates the local SQLite cache.

Provenance

• Schema: gutenberg.blueprint.v1
• Generated by: gutenberg 0.3.0
• Source spec: /tmp/npm-registry.openapi.json