Plugin apply

Skill codecraftersautomation/claude-code/plugins/ccp/skills/plugin-apply

Claude Code plugins, MCP servers & skills by CodeCrafters Automation. Includes Change Claude Profile (ccp): hand off / take over work between Claude Code profiles (claude-team ⇄ claude-max) and keep their plugins in sync.

Install

npx -y skills add codecraftersautomation/claude-code --skill plugin-apply

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Apply a generated plugin sync plan to one profile, only after explicit user confirmation. Use when the user has reviewed /ccp:plugin-sync-plan output and says "apply the plugin plan", "install the missing plugins", or "sync now". Asks which profile (team/max/both), shows the exact commands first, requires confirmation, then runs only the selected generated script. Afterward tells the user to run /reload-plugins and re-verify with /ccp:plugin-inventory.

SKILL.md

2.2 KB, 434 tokens by cl100k_base, as published. Nobody here has run it

CCP: plugin-apply

Execute the reviewed sync plan — carefully, and only with the user's explicit go-ahead. This is the only CCP skill that changes profile state, so it is deliberately gated.

Steps

Confirm the plan exists. Read .claude/ccp/plugins/PLUGIN_SYNC_PLAN.md and the relevant install-missing-*.sh script. If they're missing, run /ccp:plugin-sync-plan first.
Ask the user which target profile to apply to:
- team (claude-team)
- max (claude-max)
- both
For both, apply them as two separate, individually-confirmed steps — never as one silent batch.
Show the exact commands first. Run the apply script in its default dry-run mode so the user sees precisely what would execute (and what is commented out / skipped):
```
bash "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-apply.sh" team        # dry run
bash "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-apply.sh" max         # dry run
```
Require explicit confirmation. Only after the user clearly approves, run with --yes for the chosen profile:
```
bash "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-apply.sh" team --yes
# or
bash "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-apply.sh" max --yes
```
This runs only that profile's generated script. High-risk and unknown-marketplace plugins remain commented out unless the user uncommented them during review.
After applying, tell the user to run:
```
/reload-plugins
```
Then re-run /ccp:plugin-inventory to verify the profiles are now aligned.

Guardrails