Configuration

Configure the SkillReg CLI with .skillregrc files and global settings. Customize registries, default scopes, and team-wide preferences.

Config File

The SkillReg CLI reads its configuration from a .skillregrc file in JSON format. The CLI searches for this file in the following order:

• Current working directory
• Parent directories (walking up to the filesystem root)
• Home directory (~/.skillregrc)

{
  "token": "sr_live_...",
  "org": "acme",
  "apiUrl": "https://app.skillreg.dev",
  "defaultAgent": "claude",
  "defaultScope": "project"
}

All fields are optional. The CLI merges project-level and global configs, with project-level values taking precedence.

Config Command

Use skillreg config to set configuration values non-interactively — useful in scripts or for quick one-off changes.

# Set default org
skillreg config --org acme

# Set agent and scope in one command
skillreg config --default-agent claude --default-scope project

# Point CLI to a custom API endpoint
skillreg config --api-url https://custom.skillreg.dev

Configuration Precedence

When the same setting is defined in multiple places, the CLI uses the value with the highest priority. From highest to lowest:

• 1. Command-line flags — --org, --agent, --scope passed directly to a command.
• 2. Project .skillregrc — Found in the current directory or a parent directory.
• 3. Global ~/.skillregrc — Your machine-wide default configuration.
• 4. Default values — Agent: claude, Scope: project.

File Locations Summary

Here is a quick reference of all file locations used by the SkillReg CLI:

Configuration Files

• Global config — ~/.skillregrc
• Project config — .skillregrc (in project root)
• Env variables — ~/.skillregrc.env/<org>/<skill>.env

Installed Skills by Agent

• Claude — ~/.claude/skills/
• Codex — ~/.codex/skills/
• Cursor — ~/.cursor/extensions/skills/