
Prpm Json Best Practices
Structured manifest guidance for publishing PRPM packages, covering single, multi-package, and collection layouts.
- GitHub stars
- 1.1K
- last updated
- Jun 11, 2026
What it does
- Covers single-package, multi-package, collections-only, and combined repository layouts, each with an example file under
examples/ - Lists required and optional fields for top-level, multi-package, and collection entries, with types and descriptions
- Explains when a
prpm.jsonis needed and when not, such as for.prpmrc,prpm.lock, or plain installs - Designed for authors publishing packages or bundling existing packages into curated collections in a monorepo
Install
$ npx -y skills add agentworkforce/relay --skill prpm-json-best-practices -yInstalls into .agents/skills for every agent it finds here, and .claude/skills for Claude Code.
Files
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.jsonmanifest for publishing packages - Maintaining existing
prpm.jsonfiles - 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
Details
- Repository
- github.com/agentworkforce/relay
- Categories
- Code Review & Quality, Marketing & SEO
- License
- Apache-2.0
- First seen
- Jun 11, 2026
More from agentworkforce/relay
All 17- Relay 80 100 Workflow
- Review Fix Signoff Loop
- Setting Up Relayfile
- Using Agent Relay
- Writing Agent Relay Workflows
- Browser Testing With Screenshots
- Choosing Swarm Patterns
- Creating Agent Skills Skill
- Creating Claude Agents
- Creating Claude Hooks
- Creating Claude Rules
- Creating Skills
- Debugging Websocket Issues
- Deploying To Staging Environment
- Github Oauth Nango Integration
- Implementing Command Palettes
Similar to Prpm Json Best Practices
More Code Review & Quality
Anomaly Detectionaj-geddes/useful-ai-promptsIdentify unusual patterns, outliers, and anomalies in data using statistical methods, isolation forests, and autoencoders for fraud detection and quality monito
Data Cleaning Pipelineaj-geddes/useful-ai-promptsBuild robust processes for data cleaning, missing value imputation, outlier handling, and data transformation for data preprocessing, data quality, and data pip
github-issue-creatoralex-ilgayev/MCPSpyCreates well-structured GitHub issues for the MCPSpy project using the gh CLI tool. Use when asked to create issues, report bugs, or document features. Follows
content-refinement-agentar9av/paperorchestraStep 5 of the PaperOrchestra pipeline (arXiv:2604.05018). Iteratively refine drafts/paper.tex by simulating peer review and applying targeted revisions, with st
paper-orchestraar9av/paperorchestraOrchestrate the full PaperOrchestra (Song et al., 2026, arXiv:2604.05018) five-agent pipeline to turn unstructured research materials (idea, experimental log, L
Mobile App Design Standardsawesome-skills/mobile-app-designThis skill should be used when the user asks to "design mobile UI", "review app design", "check UI guidelines", "improve app UX", "design React Native interface