parse-package-json — package json parsing parse-package-json, BuhBot, maslennikov-ig, community, package json parsing, ai agent skill, ide skills, agent automation, dependency auditing, version management, metadata extraction, release workflow automation

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing advanced package management and version control capabilities. parse-package-json is a skill that extracts structured data from package.json files for version management, dependency auditing, and metadata retrieval.

Features

Extracts project version for release workflows
Reads package metadata for reports
Validates package.json structure
Loads package.json files using Read tool
Extracts dependency list for auditing
Supports default file path ./package.json

# Core Topics

maslennikov-ig maslennikov-ig
[0]
[0]
Updated: 3/12/2026

Quality Score

Top 5%
60
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
> npx killer-skills add maslennikov-ig/BuhBot/parse-package-json
Supports 19+ Platforms
Cursor
Windsurf
VS Code
Trae
Claude
OpenClaw
+12 more

Agent Capability Analysis

The parse-package-json skill by maslennikov-ig is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance. Optimized for package json parsing, dependency auditing, version management.

Ideal Agent Persona

Perfect for Development Agents needing advanced package management and version control capabilities.

Core Value

Empowers agents to extract and analyze package.json metadata, including version management, dependency auditing, and structure validation, using JSON parsing and file system access.

Capabilities Granted for parse-package-json

Automating release workflows by extracting current project versions
Generating dependency lists for auditing and security checks
Retrieving package metadata for reporting and documentation purposes

! Prerequisites & Limits

  • Requires file system access to read package.json files
  • Limited to parsing JSON files, specifically package.json format
Project
SKILL.md
2.9 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

Parse Package JSON

Extract structured data from package.json files for version management, dependency auditing, and metadata retrieval.

When to Use

  • Get current project version for release workflows
  • Extract dependency list for auditing
  • Read package metadata for reports
  • Validate package.json structure

Instructions

Step 1: Read package.json

Use Read tool to load package.json file.

Expected Input:

  • file_path: Path to package.json (default: ./package.json)

Tools Used: Read

Step 2: Parse JSON

Parse the JSON content and validate structure.

Validation:

  • File must be valid JSON
  • Must contain name and version fields at minimum
  • Dependencies should be objects (if present)

Step 3: Extract Fields

Extract relevant fields into structured output.

Fields to Extract:

  • version: Semantic version string
  • name: Package name
  • description: Package description (optional)
  • dependencies: Production dependencies object (optional)
  • devDependencies: Development dependencies object (optional)
  • scripts: Available npm scripts (optional)
  • main: Entry point file (optional)
  • private: Private flag (optional)

Step 4: Return Structured Data

Return extracted data as JSON object.

Expected Output:

json
1{ 2 "version": "0.7.0", 3 "name": "megacampus2", 4 "description": "Project description", 5 "dependencies": { 6 "react": "^18.2.0" 7 }, 8 "devDependencies": { 9 "typescript": "^5.0.0" 10 }, 11 "scripts": { 12 "build": "tsc", 13 "test": "jest" 14 }, 15 "main": "dist/index.js", 16 "private": true 17}

Error Handling

  • File Not Found: Return error with message "package.json not found at {path}"
  • Invalid JSON: Return error with parsing details
  • Missing Required Fields: Return error listing missing fields (name, version)
  • Invalid Structure: Return error describing structure issue

Examples

Example 1: Extract Version

Input:

file_path: ./package.json

Output:

json
1{ 2 "version": "0.7.0", 3 "name": "megacampus2" 4}

Example 2: Full Package Info

Input:

file_path: ./packages/client/package.json

Output:

json
1{ 2 "version": "1.2.3", 3 "name": "@megacampus/client", 4 "dependencies": { 5 "react": "^18.2.0", 6 "react-dom": "^18.2.0" 7 }, 8 "scripts": { 9 "dev": "vite", 10 "build": "vite build" 11 } 12}

Example 3: Error - File Not Found

Input:

file_path: ./nonexistent.json

Output:

json
1{ 2 "error": "package.json not found at ./nonexistent.json", 3 "success": false 4}

Validation

  • Can read package.json from default path
  • Can read package.json from custom path
  • Extracts all specified fields correctly
  • Handles missing optional fields gracefully
  • Returns error for missing file
  • Returns error for invalid JSON
  • Returns error for missing required fields

Supporting Files

  • schema.json: JSON schema defining expected package.json structure

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is parse-package-json?

Perfect for Development Agents needing advanced package management and version control capabilities. parse-package-json is a skill that extracts structured data from package.json files for version management, dependency auditing, and metadata retrieval.

How do I install parse-package-json?

Run the command: npx killer-skills add maslennikov-ig/BuhBot/parse-package-json. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for parse-package-json?

Key use cases include: Automating release workflows by extracting current project versions, Generating dependency lists for auditing and security checks, Retrieving package metadata for reporting and documentation purposes.

Which IDEs are compatible with parse-package-json?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for parse-package-json?

Requires file system access to read package.json files. Limited to parsing JSON files, specifically package.json format.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add maslennikov-ig/BuhBot/parse-package-json. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use parse-package-json immediately in the current project.

Related Skills

Looking for an alternative to parse-package-json or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
Design

linear

Logo of lobehub
lobehub

Linear issue management. MUST USE when: (1) user mentions LOBE-xxx issue IDs (e.g. LOBE-4540), (2) user says linear, linear issue, link linear, (3) creating PRs that reference Linear issues. Provides

73.4k
0
Communication

testing

Logo of lobehub
lobehub

Testing guide using Vitest. Use when writing tests (.test.ts, .test.tsx), fixing failing tests, improving test coverage, or debugging test issues. Triggers on test creation, test debugging, mock setup

73.3k
0
Communication

zustand

Logo of lobehub
lobehub

Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.

72.8k
0
Communication