Command Reference - PRPM Documentation

Package Discovery Commands

search

Search for packages in the PRPM registry.

prpm search <query> [options]

Arguments:

query - Search term to find packages

Options:

--format <format> - Filter by format (cursor, claude, windsurf, continue, etc.)
--subtype <subtype> - Filter by subtype (rule, agent, skill, slash-command, etc.)
--limit <number> - Maximum number of results to return (default: 20)
--no-interactive - Disable interactive pagination (useful for automation and scripting)

Note: Interactive mode is enabled by default when there are multiple pages of results. Use --no-interactive when you want to search and install packages programmatically in scripts or CI/CD environments. Examples:

# Basic search (interactive by default)
prpm search typescript

# Filter by format
prpm search react --format cursor

# Filter by subtype
prpm search coding --subtype rule

# Disable interactive mode for automation
prpm search python --no-interactive

# Use in scripts/CI/CD pipelines
prpm search typescript --format cursor --no-interactive | head -n 1

Output: Displays matching packages with their name, description, format, downloads, and installation command.

info

Display detailed information about a specific package.

prpm info <package-name>

Arguments:

package-name - Full package name (e.g., @username/typescript-rules)

Options:

--json - Output in JSON format
--version <version> - Show info for a specific version

Examples:

# View package details
prpm info @username/typescript-best-practices

# View specific version
prpm info @username/typescript-best-practices --version 1.2.0

# JSON output for scripting
prpm info @username/typescript-rules --json

Output: Shows package name, version, description, author, format, subtype, dependencies, installation instructions, and README content.

View trending packages from the registry.

prpm trending [options]

Options:

--format <format> - Filter by format
--subtype <subtype> - Filter by subtype
--limit <number> - Number of packages to display (default: 10)
--period <period> - Time period (day, week, month) (default: week)

Examples:

# View trending packages
prpm trending

# Trending Cursor rules this month
prpm trending --format cursor --period month

# Top 20 trending agents
prpm trending --subtype agent --limit 20

collections

Browse and view curated collections of packages.

prpm collections [options]
prpm collections <collection-name>

Options:

--list - List all available collections
--install - Install all packages in a collection

Examples:

# List all collections
prpm collections --list

# View a specific collection
prpm collections web-development

# Install all packages in a collection
prpm collections web-development --install

Package Management Commands

install

Install one or more packages from the registry.

prpm install <package-name> [additional-packages...] [options]

Arguments:

package-name - Package to install (supports multiple packages)

Options:

--version <version> - Install a specific version
--as <format> - Convert and install in specific format (cursor, claude, continue, windsurf, copilot, kiro, agents.md, canonical)
--format <format> - Alias for --as
--subtype <subtype> - Specify subtype when converting (skill, agent, rule, etc.)
--frozen-lockfile - Fail if lock file needs to be updated (for CI)

Examples:

# Install a package
prpm install @username/typescript-best-practices

# Install multiple packages
prpm install @username/typescript-rules1 @username/typescript-rules2 @username/typescript-rules3

# Install specific version
prpm install @username/typescript-rules --version 2.1.0

# Install and convert to Cursor format
prpm install @username/typescript-rules --as cursor

# Install and convert to Claude format
prpm install @username/typescript-rules --format claude

# Frozen lockfile (for CI)
prpm install @username/typescript-rules --frozen-lockfile

What happens during installation:

Package is downloaded from the registry
Files are extracted to the appropriate directory (.cursor/, .claude/, etc.)
Package is registered in prpm.lock
Format-specific configuration is applied (MDC headers for Cursor, etc.)

uninstall

Remove installed packages from your project.

prpm uninstall <package-id> [additional-packages...] [options]

Arguments:

package-id - ID of the package to uninstall

Options:

--force - Skip confirmation prompts
--keep-files - Remove from lock file but keep the files

Examples:

# Uninstall a package
prpm uninstall @username/typescript-best-practices

# Uninstall multiple packages
prpm uninstall package1 package2 package3

# Uninstall without confirmation
prpm uninstall package-name --force

list

List all installed packages in the current project.

prpm list [options]

Options:

--format <format> - Filter by format
--subtype <subtype> - Filter by subtype
--json - Output in JSON format
--verbose - Show additional details (file paths, versions)

Examples:

# List all packages
prpm list

# List only Cursor packages
prpm list --format cursor

# List all agents
prpm list --subtype agent

# Detailed output
prpm list --verbose

# JSON output
prpm list --json

Output: Shows package ID, format, subtype, version, and file path for each installed package.

outdated

Check for packages that have newer versions available.

prpm outdated [options]

Options:

--json - Output in JSON format

Examples:

# Check for outdated packages
prpm outdated

# JSON output for scripting
prpm outdated --json

Output: Displays packages with their current version, latest available version, and update command.

update

Update specific packages to their latest versions.

prpm update <package-name> [additional-packages...] [options]

Arguments:

package-name - Package(s) to update

Options:

--version <version> - Update to a specific version
--force - Force update even if at latest version

Examples:

# Update a single package
prpm update @username/typescript-rules

# Update multiple packages
prpm update package1 package2 package3

# Update to specific version
prpm update package-name --version 2.5.0

upgrade

Upgrade all installed packages to their latest versions.

prpm upgrade [options]

Options:

--dry-run - Show what would be upgraded without making changes
--interactive - Prompt for confirmation for each package
--skip-breaking - Skip packages with breaking changes (major version bumps)

Examples:

# Upgrade all packages
prpm upgrade

# Preview upgrades
prpm upgrade --dry-run

# Interactive upgrades
prpm upgrade --interactive

Package Creation Commands

init

Initialize a new PRPM package in the current directory.

prpm init [options]

Options:

--yes - Use default values, skip prompts
--private - Create a private package
--force - Overwrite existing prpm.json if present

Interactive Prompts:

Package name
Version
Description
Format (cursor, claude, windsurf, etc.)
Subtype (rule, agent, skill, etc.)
Author name
License
Repository URL
Tags
Files to include

Examples:

# Interactive initialization
prpm init

# Use defaults
prpm init --yes

# Create private package
prpm init --private

# Force overwrite
prpm init --force

What gets created:

prpm.json - Package manifest
README.md - Package documentation template
Format-specific example files based on your selection

catalog

Discover and catalog existing packages from your directories. Scans specified directories for prompt files (Cursor rules, Claude skills, etc.) and creates or updates a prpm.json manifest that you can use to publish them.

prpm catalog [directories...] [options]

Arguments:

directories - Directories to scan (default: current directory)

Options:

-o, --output <path> - Output path for prpm.json (default: ./prpm.json)
-a, --append - Append to existing prpm.json instead of overwriting
--dry-run - Show what would be cataloged without making changes

Examples:

# Catalog packages in current directory
prpm catalog

# Catalog specific directories
prpm catalog .claude .cursor .windsurf

# Append to existing prpm.json
prpm catalog --append

# Preview without making changes
prpm catalog --dry-run

# Output to custom location
prpm catalog -o packages.json

What it does:

Scans directories for prompt files (.md, .mdc, SKILL.md, etc.)
Detects format (cursor, claude, windsurf, etc.) and subtype (rule, skill, agent)
Extracts package metadata from file content
Filters out packages installed from registry (only catalogs user-created content)
Creates/updates prpm.json with discovered packages

Output: Creates a multi-package manifest file that you can review, edit, and publish with prpm publish.

publish

Publish your package to the PRPM registry.

prpm publish [options]

Options:

--dry-run - Test publishing without actually uploading
--tag <tag> - Publish with a specific tag (e.g., beta, next)
--access <public|private> - Set package access level
--force - Skip validation warnings

Prerequisites:

Must be logged in (prpm login)
Must have a valid prpm.json in current directory
Package version must not already exist in registry

Examples:

# Publish package
prpm publish

# Test publish
prpm publish --dry-run

# Publish beta version
prpm publish --tag beta

# Publish private package
prpm publish --access private

What happens during publish:

Package is validated against schema
Files are packaged into a tarball
Package metadata is uploaded to registry
Tarball is uploaded to storage
Package becomes available for installation

Playground Commands

playground

Test packages with real AI models before installing.

prpm playground <package> [input] [options]

Arguments:

package - Package identifier (e.g., @user/package-name)
input - Test input text (optional if using --interactive)

Options:

-m, --model <model> - AI model to use (sonnet, opus, gpt-4o, gpt-4o-mini) (default: sonnet)
-c, --compare - Compare with and without package prompt (baseline test)
-i, --interactive - Start interactive multi-turn conversation mode

Examples:

# Basic test
prpm playground @user/code-reviewer "Review this: console.log('hello')"

# Interactive conversation
prpm playground @user/brainstorm-assistant --interactive

# Compare mode (with and without prompt)
prpm playground @user/optimizer "Optimize this function" --compare

# Use a specific model
prpm playground @user/complex-task "Analyze this" --model opus
prpm playground @user/simple-task "Format this" --model gpt-4o-mini

Supported Models:

sonnet (Claude Sonnet 3.5) - Balanced performance, 2 credits (default)
gpt-4o-mini - Fast and economical, 1 credit
gpt-4o - Advanced reasoning, 3 credits
gpt-4-turbo - Complex tasks, 4 credits
opus (Claude Opus) - Most capable, 7 credits

Credits:

1 credit = 5,000 tokens (input + output combined)
Free tier: 5 trial credits
PRPM+: 100 monthly credits ($6/month)
Credit packs: Buy additional credits that never expire

See the Playground Guide for detailed information.

Manage your PRPM+ subscription.

prpm subscribe [command]

Commands:

(no command) - Subscribe to PRPM+
status - View subscription status and credit balance
cancel - Cancel your PRPM+ subscription

Examples:

# Subscribe to PRPM+
prpm subscribe

# Check subscription status and credits
prpm subscribe status

# Cancel subscription
prpm subscribe cancel

PRPM+ Benefits:

100 monthly playground credits
Credits roll over (max 200 balance)
$6/month (or$ 3/month for organization members)
Priority support

buy-credits

Purchase additional playground credits.

prpm buy-credits

Opens an interactive prompt to select and purchase credit packs. Credit Packs:

100 credits = $5.00
Credits never expire
Stack with monthly PRPM+ credits

Examples:

# Open credit purchase flow
prpm buy-credits

suggested-inputs

Manage suggested test inputs for your packages (authors only).

prpm suggested-inputs <command> <package> [input]

Commands:

add <package> <input> - Add a suggested test input
list <package> - List all suggested inputs for a package
remove <package> <id> - Remove a suggested input

Examples:

# Add suggested input
prpm suggested-inputs add @user/my-package "Review this authentication code"

# List all inputs
prpm suggested-inputs list @user/my-package

# Remove an input
prpm suggested-inputs remove @user/my-package abc123

What it does: Suggested inputs appear automatically in the playground web interface, making it easier for users to test your package with relevant examples.

Local File Management Commands

index

Scan your project directories for existing prompt files and register them in PRPM.

prpm index [options]

Options:

--verbose - Show detailed output for each file

Scanned Directories:

.cursor/rules/ - Cursor rules
.cursor/agents/ - Cursor agents
.cursor/commands/ - Cursor slash commands
.claude/agents/ - Claude agents
.claude/skills/ - Claude skills
.claude/commands/ - Claude slash commands
.continue/rules/ - Continue rules
.windsurf/rules/ - Windsurf rules
.prompts/ - Generic prompts
.mcp/ - MCP servers

Examples:

# Index local files
prpm index

# Verbose output
prpm index --verbose

Output: Shows how many files were found and registered in each directory, and updates prpm.lock.

User Management Commands

Authenticate with the PRPM registry.

prpm login [options]

Options:

--token <token> - Use an existing authentication token
--registry <url> - Specify a custom registry URL

Examples:

# Interactive login
prpm login

# Login with token
prpm login --token your-auth-token

# Login to custom registry
prpm login --registry https://custom-registry.example.com

Authentication Flow:

Opens browser for authentication (or uses provided token)
Saves authentication token to ~/.prpmrc
Token is used for future authenticated requests

whoami

Display information about the currently authenticated user.

prpm whoami [options]

Options:

--json - Output in JSON format

Examples:

# Show current user
prpm whoami

# JSON output
prpm whoami --json

Output: Displays username, email, and authentication status.

Configuration Commands

config

View or modify CLI configuration.

prpm config <action> [key] [value]

Subcommands:

list (or ls) - List all configuration values
get <key> - Get a configuration value
set <key> <value> - Set a configuration value
delete <key> (or rm) - Reset a configuration value to default

Configuration Keys: Readable keys:

registryUrl - Registry URL
telemetryEnabled - Telemetry enabled (true/false)
token - Authentication token (set via prpm login)
username - Username (set via prpm login)

Settable keys:

registryUrl - Change the registry URL
telemetryEnabled - Enable or disable telemetry

Note: token and username are managed via prpm login and cannot be set directly. Examples:

# List all configuration
prpm config list
# or just:
prpm config

# Get a specific value
prpm config get registryUrl
prpm config get telemetryEnabled

# Set registry URL
prpm config set registryUrl https://custom-registry.dev

# Enable telemetry
prpm config set telemetryEnabled true

# Disable telemetry
prpm config set telemetryEnabled false

# Reset a value to default
prpm config delete registryUrl
prpm config delete telemetryEnabled

Telemetry values: When setting telemetryEnabled, you can use:

true, 1, yes - Enable telemetry
false, 0, no - Disable telemetry

telemetry

Manage anonymous usage telemetry.

prpm telemetry <action>

Actions:

enable - Enable telemetry
disable - Disable telemetry
status - Show current telemetry status

Examples:

# Check status
prpm telemetry status

# Enable telemetry
prpm telemetry enable

# Disable telemetry
prpm telemetry disable

What we collect:

Command usage (anonymized)
Error messages (anonymized)
Installation success/failure rates
Package popularity

We do NOT collect:

Personal information
File contents
Project details
Authentication tokens

schema

View or validate package schemas.

prpm schema [options]

Options:

--validate <file> - Validate a package manifest against schema
--format <format> - Show schema for a specific format
--output <file> - Write schema to file

Examples:

# View main package schema
prpm schema

# Validate your package
prpm schema --validate prpm.json

# Get schema for specific format
prpm schema --format cursor

# Save schema to file
prpm schema --output schema.json

Exit Codes

The PRPM CLI uses standard exit codes:

0 - Success
1 - General error
2 - Invalid arguments or usage
3 - Network error
4 - Authentication error
5 - Package not found
6 - Validation error

These can be useful when scripting with PRPM:

#!/bin/bash
if prpm install @username/typescript-rules; then
  echo "Installation successful"
else
  echo "Installation failed with code $?"
fi

Environment Variables

PRPM respects these environment variables:

PRPM_REGISTRY_URL - Override default registry URL
PRPM_TOKEN - Authentication token
PRPM_TELEMETRY - Enable/disable telemetry (true/false)
PRPM_CONFIG_PATH - Custom config file location
NO_COLOR - Disable colored output

Example:

PRPM_REGISTRY_URL=https://custom.registry.dev prpm search typescript

CLI Reference

​Package Discovery Commands

​search

​info

​trending

​popular

​collections

​Package Management Commands

​install

​uninstall

​list

​outdated

​update

​upgrade

​Package Creation Commands

​init

​catalog

​publish

​Playground Commands

​playground

​subscribe

​buy-credits

​suggested-inputs

​Local File Management Commands

​index

​User Management Commands

​login

​whoami

​Configuration Commands

​config

​telemetry

​schema

​Exit Codes

​Environment Variables

Package Discovery Commands

search

info

trending

popular

collections

Package Management Commands

install

uninstall

list

outdated

update

upgrade

Package Creation Commands

init

catalog

publish

Playground Commands

playground

subscribe

buy-credits

suggested-inputs

Local File Management Commands

index

User Management Commands

login

whoami

Configuration Commands

config

telemetry

schema

Exit Codes

Environment Variables