A collection of Solace AI agent plugins that package skills for building event-driven messaging applications. These skills help developers using AI coding assistants (such as Claude Code) design and implement Solace messaging applications that follow Solace best practices out of the gate. The solace-application-development skill designs and generates Solace messaging applications (publishing to topics, consuming from queues, and guaranteed messaging), starting with the Solace Messaging API for JCSMP. A companion solace-topic-best-practices skill looks up the canonical Topic Architecture Best Practices page online and applies it to topic-hierarchy decisions.
Warning
These skills are powered by language models, which are nondeterministic and may change over time. Generated code can vary between runs and may be incorrect, insecure, incomplete, or unsuitable for your environment. You are responsible for reviewing, testing, and validating all generated code before use, especially before deploying to production.
/plugin marketplace add SolaceProducts/agent-plugins
/plugin install solace-messaging-skills@solace-agent-pluginsThis lets you pick specific skills to install and supports most agents.
npx skills add SolaceProducts/agent-pluginsSolace Cloud is the primary, recommended broker for the applications these skills generate. A self-hosted Software Broker or an existing Appliance work as alternatives.
- Install the skills using one of the methods above
- Open a project where you want to build a Solace messaging application
- Ask your AI agent (for example, Claude) to help design or implement a Solace messaging application
- The relevant skill will automatically activate based on your request
Example prompts:
- "Design a Solace application that publishes order events to a topic"
- "Build a Solace app that publishes to a topic and consumes from a durable queue"
This repository includes the following skills:
| Skill | Description |
|---|---|
| solace-application-development | Routes Solace messaging design and implementation requests to grounded Solace documentation. Full guidance for messaging pattern selection, runnable code generation, and message round trip verification arrives in upcoming releases. |
| solace-topic-best-practices | Navigation-only lookup skill that reads the canonical Topic Architecture Best Practices page online and applies it to topic-hierarchy decisions, without generating application code. |
| solace-messaging-feedback | Formats the current session into copy-paste-ready feedback about the skills, routed by support-contract status: contract holders get an email to Solace Support for bugs and a Solace Ideas portal submission for feature ideas, users without a contract get a Solace Community post for both. Formatter only: it produces the text for you to review and send or post, and never sends anything itself. |
agent-plugins/
├── plugins/ # Claude plugins, one subdirectory per plugin
│ └── solace-messaging-skills/ # The messaging skills plugin
│ ├── .claude-plugin/ # Plugin definition (plugin.json)
│ ├── evals/ # Trigger eval corpus (trigger-evals.json) and its README
│ └── skills/ # Individual skill definitions (shared by all agents)
│ ├── solace-application-development/ # Solace application development umbrella skill
│ │ ├── SKILL.md # Skill routing and instructions
│ │ └── references/ # Assets referenced by SKILL.md (per-API subfolders)
│ ├── solace-topic-best-practices/ # Online topic-architecture lookup skill
│ │ └── SKILL.md # Navigation-only manifest; reads the live docs page
│ └── solace-messaging-feedback/ # Feedback formatter skill
│ └── SKILL.md # Formats and routes session feedback (Support, Community, or Ideas portal)
├── tools/ # Re-runnable scripts (check-links, run-trigger-evals)
├── README.md # This file
└── .claude-plugin/ # Claude marketplace definition (marketplace.json)
Each plugin ships a trigger eval corpus under plugins/<plugin>/evals/ that checks each skill fires on the prompts it should and stays silent on the prompts it should not. See the trigger evals README for the corpus format, how to run the evals locally, and how they run in CI.
This project is licensed under the Apache License 2.0. See the LICENSE file for details.