
Lukeocodes Claude Plugins
- Updated February 8, 2026
- lukeocodes/claude-plugins
lukeocodes-claude-plugins is a Claude Code plugin that bundles two personal agent-tooling extensions from Luke O’Connor’s workflow.
About
lukeocodes-claude-plugins is Matthias-style personal infrastructure made public: a two-plugin Claude Code collection Luke O’Connor uses on his own projects. Catalog metadata is sparse compared with domain-specific bundles, so you should treat it as an exploratory agent-tooling add-on—install when you want to study or reuse individual commands another developer dogfoods, not when you need a documented Flutter or security suite. For Skillselion’s audience, developers curating their plugin stack often mix one personal repo like this with targeted quality or integration plugins. Read each plugin’s manifest in the repository before enabling anything that touches git, network, or secrets. Expect to adapt naming and triggers to your monorepo; the value is portability of patterns, not enterprise coverage.
- Personal plugin pack from lukeocodes with 2 plugins
- Community-sourced utilities for individual Claude Code workflows
- Lightweight add-on set rather than a full marketplace distribution
- Suitable as a starter reference for authoring your own plugins
- Pairs with other community catalogs when you want niche commands
Lukeocodes Claude Plugins by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install lukeocodes-claude-plugins@lukeocodes/claude-pluginsAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| Last updated | February 8, 2026 |
|---|---|
| Repository | lukeocodes/claude-plugins ↗ |
What it does
Pull in Luke O’Connor’s personal Claude Code plugins as a small custom agent tooling kit for day-to-day repos.
Who is it for?
Claude Code users who browse community plugin repos for inspiration and incremental workflow tweaks.
Skip if: Skip if you need a single well-documented domain plugin with clear SLAs, or teams forbidding unvetted personal plugin sources.
What you get
After you add the collection, you can enable two personal plugins and adapt their commands into your own agent-tooling stack.
- Up to two enabled personal plugins in your Claude Code setup
- Reference implementations you can fork for custom commands
- Incremental workflow automation on your local repos
By the numbers
- Catalog metadata reports plugin count 2
- Repository slug lukeocodes/claude-plugins
- Catalog category community
Recommended Plugins
How it compares
Small personal Claude plugin repo, not a curated multi-skill marketplace or MCP integration server.
FAQ
Who is Lukeocodes Claude Plugins for?
It is for individual Claude Code users who want a minimal, author-maintained plugin set to inspect, fork, or selectively enable—not for org-wide standardized tooling.
When should I use Lukeocodes Claude Plugins?
Use it during Build when you are customizing agent behavior and want to try plugins another developer already uses on real repos.
How do I add Lukeocodes Claude Plugins to my agent?
Register the lukeocodes/claude-plugins GitHub repository in Claude Code’s plugin configuration and enable only the plugins you have reviewed in that repo.