Extract version, dependencies, and metadata from package.json files. Use when needing project version, dependency list, or package metadata for releases, audits, or reports.
60
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/parse-package-json/SKILL.mdExtract structured data from package.json files for version management, dependency auditing, and metadata retrieval.
Use Read tool to load package.json file.
Expected Input:
file_path: Path to package.json (default: ./package.json)Tools Used: Read
Parse the JSON content and validate structure.
Validation:
name and version fields at minimumExtract relevant fields into structured output.
Fields to Extract:
version: Semantic version stringname: Package namedescription: 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)Return extracted data as JSON object.
Expected Output:
{
"version": "0.7.0",
"name": "megacampus2",
"description": "Project description",
"dependencies": {
"react": "^18.2.0"
},
"devDependencies": {
"typescript": "^5.0.0"
},
"scripts": {
"build": "tsc",
"test": "jest"
},
"main": "dist/index.js",
"private": true
}Input:
file_path: ./package.jsonOutput:
{
"version": "0.7.0",
"name": "megacampus2"
}Input:
file_path: ./packages/client/package.jsonOutput:
{
"version": "1.2.3",
"name": "@megacampus/client",
"dependencies": {
"react": "^18.2.0",
"react-dom": "^18.2.0"
},
"scripts": {
"dev": "vite",
"build": "vite build"
}
}Input:
file_path: ./nonexistent.jsonOutput:
{
"error": "package.json not found at ./nonexistent.json",
"success": false
}schema.json: JSON schema defining expected package.json structure8c3b576
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.