Tons of Skills
A large Claude Code plugin and skill marketplace with the ccpi CLI and a category-based catalog site
Install
/plugin marketplace add jeremylongshore/claude-code-pluginsThis is third-party code. Review the repository files before installing.
What it does
The repository plugs into Claude Code as a marketplace and gives access to hundreds of plugins with thousands of skills and agents. Plugins are grouped by category: AI and ML, APIs, databases, DevOps, security, testing, SaaS skill packs and more. Individual plugins install via /plugin or the ccpi CLI, and tonsofskills.com offers search across plugins and skills plus task-oriented bundles. Third-party plugins are kept as mirrors that record the author, license and pinned commit.
Who it is for. For Claude Code users looking for ready plugins for a specific stack or service.
Good fit when
- You need a skill pack for a specific SaaS or cloud service
- You need to find a plugin by category, such as DevOps or testing
- You want to install plugins from the command line via ccpi
Not a fit when
- You want only vetted items: the certification program has not launched
- You do not use Claude Code: other harnesses are not officially supported
Example request
Find a DevOps automation plugin in Tons of Skills and install itLimitations
Plugin quality varies and there is no certification yet. Many packs target foreign services that need their own keys and accounts. The marketplace uses the old slug jeremylongshore/claude-code-plugins, which GitHub redirects to the current repo. Each plugin's license is in its manifest.
How to disable. Uninstall plugins via /plugin uninstall and remove the marketplace via /plugin marketplace remove.
Security check
- Plugins from many authors may run commands and hooks
- No quality certification is in place yet
README in short
The README gives two install paths: adding the marketplace in Claude Code and the ccpi CLI. It has a category table and explains four artifact classes: first-party skills, generated adapters, author packages and mirrors of others' plugins. It covers contribution rules, governance and the mirroring model for third-party repos. MIT for the scaffolding; plugins carry their own licenses.
FAQ
Why does the command use the old repo name?
The authors kept it for compatibility, and GitHub redirects it to the new repo.
Are plugins vetted?
No certification yet; third-party plugins are mirrors that credit the original source.
Related
Open-source personal AI assistant on your own machine: answers in Telegram, Slack, Discord and WhatsApp, extended with skills and plugins
A self-improving agent from Nous Research with a TUI, messaging gateway, cron jobs and skills it writes itself
An open source coding agent for the terminal and desktop with build and plan modes
Open prompt library with a Claude Code plugin, MCP server and CLI: search, fetch and improve prompts and skills from an agent