
Ccpi Marketplace
- 141 installs
- 40 repo stars
- Updated August 4, 2026
- akillness/oh-my-skills
Browse and install Claude Code skills or plugins from a CCPI marketplace so you can extend agent capabilities without hand-writing SKILL.md packs from scratch.
About
ccpi-marketplace from akillness/oh-my-skills connects Claude Code to a CCPI skill marketplace for discovering and installing community skills. It shortens agent setup by letting you browse, compare, and add prebuilt capabilities instead of authoring every SKILL.md yourself.
- CCPI skill discovery
- One-step skill install
- Expands agent capability set
- Reduces custom SKILL authoring
- Curated plugin browsing
Ccpi Marketplace by the numbers
- 141 all-time installs (skills.sh)
- Ranked #216 of 782 Skill Development skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/akillness/oh-my-skills --skill ccpi-marketplaceAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 141 |
|---|---|
| repo stars | ★ 40 |
| Last updated | August 4, 2026 |
| Repository | akillness/oh-my-skills ↗ |
What it does
Browse and install Claude Code skills or plugins from a CCPI marketplace so you can extend agent capabilities without hand-writing SKILL.md packs from scratch.
Files
ccpi-marketplace — Tons of Skills CLI & Plugin Marketplace Operations
Use this skill when the task is operating the Tons of Skills ecosystem through CLI commands instead of manual browsing.
When to use
- Install the
ccpiCLI and discover plugin packs by keyword. - Install/update/remove plugin packs in Claude Code environments.
- Verify installed packs and produce reproducible install notes for team handoff.
Install
pnpm add -g @intentsolutionsio/ccpiCore commands
ccpi search <keyword>
ccpi install <pack-name>
ccpi list --installed
ccpi updateClaude built-in marketplace path:
/plugin marketplace add jeremylongshore/claude-code-plugins
/plugin install <pack>@claude-code-plugins-plusSafety rules
1. Prefer ccpi list --installed before adding/updating packs. 2. Record exact pack names (and versions when available) in change notes. 3. Treat marketplace installs as reversible; keep uninstall/remove path in rollback notes. 4. Do not auto-install large bundles without explicit scope (keyword + target capability).
Verification checklist
ccpicommand resolves and reports version/help.- search/install/list/update commands run without auth/runtime errors.
- Installed pack appears in
ccpi list --installedoutput.
References
- https://github.com/jeremylongshore/claude-code-plugins-plus-skills
- https://www.npmjs.com/package/@intentsolutionsio/ccpi
- https://tonsofskills.com
{
"skill_name": "ccpi-marketplace",
"evals": [
{
"id": 1,
"prompt": "install ccpi and add a plugin pack for devops workflows, then show how to verify it is installed",
"expected_output": "Uses pnpm global install for ccpi, runs search/install/list commands, and includes rollback-aware notes.",
"assertions": [
"Mentions or runs `pnpm add -g @intentsolutionsio/ccpi`",
"Uses `ccpi search`, `ccpi install`, and `ccpi list --installed` in sequence",
"Includes rollback guidance for installed packs"
]
}
]
}N:ccpi-marketplace
D:Operate the Tons of Skills marketplace via the ccpi CLI and Claude plugin marketplace commands. Use for searching installing listing and updating Claude Code plugin packs with reversible rollbacks.
G:ccpi claude-code plugin-marketplace skills-marketplace cli package-management tons-of-skills
U[4]:
Install and validate @intentsolutionsio/ccpi
Discover plugin packs with keyword search
Install and update packs with rollback-aware notes
Verify installed packs before and after changes
S[5]{n,action,details}:
1,Assess scope,Confirm target capability and whether CLI or built-in plugin command should be used
2,Install CLI,Install ccpi and verify command availability
3,Discover,Search marketplace and shortlist candidate packs
4,Apply,Install or update selected packs and capture exact identifiers
5,Verify,Run installed-list check and record rollback steps
R[4]:
Keep installs reversible with explicit rollback notes
Avoid broad bundle installs without scope
Prefer deterministic CLI output over ad-hoc screenshots
Keep evidence linked to source repository and npm package