npx claudepluginhub coreos/ai-helpersSummarize the status of the RHCOS pipeline using Slack
Summarize the RHCOS OCPBUGS with an open Customer Case
Analyze and categorize RHCOS CVEs for verification readiness
Analyze Jenkins build failures and generate summaries with root cause findings
Production-ready workflow orchestration with 75 focused plugins, 182 specialized agents, and 147 skills - optimized for granular installation and minimal token usage
Claude Code marketplace entries for the plugin-safe Antigravity Awesome Skills library and its compatible editorial bundles.
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations
A collection of Claude Code plugins to automate and assist with various development tasks.
Add the marketplace:
/plugin marketplace add coreos/ai-helpers
Install a plugin:
/plugin install pipeline-status@ai-helpers
Use the commands:
/pipeline-status
Cursor is able to find the various commands defined in this repo by
making it available inside your ~/.cursor/commands directory.
$ mkdir -p ~/.cursor/commands
$ git clone git@github.com:coreos/ai-helpers.git
$ ln -s ai-helpers ~/.cursor/commands/ai-helpers
Want to contribute or create your own plugins? Check out the plugins/ directory for examples.
Plugins, commands, skills, and hooks must NEVER reference real people by name, even as stylistic examples (e.g., "in the style of <specific human>").
Ethical rationale:
Instead, describe specific qualities explicitly
Good examples:
When you identify a desirable characteristic (clarity, brevity, formality, humor, etc.), describe it explicitly rather than using a person as proxy.
When contributing new commands:
commands/ directoryplugins/utils/commands/)
If you're contributing several related commands that warrant their own plugin:
plugins/ with your plugin nameplugins/your-plugin/
├── .claude-plugin/
│ └── plugin.json
└── commands/
└── your-command.md
.claude-plugin/marketplace.jsonSee LICENSE for details.