Brite Nites Brite Claude Plugins
brite-nites-brite-claude-plugins is a Claude Code plugin for the Operate phase that provides Brite Nites baseline tooling in a one-plugin org bundle.
by Brite-Nites · github.com/Brite-Nites/brite-claude-plugins
Register the Brite Nites organization’s baseline Claude Code plugin bundle so team members share the same default tooling hooks.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install brite-nites-brite-claude-plugins@Brite-Nites/brite-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:Brite-Nites/brite-claude-plugins") and the paste-ready config with skillselion.get_install_config("plugin:Brite-Nites/brite-claude-plugins").
What it does
brite-nites-brite-claude-plugins is a minimal Claude Code plugin bundle published for the Brite Nites organization. Catalog metadata describes it as baseline tools with one plugin in the bundle and keywords centered on britenites and baseline setup. For a solo builder browsing Skillselion, the honest story is narrow: it is primarily useful if you work inside or alongside that organization and need the same default Claude Code plugin registration as the team. It does not advertise a broad skill library, MCP surface, or journey-wide methodology in the ingested readme—placement on Operate / iterate reflects ongoing team alignment rather than idea validation or launch distribution. Install when you want org-parity on Claude Code extensions; skip if you need rich, documented capabilities for a personal indie product. Confidence is lower because public detail beyond org baseline wording is thin.
Highlights
- Claude Code plugin bundle scoped to the Brite Nites organization
- Single-plugin bundle described as baseline tooling for the org
- Community-sourced auto listing with britenites-oriented keywords
- Lightweight entry point before adding heavier custom plugins
- Best treated as internal consistency layer rather than feature shipping
Why builders use it
Contributors on a named org repo lack a shared default Claude Code plugin setup, so everyone wires ad-hoc tools inconsistently.
After you add the bundle, team members can enable the same baseline Brite Nites Claude Code plugin configuration during everyday iteration work.
At a glance
- Type - Plugin in Development Tools.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is brite-nites-brite-claude-plugins for?
It is for people working in the Brite Nites organization who want the standard Claude Code plugin baseline the repo documents.
When should I use brite-nites-brite-claude-plugins?
Use it during Operate-style day-to-day work when you need org-consistent Claude Code tooling rather than when exploring new product ideas.
How do I add brite-nites-brite-claude-plugins to my agent?
Install or register the Brite-Nites/brite-claude-plugins bundle in Claude Code and enable the single baseline plugin per your team’s setup guide.
Comments
Share how you use brite-nites-brite-claude-plugins, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.