← ClaudeAtlas

inspect-node-package-apilisted

Resolve and inspect the public API of an installed Node.js package without executing it. Use when Codex needs to understand a dependency in node_modules, verify an import or subpath, find exported functions, classes, types, or signatures, trace TypeScript declaration re-exports, compare ESM/CommonJS/type entry points, or determine the installed package version and interface before writing integration code.
dills122/ai-central · ★ 0 · Testing & QA · score 70
Install: claude install-skill dills122/ai-central
# Inspect Node Package API Treat the installed package and its declarations as the primary evidence for the version the project actually uses. Produce a compact, usage-ready API map with source paths and clearly label anything inferred from runtime syntax. ## Start With The Inspector Run the bundled script from the target project: ```sh node path/to/skill/scripts/inspect-package-api.mjs PACKAGE_OR_SUBPATH --project PROJECT_DIR ``` Useful forms: ```sh node path/to/skill/scripts/inspect-package-api.mjs zod --project . node path/to/skill/scripts/inspect-package-api.mjs @scope/pkg/server --project . node path/to/skill/scripts/inspect-package-api.mjs pkg --project . --symbol Client node path/to/skill/scripts/inspect-package-api.mjs pkg --project . --json ``` Resolve the script path from this skill directory. Do not copy or rewrite the helper into the target repository. The inspector: - resolves npm, pnpm, or Yarn packages exposed through `node_modules` - reports the installed version and package root - interprets root, conditional, explicit subpath, and wildcard `exports` - distinguishes type, import, require, node, and default targets - finds declaration entry files and follows relative declaration re-exports - extracts exported symbol names as navigation hints - reports static ESM/CommonJS export hints when declarations are unavailable - never imports or evaluates package code Use `--help` for the complete command interface. ## Trace The Requested Surface 1. Inspect