Claude Code Plugins

Choose by task and evidence

For Claude Code, begin with the manifest and the job the package adds. Frontend design guidance, pull-request review and a GitHub connection solve different problems: a design skill can work with project files, while a GitHub integration reaches an external account. The reviewed starting points below make those boundaries explicit. Check whether a package bundles skills, hooks or MCP configuration before enabling it, and use its publisher marketplace instructions for the version you intend to install. A native manifest is evidence of the intended client format, not a completed compatibility test. Try one package in a disposable project, inspect the available command or capability and keep publication and repository writes separately authorized. Security-review hooks can use additional model resources; a package being listed here does not make its connected services free.

Agent labels reflect detected manifests or repository setup documentation. The runtime of each entry has not been tested in every client. Use the evidence links to check your exact client and version.