Best practices for structuring prpm.json package manifests with required fields, tags, organization, multi-package management, enhanced file format, eager/lazy activation, and conversion hints
SkillScore100Maintained
Automatic
◆AI Engineer pack
Last verified 8/14/2026
What it changes
Passed 22 of 22 test cases with the skill, and 6 of 22 without it.
Without skill27%
With skill100%
Checks it passed that the model alone missed
Sets format to mcp.
Sets subtype to tool.
Kiro package uses subtype chatmode.
and 24 more in the full report
16 fixed6 passed either way0 still failing0 broke
Pass-rate lift
+73 pp
Tokens
+501%
Agent turns
0%
Response time
-29%
Model gemini-3.6-flashMeasured 8/14/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 16
Prompt
Create a `files` array using the enhanced file object format for a Claude skill where `CRITICAL.md` should load at session start but `OPTIONAL.md` should load lazily.
What was checked, without and with the skill
Checked
Without skill
With skill
File object for CRITICAL.md sets eager to true.
Missed
Passed
File object for OPTIONAL.md sets eager to false.
Missed
Passed
case-19 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md1274 linessingle file
PRPM JSON Best Practices
You are an expert at creating and maintaining prpm.json package manifests for PRPM (Prompt Package Manager). You understand the structure, required fields, organization patterns, and best practices for multi-package repositories.
When to Apply This Skill
Use when:
Creating a new prpm.json manifest for publishing packages
Maintaining existing prpm.json files
Organizing multi-package repositories
Adding or updating package metadata
Ensuring package manifest quality and completeness
Don't use for:
User configuration files (.prpmrc) - those are for users
Lockfiles (prpm.lock) - those are auto-generated by PRPM
Regular package installation (users don't need prpm.json)
Dependencies already tracked in lockfiles
Core Purpose
prpm.json is only needed if you're publishing packages. Regular users installing packages from the registry don't need this file.
Use prpm.json when you're:
Publishing a package to the PRPM registry
Creating a collection of packages
Distributing your own prompts/rules/skills/agents
Managing multiple related packages in a monorepo
File Structure
Single Package
See examples/single-package.json for complete structure.
Key fields:name, version, description, author, license, format, subtype, files