Plugin inventory

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

Inventory and compare the plugins available in both Claude Code profiles (claude-team and claude-max). Use when the user wants to know "which plugins are in each account", "compare my profiles' plugins", "what's installed where", or before syncing plugins between profiles. Runs plugin-inventory.sh, captures each launcher's `plugin list`, and writes team-plugins.txt, max-plugins.txt, and PLUGIN_INVENTORY.md under .claude/ccp/plugins/. Installs nothing.From its SKILL.md

Install

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

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.

SKILL.md

2.0 KB, 371 tokens by cl100k_base, as published. Nobody here has run it

CCP: plugin-inventory

See, at a glance, what plugins each profile has — so you can decide what to align. This is purely a read step; it installs and changes nothing.

Steps

Run the inventory script:
```
bash "${CLAUDE_PLUGIN_ROOT}/scripts/plugin-inventory.sh"
```
It invokes claude-team plugin list and claude-max plugin list, captures each separately, and redacts the output. If one launcher is missing or errors, the script records that safely and still produces a report for the other.
It writes under .claude/ccp/plugins/:
- team-plugins.txt — raw (redacted) Team capture
- max-plugins.txt — raw (redacted) Max capture
- PLUGIN_INVENTORY.md — comparison: only-Team, only-Max, common, plus any enabled/disabled and scope info that the raw output happened to include
Summarize the diff for the user: which plugins are only in one profile, which are shared, and the recommended next move (/ccp:plugin-export → /ccp:plugin-sync-plan → review → /ccp:plugin-apply).

Notes on parsing

plugin list output varies by Claude Code version, so the comparison is best-effort. Treat team-plugins.txt and max-plugins.txt as authoritative; the markdown diff is a convenience. If a launcher isn't found, point the user at /ccp:profile-doctor.

What this skill must never do

Never install, enable, or disable any plugin.
Never copy plugin cache between profiles.
Never touch credentials/OAuth/Keychain data.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most operations skills give in 371 tokens

Counted across 483 of the 484 authors here whose files we hold, read 2026-08-07

Collect monitoring data throughout the simulationin 14 of 483, across 6 files
Set the random seed for reproducibilityin 14 of 483, across 6 files
Validate simulations against analytical solutionsin 12 of 483, across 4 files
Clarify goals, constraints, and inputsin 11 of 483, across 2 files
Implement contract tests for integration pointsin 11 of 483, across 2 files
Implement strangler fig infrastructure with API gatewayin 11 of 483, across 2 files
Audit modernized components for security vulnerabilitiesin 11 of 483, across 2 files
Avoid Python blocking calls in processesin 10 of 483, across 3 files
Use resource context managers for automatic cleanupin 9 of 483, across 2 files
Maintain consistent time unitsin 9 of 483, across 2 files
Validate outcomes against success criteriain 8 of 483, across 1 file
Analyze the legacy codebase for technical debtin 8 of 483, across 1 file

Said here and by no other author read

summarize the plugin diff
recommend the next sync move
treat raw txt files as authoritative
point the user at profile-doctor for missing launchers

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.