Stats
Actions
Tags
Export your Claude Code configuration profile to a portable JSON file
How this command is triggered — by the user, by Claude, or both
Slash command
/claude-config-manager:Skillccm-export/The summary Claude sees in its command listing — used to decide when to auto-load this command
Export a Claude Code configuration profile to a portable JSON file for backup or transfer to another machine. All operations go through the `claude-config` CLI. ## Steps 1. List profiles so the user can pick one: 2. Ask which profile to export. If the user doesn't specify and there's only one profile, pick it. If there are none, create one first via `/ccm-profile`. 3. Export to a file (the CLI writes the JSON directly): If the user prefers a different path, honor it. If they want stdout (e.g. to pipe into `gh gist create`), omit `--output`: 4. Tell the user: `"Exported <profil...
Export a Claude Code configuration profile to a portable JSON file for backup or transfer to another machine. All operations go through the claude-config CLI.
CCM="node ${CLAUDE_PLUGIN_ROOT}/packages/cli/dist/index.js"
$CCM profile list
Ask which profile to export. If the user doesn't specify and there's only one profile, pick it. If there are none, create one first via /ccm-profile.
Export to a file (the CLI writes the JSON directly):
$CCM export "<profile-name>" --output ~/claude-config-export.json
If the user prefers a different path, honor it. If they want stdout (e.g. to pipe into gh gist create), omit --output:
$CCM export "<profile-name>"
"Exported <profile-name> → <path>. Copy this file to another machine and run /ccm-import."npx claudepluginhub wangcansunking/can-claude-plugins --plugin claude-config-manager