plugins
A marketplace of Claude Code plugins I build for my own use.
Add the marketplace once, install anything from it selectively.
/plugin marketplace add kaushalvivek/plugins
Catalog
| Plugin | Commands | What it does |
|---|
| spotify | /spotify:setup · /spotify:now-playing · /spotify:top · /spotify:profile | Control Spotify playback, query your listening history, and generate a magazine-style visual profile of your musical taste. |
Install:
/plugin install spotify@kaushalvivek/plugins
/spotify:setup
What these plugins have in common
No npm, no node_modules. Everything that needs code is single-file Python.
If you have Python 3.9+, you have the whole stack. No install drift, no lockfile
churn, no runtime surprises.
Setup is a slash command, not a README hunt. Install a plugin, run
/<plugin>:setup, and Claude walks you through whatever needs to happen —
OAuth flows, dev app creation, API keys. No scavenger hunts through docs.
Credentials stay with you. Every plugin that needs auth keeps its secrets
in a dedicated ~/.<plugin>/ directory, chmod 600, owned by you. The plugin
ships no credentials of its own. Nothing is hosted; nothing phones home.
Skills + slash commands, always both. Each plugin exposes a skill (so
Claude fires it automatically when you ask things in natural language) and
explicit slash commands (for when you want deliberate control). Same
capabilities, two doors.
I only publish what I use. If it's here, it earned its place on my own
setup first. No speculative releases, no scaffolding-for-its-own-sake.
Contributing
Bug reports and PRs welcome per-plugin — open issues here and include which
plugin (spotify, etc.) in the title. For anything beyond a one-liner, read
the plugin's own README first.
License
MIT, across the monorepo. See LICENSE.
By Vivek Kaushal.
wshobson
Lucklyric
xrf9268-hue
anthropics