Configuration

Settings, telemetry controls, and JSON output options.

The config command

View and modify equip settings with equip config:

$ equip config
  projects_path: ~/dev
  telemetry: on

Setting values

$ equip config projects_path ~/dev

Clearing values

$ equip config projects_path unset

Settings reference

projects_path

When set, equip survey uses this as the default scan path instead of requiring --path each time:

$ equip config projects_path ~/dev

# Now these are equivalent:
$ equip survey
$ equip survey --path ~/dev

Telemetry

equip collects anonymous usage data to power registry install counts. This helps the community discover popular skills.

What is collected

• Random client ID (not tied to your identity)
• Skill name and event type (install, uninstall, update)
• Operating system
• equip version

What is not collected

• No personal information
• No file contents
• No IP addresses
• No usage patterns or session data

Opting out

$ equip config telemetry off

Re-enable with:

$ equip config telemetry on

JSON output

Most commands support --json for machine-readable output. This is useful for scripting and automation.

$ equip list --json
[
  {
    "name": "skill-creator",
    "source": "anthropics/skill-creator",
    "agents": ["claude", "cursor", "windsurf"],
    "up_to_date": true
  }
]

Commands that support --json:

• equip list --json
• equip search --json
• equip update --json
• equip outdated --json
• equip survey --json

Config file location

equip stores its configuration at ~/.config/equip/config.json. You generally don't need to edit this file directly — use equip config instead.