Lukeocodes Claude Plugins
lukeocodes-claude-plugins is a Claude Code plugin for the Build phase that bundles two personal agent-tooling extensions from Luke O’Connor’s workflow.
by lukeocodes · github.com/lukeocodes/claude-plugins
Pull in Luke O’Connor’s personal Claude Code plugins as a small custom agent tooling kit for day-to-day repos.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install lukeocodes-claude-plugins@lukeocodes/claude-pluginsBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:lukeocodes/claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:lukeocodes/claude-plugins").
What it does
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 builder dogfoods, not when you need a documented Flutter or security suite. For Skillselion’s audience, it fits the Build phase under agent-tooling because the outcome is a tweaked Claude Code environment (hooks, helpers, repo-specific rituals) rather than a finished product feature. Solo builders 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.
Highlights
- 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
Why builders use it
Solo builders reinvent one-off Claude Code helpers instead of borrowing small, battle-tested plugin patterns from another developer’s repo.
After you add the collection, you can enable two personal plugins and adapt their commands into your own agent-tooling stack.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 0 stars, 0 votes.
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 solo builder 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.
Comments
Share how you use lukeocodes-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.