Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

prpm-json-best-practices

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

AgentWorkforce · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add AgentWorkforce/relay --skill prpm-json-best-practices

About this skill


name: prpm-json-best-practices description: 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

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

Multi-Package Repository

See examples/multi-package.json for complete structure.

Use when: Publishing multiple related packages from one repo Key difference: Top-level packages array with individual package definitions

Collections Repository

See examples/collections-repository.json for complete structure.

Use when: Bundling existing published packages into curated collections Key points:

  • collections array references packages by packageId (not files)
  • Each collection has id, name, description, packages
  • Packages can be required: true (default) or false (optional)
  • Use version ranges (^1.0.0) or latest
  • Add reason to explain why package is included

Packages + Collections (Combined)

See examples/packages-with-collections.json for complete structure.

Use when: Publishing packages AND creating collections that bundle them Key points:

  • Define packages in packages array with files
  • Define collections in collections array referencing those packages
  • Collections can reference both local packages and external ones
  • Publish both individual packages and collection bundles from same repo

Required Fields

Top-Level (Single Package)

FieldTypeRequiredDescription
namestringYesPackage name (kebab-case, unique in registry)
versionstringYesSemver version (e.g., 1.0.0)
descriptionstringYesClear description of what the package does
authorstringYesAuthor name and optional email
licensestringYesSPDX license identifier (e.g., MIT, Apache-2.0)
formatstringYesTarget format: claude, cursor, continue, windsurf, etc.
subtypestringYesPackage type: agent, skill, rule, slash-command, prompt, collection
filesstring[]YesArray of files to include in package

Optional Top-Level Fields

FieldTypeDescription
repositorystringGit repository URL
organizationstringOrganization name (for scoped packages)
homepagestringPackage homepage URL
documentationstringDocumentation URL
license_textstringFull text of the license file for proper attribution
license_urlstringURL to the license file in the repository
tagsstring[]Searchable tags (kebab-case)
keywordsstring[]Additional keywords for search
categorystringPackage category
privatebooleanIf true, won't be published to public registry
dependenciesobjectPackage dependencies (name: semver)
scriptsobjectLifecycle scripts (multi-package only)
eagerbooleanIf true, skill/agent loads at session start (not on-demand)

Multi-Package Fields

When using packages array:

FieldTypeRequiredDescription
namestringYesUnique package name
versionstringYesPackage version
descriptionstringYesPackage description
Read the complete source ↗