How do I install the Ccp skill?

Run npx skillmds@latest add luanquangminh/ccp in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ccp?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

luanquangminh (@luanquangminh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ccp by luanquangminh — Agent Skill

Name: Ccp
Rating: 4.666666666666667 (3 reviews)
Author: luanquangminh

Ccp

Use and manage ccp — the Claude Code Profile Manager. Use when: switching profiles, creating profiles, installing skills from sources, managing hub items, linking/unlinking items, setting up ccp for the first time, activating profiles per-project. Actions: switch, create, install, link, unlink, init, find, list, update profiles and hub items. Keywords: ccp use, ccp init, profile switch, hub link, source add, install skill, settings template, find skills, profile create. Casual triggers: 'switch to my dev profile', 'install a skill', 'set up ccp', 'find skills on github', 'which profile am I using', 'add this skill to my profile', 'how do I use ccp'.

luanquangminh Updated Sep 22, 2026

File contents

ccp — Claude Code Profile Manager

Manage multiple Claude Code configurations via a central hub of reusable components.

Core Concepts

Concept	What
Hub	Central directory of reusable items (~/.ccp/hub/)
Profile	Named config referencing hub items via symlinks
Source	External repo providing installable items
Settings Template	Complete settings.json stored in hub
Activation	How a profile becomes active (global symlink or env var)

Common Workflows

First-Time Setup

ccp init                    # Migrate existing ~/.claude → hub + default profile

Switch Profiles

ccp use dev -g              # Global: ~/.claude → ~/.ccp/profiles/dev
ccp use quickfix            # Project: updates mise.toml or .envrc
ccp which                   # Show active profile

Create a Profile

ccp profile create myprofile              # Empty profile
ccp profile create myprofile --from dev   # Copy from existing
ccp profile create myprofile -i           # Interactive hub picker

Find and Install Skills

ccp find <query>                          # Search skills.sh registry
ccp find -r github <query>               # Search GitHub repos
ccp install owner/repo                    # Add source + interactive install
ccp install owner/repo skills/name        # Install specific skill
ccp install owner/repo -a                 # Install all items

Manage Hub Items

ccp hub list                              # List all hub items
ccp hub add skills/my-skill               # Add item to hub manually
ccp hub remove skills/old-skill           # Remove from hub

Link Items to Profiles

ccp link skills/coding agents/reviewer    # Link hub items to active profile
ccp link -i                               # Interactive picker
ccp unlink skills/coding                  # Remove from profile

Project Setup (for teams)

ccp project add skills/coding             # Copy hub items into .claude/
ccp project install owner/repo -a         # Install from source into .claude/
ccp project list                          # Show project's .claude/ items

Sources

ccp source list                           # List installed sources
ccp source add owner/repo                 # Add a source
ccp source update                         # Update all sources
ccp source remove owner/repo              # Remove a source

Settings Templates

ccp template list                         # List available templates
ccp template show opus-full               # Display template JSON
ccp profile edit dev --template minimal   # Change profile's template

Activation Modes

Mode	Command	How It Works
Global	`ccp use dev -g`	~/.claude symlink → profile dir
Project	`ccp use dev`	Updates mise.toml/envrc with CLAUDE_CONFIG_DIR
Inline	env var	`CLAUDE_CONFIG_DIR=~/.ccp/profiles/dev claude`

Hub Item Types

Skills, agents, commands, rules, hooks, settings-templates — all live in ~/.ccp/hub/<type>/ and get symlinked into profiles.

Tips

Different terminals can use different profiles via env override
ccp install (no args) syncs all sources from ccp.toml — useful for new machines
ccp project add copies (not symlinks) so projects are self-contained and git-committable
Hub items are single-source-of-truth: edit once, all linked profiles update

---name: ccpdescription: Use and manage ccp — the Claude Code Profile Manager. Use when: switching profiles, creating profiles, installing skills from sources, managing hub items, linking/unlinking items, setting up ccp for the first time, activating profiles per-project. Actions: switch, create, install, link, unlink, init, find, list, update profiles and hub items. Keywords: ccp use, ccp init, profile switch, hub link, source add, install skill, settings template, find skills, profile create. Casual triggers: 'switch to my dev profile', 'install a skill', 'set up ccp', 'find skills on github', 'which profile am I using', 'add this skill to my profile', 'how do I use ccp'.---# ccp — Claude Code Profile ManagerManage multiple Claude Code configurations via a central hub of reusable components.## Core Concepts| Concept | What ||---------|------|| **Hub** | Central directory of reusable items (~/.ccp/hub/) || **Profile** | Named config referencing hub items via symlinks || **Source** | External repo providing installable items || **Settings Template** | Complete settings.json stored in hub || **Activation** | How a profile becomes active (global symlink or env var) |## Common Workflows### First-Time Setup```bashccp init # Migrate existing ~/.claude → hub + default profile```### Switch Profiles```bashccp use dev -g # Global: ~/.claude → ~/.ccp/profiles/devccp use quickfix # Project: updates mise.toml or .envrcccp which # Show active profile```### Create a Profile```bashccp profile create myprofile # Empty profileccp profile create myprofile --from dev # Copy from existingccp profile create myprofile -i # Interactive hub picker```### Find and Install Skills```bashccp find <query> # Search skills.sh registryccp find -r github <query> # Search GitHub reposccp install owner/repo # Add source + interactive installccp install owner/repo skills/name # Install specific skillccp install owner/repo -a # Install all items```### Manage Hub Items```bashccp hub list # List all hub itemsccp hub add skills/my-skill # Add item to hub manuallyccp hub remove skills/old-skill # Remove from hub```### Link Items to Profiles```bashccp link skills/coding agents/reviewer # Link hub items to active profileccp link -i # Interactive pickerccp unlink skills/coding # Remove from profile```### Project Setup (for teams)```bashccp project add skills/coding # Copy hub items into .claude/ccp project install owner/repo -a # Install from source into .claude/ccp project list # Show project's .claude/ items```### Sources```bashccp source list # List installed sourcesccp source add owner/repo # Add a sourceccp source update # Update all sourcesccp source remove owner/repo # Remove a source```### Settings Templates```bashccp template list # List available templatesccp template show opus-full # Display template JSONccp profile edit dev --template minimal # Change profile's template```## Activation Modes| Mode | Command | How It Works ||------|---------|--------------|| Global | `ccp use dev -g` | ~/.claude symlink → profile dir || Project | `ccp use dev` | Updates mise.toml/envrc with CLAUDE_CONFIG_DIR || Inline | env var | `CLAUDE_CONFIG_DIR=~/.ccp/profiles/dev claude` |## Hub Item TypesSkills, agents, commands, rules, hooks, settings-templates — all live in `~/.ccp/hub/<type>/` and get symlinked into profiles.## Tips- Different terminals can use different profiles via env override- `ccp install` (no args) syncs all sources from ccp.toml — useful for new machines- `ccp project add` copies (not symlinks) so projects are self-contained and git-committable- Hub items are single-source-of-truth: edit once, all linked profiles update

Frequently asked questions

Ccp