parse-package-json

Parse package.json files to extract version, name, and metadata.

243|40|Updated Nov 11, 2025
One-click install
npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill parse-package-json
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parse-package-json
Source: https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/parse-package-json
Command: npx skills add https://github.com/maslennikov-ig/claude-code-orchestrator-kit --skill parse-package-json

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reads and parses package.json files to extract version, name, dependencies, and other metadata for releases and audits.

Core Features & Use Cases

  • Structure validation: Ensures required fields exist (name, version).
  • Field extraction: Returns version, name, description, dependencies, and scripts.
  • Error handling: Reports missing files or invalid JSON with clear messages.

Quick Start

Read ./package.json and return version and name.

Frequently Asked Questions about parse-package-json

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extract version and name from package.json?

Parse package.json to extract version and name by reading the file, validating JSON structure, and returning both fields as structured output. This Skill enforces these as required fields and reports clear errors if missing.

Can I parse package.json to get dependencies and scripts?

Yes. This Skill extracts dependencies, devDependencies, scripts, main, description, and the private flag from package.json in a single operation, enabling audits and release workflows.

What happens if package.json is invalid or missing required fields?

Invalid JSON or missing name/version fields trigger robust error handling that reports specific failure reasons—missing file, invalid JSON syntax, or absent required fields—rather than silent failures.

How do I validate package.json metadata before release?

Use this Skill to read and validate package.json structure, ensuring required fields exist and metadata is well-formed. Results support release workflows, audits, and npm project reports.

Does this work with monorepo or nested package.json files?

This Skill parses individual package.json files you specify. It validates and extracts metadata from each file independently, supporting workflows that process multiple packages.

Why use dedicated JSON parsing instead of manual file reading?

Dedicated parsing enforces validation of required fields, handles malformed JSON gracefully with clear error messages, and structures output consistently for automated audits and reports.