Structured Data
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Add structured data markup.
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
$ npx skills add pr-pm/prpm --skill prpm-json-best-practices -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pr-pm/prpm prpm-json-best-practices --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/prpm-json-best-practices .claude/skills/prpm-json-best-practices && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "prpm-json-best-practices" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/prpm-json-best-practices into .claude/skills/prpm-json-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prpm-json-best-practices", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/pr-pm/prpm/tree/main/.claude/skills/prpm-json-best-practicesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add pr-pm/prpm --skill prpm-json-best-practices -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pr-pm/prpm prpm-json-best-practices --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/prpm-json-best-practices .agents/skills/prpm-json-best-practices && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prpm-json-best-practices" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/prpm-json-best-practices into .agents/skills/prpm-json-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prpm-json-best-practices", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pr-pm/prpm --skill prpm-json-best-practices -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pr-pm/prpm prpm-json-best-practices --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/prpm-json-best-practices .cursor/skills/prpm-json-best-practices && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prpm-json-best-practices" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/prpm-json-best-practices into .cursor/skills/prpm-json-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prpm-json-best-practices", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/pr-pm/prpm.git --path .claude/skills/prpm-json-best-practices--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add pr-pm/prpm --skill prpm-json-best-practices -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pr-pm/prpm prpm-json-best-practices --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/prpm-json-best-practices .gemini/skills/prpm-json-best-practices && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "prpm-json-best-practices" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/prpm-json-best-practices into .gemini/skills/prpm-json-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prpm-json-best-practices", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install pr-pm/prpm prpm-json-best-practicesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add pr-pm/prpm --skill prpm-json-best-practices -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/prpm-json-best-practices .github/skills/prpm-json-best-practices && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "prpm-json-best-practices" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/prpm-json-best-practices into .github/skills/prpm-json-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prpm-json-best-practices", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add pr-pm/prpm --skill prpm-json-best-practices -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pr-pm/prpm prpm-json-best-practices --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pr-pm/prpm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/prpm-json-best-practices .opencode/skills/prpm-json-best-practices && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prpm-json-best-practices" agent skill from https://github.com/pr-pm/prpm/tree/main/.claude/skills/prpm-json-best-practices into .opencode/skills/prpm-json-best-practices/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prpm-json-best-practices", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
prpm-json-best-practicesBest 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 is an agent skill from pr-pm/prpm. 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
Its SKILL.md is about 8.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `examples/collections-repository.json`, `examples/multi-package.json` and `examples/packages-with-collections.json`).
The repository describes itself as: The universal registry for AI coding tools. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 5f993e6. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
jqnpmFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
docs.prpm.devFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Prpm JSON Best Practices loads about 8.1k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 2,364 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from pr-pm/prpm at commit 5f993e6, republished under its MIT licence (© pr-pm). 2,364 words, ~8,145 tokens.
.claude/skills/prpm-json-best-practices/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.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.
Use when:
prpm.json manifest for publishing packagesprpm.json filesDon't use for:
.prpmrc) - those are for usersprpm.lock) - those are auto-generated by PRPMprpm.json)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:
See examples/single-package.json for complete structure.
Key fields: name, version, description, author, license, format, subtype, files
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
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)id, name, description, packagesrequired: true (default) or false (optional)^1.0.0) or latestreason to explain why package is includedSee examples/packages-with-collections.json for complete structure.
Use when: Publishing packages AND creating collections that bundle them Key points:
packages array with filescollections array referencing those packages| Field | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Package name (kebab-case, unique in registry) |
version | string | Yes | Semver version (e.g., 1.0.0) |
description | string | Yes | Clear description of what the package does |
author | string | Yes | Author name and optional email |
license | string | Yes | SPDX license identifier (e.g., MIT, Apache-2.0) |
format | string | Yes | Target format: claude, cursor, continue, windsurf, etc. |
subtype | string | Yes | Package type: agent, skill, rule, slash-command, prompt, collection |
files | string[] | Yes | Array of files to include in package |
| Field | Type | Description |
|---|---|---|
repository | string | Git repository URL |
organization | string | Organization name (for scoped packages) |
homepage | string | Package homepage URL |
documentation | string | Documentation URL |
license_text | string | Full text of the license file for proper attribution |
license_url | string | URL to the license file in the repository |
tags | string[] | Searchable tags (kebab-case) |
keywords | string[] | Additional keywords for search |
category | string | Package category |
private | boolean | If true, won't be published to public registry |
dependencies | object | Package dependencies (name: semver) |
scripts | object | Lifecycle scripts (multi-package only) |
eager | boolean | If true, skill/agent loads at session start (not on-demand) |
When using packages array:
| Field | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Unique package name |
version | string | Yes | Package version |
description | string | Yes | Package description |
format | string | Yes | Package format |
subtype | string | Yes | Package subtype |
tags | string[] | Recommended | Searchable tags |
files | string[] | Yes | Files to include |
private | boolean | No | Mark as private |
eager | boolean | No | Load at session start (skills/agents only) |
When using collections array:
Top-level (repository with collections):
name, version, description, author, license - Requiredrepository, organization - Recommendedformat, subtype, or files required at top levelEach collection object:
| Field | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Unique collection identifier (kebab-case, 3-100 chars) |
name | string | Yes | Display name (3-100 chars) |
description | string | Yes | What the collection provides (10-500 chars) |
packages | array | Yes | Array of packages to include (minimum 1) |
version | string | Recommended | Semantic version of collection |
category | string | Recommended | Collection category (development, testing, etc.) |
tags | string[] | Recommended | Searchable tags (kebab-case, 1-10 items) |
icon | string | Optional | Emoji or icon (max 10 chars) |
Each package within collection:
| Field | Type | Required | Description |
|---|---|---|---|
packageId | string | Yes | Package to include |
version | string | Optional | Version range (^1.0.0, ~2.1.0, 1.0.0, latest) |
required | boolean | Optional | Whether package is required (default: true) |
reason | string | Optional | Why package is included (max 200 chars) |
| Format | Description |
|---|---|
claude | Claude Code (agents, skills) |
cursor | Cursor IDE (rules, MDC files) |
continue | Continue.dev extension |
windsurf | Windsurf IDE |
copilot | GitHub Copilot |
kiro | Kiro IDE |
agents.md | Agents.md format |
generic | Generic/universal format |
mcp | Model Context Protocol |
| Subtype | Description | Typical Formats |
|---|---|---|
agent | Autonomous agents | claude, agents.md |
skill | Specialized capabilities | claude |
rule | IDE rules and guidelines | cursor, windsurf |
slash-command | Slash commands | cursor, continue |
prompt | Prompt templates | generic |
collection | Package collections | Any |
chatmode | Chat modes | kiro |
tool | MCP tools | mcp |
Skills and agents can be configured to load eagerly (at session start) or lazily (on-demand when relevant).
Use eager: true when:
Keep lazy (default) when:
Package-level:
{
"name": "code-style-enforcer",
"version": "1.0.0",
"format": "claude",
"subtype": "skill",
"eager": true,
"files": [".claude/skills/code-style/SKILL.md"]
}File-level (enhanced files format):
{
"files": [
{
"path": ".claude/skills/critical-skill/SKILL.md",
"format": "claude",
"subtype": "skill",
"eager": true
},
{
"path": ".claude/skills/optional-skill/SKILL.md",
"format": "claude",
"subtype": "skill",
"eager": false
}
]
}When installing, the final eager setting is determined by:
--eager/--lazy) - highest priorityeager setting (enhanced files)eager setting| Subtype | Supports Eager |
|---|---|
skill | Yes |
agent | Yes |
rule | No |
slash-command | No |
hook | No |
Eager loading only affects progressive disclosure formats (agents.md, gemini.md, claude.md, aider).
Technology Tags:
typescript, python, javascript, rustreact, nextjs, fastify, djangoaws, docker, kubernetes, postgresqlDomain Tags:
deployment, testing, ci-cd, databaseinfrastructure, cloud, monitoringdocumentation, code-review, securityPurpose Tags:
troubleshooting, debugging, best-practicesautomation, quality-assurance, performancearchitecture, design-patternsMeta Tags:
meta - For packages about creating packagesprpm-internal - For internal/private packagesprpm-development - For PRPM development itselfGood Tags:
{
"tags": [
"typescript",
"type-safety",
"code-quality",
"best-practices",
"static-analysis"
]
}Poor Tags:
{
"tags": [
"code", // Too generic
"stuff", // Meaningless
"TypeScript", // Wrong case
"type_safety" // Wrong format (use kebab-case)
]
}Order packages by:
Example organization:
{
"packages": [
// Private > Claude > Agents
{ "name": "internal-agent", "private": true, "format": "claude", "subtype": "agent" },
// Private > Claude > Skills
{ "name": "internal-skill", "private": true, "format": "claude", "subtype": "skill" },
// Private > Cursor > Rules
{ "name": "internal-rule", "private": true, "format": "cursor", "subtype": "rule" },
// Public > Claude > Skills
{ "name": "public-skill", "format": "claude", "subtype": "skill" },
// Public > Cursor > Rules
{ "name": "public-rule", "format": "cursor", "subtype": "rule" }
]
}Package Names:
my-awesome-skilltypescript-type-safety not ts-typesformat-conversion-agent (Claude agent)format-conversion (Cursor rule)File Paths:
.claude/agents/name.md.claude/skills/name/SKILL.md.cursor/rules/name.mdc.claude/commands/category/name.mdFollow semantic versioning:
When to bump versions:
For multi-package repos, keep related packages in sync:
{
"packages": [
{ "name": "pkg-one", "version": "1.2.0" },
{ "name": "pkg-two", "version": "1.2.0" },
{ "name": "pkg-three", "version": "1.2.0" }
]
}CRITICAL: File paths must be full paths from project root (where prpm.json lives).
Required:
.claude/, .cursor/, etc.Why Full Paths?
File paths in prpm.json are used for:
Examples:
Claude agent (single file):
{
"format": "claude",
"subtype": "agent",
"files": [".claude/agents/my-agent.md"]
}Claude skill (multiple files):
{
"format": "claude",
"subtype": "skill",
"files": [
".claude/skills/my-skill/SKILL.md",
".claude/skills/my-skill/EXAMPLES.md",
".claude/skills/my-skill/README.md"
]
}Cursor rule:
{
"format": "cursor",
"subtype": "rule",
"files": [".cursor/rules/my-rule.mdc"]
}Slash command:
{
"format": "claude",
"subtype": "slash-command",
"files": [".claude/commands/category/my-command.md"]
}Advanced: Files can be objects with metadata instead of simple strings. Useful for packages with multiple files targeting different formats or needing per-file metadata.
Enhanced file object structure:
{
"files": [
{
"path": ".cursor/rules/typescript.mdc",
"format": "cursor",
"subtype": "rule",
"name": "TypeScript Rules",
"description": "TypeScript coding standards and best practices",
"tags": ["typescript", "frontend"]
},
{
"path": ".cursor/rules/python.mdc",
"format": "cursor",
"subtype": "rule",
"name": "Python Rules",
"description": "Python best practices for backend development",
"tags": ["python", "backend"]
}
]
}When to use enhanced format:
Enhanced file fields:
| Field | Required | Description |
|---|---|---|
path | Yes | Relative path to file from project root |
format | Yes | File's target format (cursor, claude, etc.) |
subtype | No | File's subtype (rule, skill, agent, etc.) |
name | No | Display name for this file |
description | No | Description of what this file does |
tags | No | File-specific tags (array of strings) |
Note: Cannot mix simple strings and objects in the same files array. Use all strings OR all objects, not both.
Common Mistake:
{
// ❌ WRONG - Relative paths without directory prefix
"files": ["agents/my-agent.md"] // Will fail to find file
// ✅ CORRECT - Full path from project root
"files": [".claude/agents/my-agent.md"]
}Always verify files exist:
# Check all files in prpm.json exist
for file in $(cat prpm.json | jq -r '.packages[].files[]'); do
if [ ! -f "$file" ]; then
echo "Missing: $file"
fi
doneRun this check before committing:
# Check for duplicate package names
cat prpm.json | jq -r '.packages[].name' | sort | uniq -dIf output is empty, no duplicates exist. If names appear, you have duplicates to resolve.
Bad:
{
"packages": [
{ "name": "typescript-safety", "format": "claude" },
{ "name": "typescript-safety", "format": "cursor" }
]
}Good:
{
"packages": [
{ "name": "typescript-safety", "format": "claude", "subtype": "skill" },
{ "name": "typescript-safety-rule", "format": "cursor", "subtype": "rule" }
]
}Purpose: Help improve quality when converting packages to other formats. The conversion field provides format-specific hints for cross-format transformations.
Note: This is an advanced feature primarily used by format conversion tools. Most packages don't need this.
Structure:
{
"name": "my-package",
"version": "1.0.0",
"format": "claude",
"conversion": {
"cursor": {
"alwaysApply": false,
"priority": "high",
"globs": ["**/*.ts", "**/*.tsx"]
},
"kiro": {
"inclusion": "fileMatch",
"fileMatchPattern": "**/*.ts",
"domain": "typescript",
"tools": ["fs_read", "fs_write"],
"mcpServers": {
"database": {
"command": "mcp-server-postgres",
"args": [],
"env": {
"DATABASE_URL": "${DATABASE_URL}"
}
}
}
},
"copilot": {
"applyTo": ["src/**", "lib/**"],
"excludeAgent": "code-review"
}
}
}Supported conversion hints:
{
"conversion": {
"cursor": {
"alwaysApply": boolean, // Whether rule should always apply
"priority": "high|medium|low", // Rule priority level
"globs": ["**/*.ts"] // File patterns to auto-attach
}
}
}{
"conversion": {
"claude": {
"model": "sonnet|opus|haiku|inherit", // Preferred model
"tools": ["Read", "Write"], // Allowed tools
"subagentType": "format-conversion" // Subagent type if agent
}
}
}{
"conversion": {
"kiro": {
"inclusion": "always|fileMatch|manual", // When to include
"fileMatchPattern": "**/*.ts", // Pattern for fileMatch mode
"domain": "typescript", // Domain category
"tools": ["fs_read", "fs_write"], // Available tools
"mcpServers": { // MCP server configs
"database": {
"command": "mcp-server-postgres",
"args": [],
"env": { "DATABASE_URL": "${DATABASE_URL}" }
}
}
}
}
}{
"conversion": {
"copilot": {
"applyTo": "src/**", // Path patterns
"excludeAgent": "code-review|coding-agent" // Agent to exclude
}
}
}{
"conversion": {
"continue": {
"alwaysApply": boolean, // Always apply rule
"globs": ["**/*.ts"], // File patterns
"regex": ["import.*from"] // Regex patterns
}
}
}{
"conversion": {
"windsurf": {
"characterLimit": 12000 // Warn if exceeding limit
}
}
}{
"conversion": {
"agentsMd": {
"project": "my-project", // Project name
"scope": "backend" // Scope/domain
}
}
}When to use conversion hints:
{
"name": "internal-tool",
"version": "1.0.0",
"description": "Internal development tool",
"private": true,
"format": "claude",
"subtype": "skill",
"tags": ["prpm-internal", "development"],
"files": [".claude/skills/internal-tool/SKILL.md"]
}{
"name": "creating-skills",
"version": "1.0.0",
"description": "Guide for creating effective Claude Code skills",
"format": "claude",
"subtype": "skill",
"tags": ["meta", "claude-code", "skills", "documentation", "best-practices"],
"files": [".claude/skills/creating-skills/SKILL.md"]
}When you have the same content for multiple formats:
{
"packages": [
{
"name": "format-conversion-agent",
"format": "claude",
"subtype": "agent",
"description": "Agent for converting between AI prompt formats",
"files": [".claude/agents/format-conversion.md"]
},
{
"name": "format-conversion",
"format": "cursor",
"subtype": "rule",
"description": "Rule for converting between AI prompt formats",
"files": [".cursor/rules/format-conversion.mdc"]
}
]
}Collections CAN be defined in prpm.json alongside packages using the collections array. Collections bundle multiple packages together for easier installation.
Example with both packages and collections:
{
"name": "my-prompts-repo",
"author": "Your Name",
"license": "MIT",
"packages": [
{
"name": "typescript-rules",
"version": "1.0.0",
"description": "TypeScript best practices",
"format": "cursor",
"subtype": "rule",
"tags": ["typescript"],
"files": [".cursor/rules/typescript.mdc"]
}
],
"collections": [
{
"id": "my-dev-setup",
"name": "My Development Setup",
"description": "Complete development setup with TypeScript and React",
"version": "1.0.0",
"category": "development",
"tags": ["typescript", "react"],
"packages": [
{
"packageId": "typescript-strict",
"version": "^1.0.0",
"required": true,
"reason": "Enforces strict TypeScript type safety"
},
{
"packageId": "react-best-practices",
"version": "^2.0.0",
"required": true
}
]
}
]
}For more details on creating collections, see the PRPM documentation at https://docs.prpm.dev or run prpm help collections.
Summary: prpm.json can contain both packages (skills, agents, rules, slash-commands, etc.) and collections.
IMPORTANT: The scripts field only applies to multi-package manifests (prpm.json with a packages array). It does NOT work in single-package manifests.
Use the scripts field to run commands automatically during package operations, particularly for building TypeScript hooks before publishing.
Primary use case: Building TypeScript Hooks
If your packages include Claude Code hooks written in TypeScript, you MUST build them to JavaScript before publishing:
{
"name": "my-packages",
"license": "MIT",
"scripts": {
"prepublishOnly": "cd packages/hooks && npm run build"
},
"packages": [
{
"name": "my-hook",
"version": "1.0.0",
"format": "claude",
"subtype": "hook",
"files": [
".claude/hooks/my-hook/hook.ts",
".claude/hooks/my-hook/hook.json",
".claude/hooks/my-hook/dist/hook.js"
]
}
]
}| Script | When it Runs | Use Case |
|---|---|---|
prepublishOnly | Before prpm publish only | Recommended - Build hooks, compile assets |
prepublish | Before publish AND on npm install | Not recommended - causes unexpected builds |
Always use prepublishOnly instead of prepublish to avoid running builds when users install your packages.
Single hook:
{
"scripts": {
"prepublishOnly": "cd .claude/hooks/my-hook && npm run build"
}
}Multiple hooks:
{
"scripts": {
"prepublishOnly": "cd .claude/hooks/hook-one && npm run build && cd ../hook-two && npm run build"
}
}With tests:
{
"scripts": {
"prepublishOnly": "npm test && cd packages/hooks && npm run build"
}
}When you run prpm publish:
scripts.prepublishOnly in your prpm.jsonScript execution details:
DO:
prepublishOnly for building hooks&& for dependencies: npm test && npm run buildDON'T:
prepublish (runs on install too)Hooks in packages/ directory:
{
"scripts": {
"prepublishOnly": "cd packages/hooks && npm run build"
}
}Hooks in .claude/ directory:
{
"scripts": {
"prepublishOnly": "cd .claude/hooks/my-hook && npm run build"
}
}Build multiple components:
{
"scripts": {
"prepublishOnly": "npm run build:hooks && npm run build:assets"
}
}If your prepublishOnly script fails:
Example debugging:
# Test your prepublishOnly script manually
cd /path/to/prpm.json/directory
cd packages/hooks && npm run build
# If it works manually but fails in PRPM, check:
# - Working directory assumptions
# - Environment variables
# - Installed dependenciesWithout prepublishOnly:
With prepublishOnly:
Before publishing, verify:
Required Fields:
name, version, descriptionformat and subtypefiles arrayauthor and licenseFile Verification:
files arrays existNo Duplicates:
Tags:
Organization:
The prpm.lock file is auto-generated and tracks installed packages. It serves as the source of truth for what's installed in your project.
IMPORTANT: Do NOT add packages to prpm.json if they already exist in prpm.lock:
prpm.lock tracks installed dependencies (packages you use)prpm.json defines published packages (packages you create and share)Use prpm.json when:
Use prpm.lock (auto-generated) when:
prpm install❌ WRONG - Don't add installed packages to prpm.json:
// prpm.json
{
"name": "my-project",
"packages": [
{
"name": "typescript-safety", // ❌ This is an INSTALLED package
"version": "1.0.0",
"format": "cursor",
"subtype": "rule",
"files": [".cursor/rules/typescript-safety.mdc"]
}
]
}// prpm.lock (auto-generated)
{
"packages": {
"@prpm/typescript-safety": { // ✅ Already tracked here
"version": "1.0.0",
"format": "cursor",
"subtype": "rule"
}
}
}✅ CORRECT - prpm.json only for YOUR packages:
// prpm.json - Only YOUR packages you're publishing
{
"name": "my-project",
"packages": [
{
"name": "my-custom-rule", // ✅ This is YOUR package
"version": "1.0.0",
"format": "cursor",
"subtype": "rule",
"files": [".cursor/rules/my-custom-rule.mdc"]
}
]
}// prpm.lock - Installed dependencies (auto-generated)
{
"packages": {
"@prpm/typescript-safety": { // ✅ Installed from registry
"version": "1.0.0",
"format": "cursor",
"subtype": "rule"
}
}
}prpm.lockprpm.json = What you PUBLISHprpm.lock = What you INSTALLprpm.json, check if it's already in prpm.lock# Install a package (updates prpm.lock automatically)
prpm install @prpm/typescript-safety
# This creates/updates prpm.lock - DO NOT add to prpm.json!
# Only create prpm.json entries for packages YOU create:
# 1. Create your custom rule/skill/agent
# 2. Add entry to prpm.json
# 3. Publish with: prpm publish# Validate JSON syntax
cat prpm.json | jq . > /dev/null
# Check for duplicates
cat prpm.json | jq -r '.packages[].name' | sort | uniq -d
# Verify files exist
# (see File Verification section)Update version numbers for changed packages.
# Test package installation
prpm install . --dry-run# Publish all packages
prpm publish
# Or publish specific package
prpm publish --package my-skill{
"name": "my-skill",
// Missing: version, description, format, subtype, files
}{
"tags": ["TypeScript", "Code_Quality", "bestPractices"]
// Should be: ["typescript", "code-quality", "best-practices"]
}{
"packages": [
{ "name": "my-skill", "format": "claude" },
{ "name": "my-skill", "format": "cursor" }
// Second should be: "my-skill-rule" or similar
]
}{
"files": [".claude/skills/my-skill/SKILL.md"]
// But .claude/skills/my-skill/SKILL.md doesn't exist in the repo
}{
"files": ["/Users/me/project/.claude/skills/my-skill/SKILL.md"]
// Should be: ".claude/skills/my-skill/SKILL.md" (relative to project root)
}{
"files": ["agents/my-agent.md"]
// Should be: ".claude/agents/my-agent.md" (include .claude/ prefix)
}prpm.json is only for publishing YOUR packages/collections, not for installed dependenciesprpm.lock to prpm.json - they serve different purposesprpm.lock tracks what you INSTALL, prpm.json defines what you PUBLISHcollections array to bundle existing packages (references by packageId)packages array to define packages with filespackages and collections in same repoGoal: Create maintainable, well-organized package manifests and curated collections that are easy to publish and discover in the PRPM registry.
© pr-pm, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files in .claude/skills/prpm-json-best-practices of pr-pm/prpm.
Open the folder on GitHubat commit 5f993e6
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in pr-pm/prpm, which our catalogue first saw on October 7, 2026.
Prpm JSON Best Practices next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prpm JSON Best Practices this skillpr-pm/prpm | 122 | 2 repos | ~8.1k | Automated safety check: Pass | MIT | |
| Structured Datathedaviddias/Front-End-Checklist | 74k | — | ~420 | Automated safety check: Pass | MIT | |
| Requirementsrizsotto/Bear | 6.5k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Bio Structural Biology Modern Structure PredictionFreedomIntelligence/OpenClaw-Medical-Skills | 3.1k | 1 repos | ~2.5k | Automated safety check: Pass | None | |
| List Structurethedaviddias/Front-End-Checklist | 74k | — | ~438 | Automated safety check: Pass | MIT | |
| Bio Structural Biology Structure IoGPTomics/bioSkills | 1.2k | 1 repos | ~4k | Automated safety check: Pass | MIT |
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Add structured data markup.
rizsotto/Bear
Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…
FreedomIntelligence/OpenClaw-Medical-Skills
Predict protein structures using modern ML models including AlphaFold3, ESMFold, Chai-1, and Boltz-1.
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing rendered HTML, interactive components, or design-system patterns related to Use correct list structure.
GPTomics/bioSkills
Reads, writes, downloads, and converts macromolecular structures with Biopython Bio.PDB.
GPTomics/bioSkills
Navigate the Bio.PDB SMCRA hierarchy (Structure-Model-Chain-Residue-Atom) safely, surfacing the heterogeneity it hides by default.
pr-pm/prpm
Reference for writing Claude Code agent files: location, frontmatter fields, validation limits, tool and model choices, and the required content format.
pr-pm/prpm
Covers how to build, configure and publish Claude Code hooks: event types, exit codes, JSON I/O, and PRPM packaging.
pr-pm/prpm
Shows how to write .claude/rules/ files correctly: paths frontmatter instead of globs, quoted glob patterns, global rules and conversion of Cursor rules.
pr-pm/prpm
Reference for writing portable Agent Skills packages, covering SKILL.md frontmatter limits, name rules, directory layout and where Codex CLI, GitHub Copilot and Amp look for skills.
pr-pm/prpm
A skill your agent uses when implementing Stripe webhook endpoints and getting 'Raw body not available' or signature verification errors - provides raw body parsing solutions and subscription period…
pr-pm/prpm
Guides writing an agents.md project-context file: plain markdown with no frontmatter, focused on what an AI coding assistant cannot already know.
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 is an agent skill from pr-pm/prpm.
Run `npx skills add pr-pm/prpm --skill prpm-json-best-practices -a claude-code`. Or copy the skill folder (.claude/skills/prpm-json-best-practices in pr-pm/prpm) into .claude/skills/prpm-json-best-practices in your project. Claude Code loads it when a task matches its description.
Run `npx skills add pr-pm/prpm --skill prpm-json-best-practices -a codex`. Or copy the skill folder (.claude/skills/prpm-json-best-practices in pr-pm/prpm) into .agents/skills/prpm-json-best-practices in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pr-pm/prpm --skill prpm-json-best-practices -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/prpm-json-best-practices, .gemini/skills/prpm-json-best-practices, .github/skills/prpm-json-best-practices and .opencode/skills/prpm-json-best-practices in your project.
Going by SKILL.md and its folder, Prpm JSON Best Practices needs the command-line tools its instructions call (jq and npm). Our summary lists: Docker.
SKILL.md names 1 domain. As links in the text: docs.prpm.dev. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Prpm JSON Best Practices is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 8.1k tokens (SKILL.md is roughly 33k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Prpm JSON Best Practices: Structured Data (thedaviddias/Front-End-Checklist, 74k stars), Requirements (rizsotto/Bear, 6.5k stars), Bio Structural Biology Modern Structure Prediction (FreedomIntelligence/OpenClaw-Medical-Skills, 3.1k stars) and List Structure (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
pr-pm (a GitHub organization) maintains it in pr-pm/prpm, which has 122 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 6, 2026.
Source: pr-pm/prpm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.