Plugin export

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

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-export

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

Export the desired plugin set into a repo-local lock file (.claude/ccp/plugins/PLUGINS.lock.json). Use after /ccp:plugin-inventory when the user wants to "record/pin which plugins this repo should use", "create a plugin lock file", or "capture the plugin set to sync to the other profile". Records name, marketplace, version, scope, enabled state, source profile, components, and a risk level per plugin. Contains no secrets and no cache paths. Installs nothing.

SKILL.md

2.5 KB, 496 tokens by cl100k_base, as published. Nobody here has run it

CCP: plugin-export

Turn the inventory into a declarative record of the plugin set this repo should have, so it can be synced to the other profile deliberately rather than by hand.

Steps

Make sure inventory exists. If .claude/ccp/plugins/team-plugins.txt / max-plugins.txt aren't present, run /ccp:plugin-inventory first.
Generate the lock file:
```
bash "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-export.sh"
```
This writes .claude/ccp/plugins/PLUGINS.lock.json. The script parses best-effort and, when a line is ambiguous, preserves the original under a raw field and marks uncertain fields "unknown" rather than guessing.
Review and refine the lock file. For each plugin record, confirm/improve:
- name
- marketplace (leave "unknown" if it genuinely isn't known — do not invent one)
- version (if available)
- scope: user / project / local / managed / unknown
- enabled: true / false / "unknown"
- source_profile: team / max / both
- components: skills, agents, hooks, mcp_servers, lsp_servers (if known)
- risk: low / medium / high
See templates/PLUGINS.lock.template.json for the shape.

Scope guidance

Prefer project scope for repo-specific plugins (they should travel with this repo).
Prefer user scope only for generic personal tools.
Mark managed when an org controls the plugin — CCP can't change those.

Risk flagging

Warn the user about any plugin that ships hooks, MCP servers, LSP servers, or shell-executing behavior, or comes from a local path / unknown source — mark these risk: high. The sync plan will comment those out by default so they're never installed without explicit review.

What this skill must never do

Never include secrets, OAuth tokens, or credentials in the lock file.
Never include plugin cache paths unless clearly useful and safe.
Never guess a marketplace name.
Never install anything.