Skip to content
Skills Library
Programming · Building & coding

solace-application-development

/solace-application-development

Use when the user mentions JCSMP, the com.solacesystems:sol-jcsmp library, JCSMPSession, publishing to a Solace topic, consuming from a Solace queue, or guaranteed messaging, OR asks broadly to build or design a Solace messaging app in Java (publisher, consumer, pub/sub). This is the single front door for Solace API development: it grounds the work in canonical Solace docs and routes the request to the right API (JCSMP today), helping choose a messaging pattern or generate a runnable Maven app. Do NOT trigger for an explicitly named non JCSMP API, which beats the generic Java signal: Solace JM

Licence
Apache-2.0
Last repository change
11.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
25
Scripts
12
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 11.09.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What to check before installing
  • 12 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: references/jcsmp/evals/compile-fixture/ConfigSmokeTest.java, references/jcsmp/evals/compile-fixture/compile.sh, references/jcsmp/jcsmp-direct-publisher-sample.java, references/jcsmp/jcsmp-direct-replier-sample.java, references/jcsmp/jcsmp-direct-requestor-sample.java, references/jcsmp/jcsmp-direct-subscriber-sample.java, references/jcsmp/jcsmp-guaranteed-publisher-sample.java, references/jcsmp/jcs

What it does and when to use it

Use when the user mentions JCSMP, the com.solacesystems:sol-jcsmp library, JCSMPSession, publishing to a Solace topic, consuming from a Solace queue, or guaranteed messaging, OR asks broadly to build or design a Solace messaging app in Java (publisher, consumer, pub/sub). This is the single front door for Solace API development: it grounds the work in canonical Solace docs and routes the request to the right API (JCSMP today), helping choose a messaging pattern or generate a runnable Maven app. Do NOT trigger for an explicitly named non JCSMP API, which beats the generic Java signal: Solace JM

Original author description

Use when the user mentions JCSMP, the com.solacesystems:sol-jcsmp library, JCSMPSession, publishing to a Solace topic, consuming from a Solace queue, or guaranteed messaging, OR asks broadly to build or design a Solace messaging app in Java (publisher, consumer, pub/sub). This is the single front door for Solace API development: it grounds the work in canonical Solace docs and routes the request to the right API (JCSMP today), helping choose a messaging pattern or generate a runnable Maven app. Do NOT trigger for an explicitly named non JCSMP API, which beats the generic Java signal: Solace JM

How it works

  1. IMPORTANT: Lazy-Load References Only
  2. What is Solace
  3. API Selection
  4. Invariants
  5. Reference Files (read on-demand only)
Original SKILL.md headings · 47 lines, 919 words
SKILL.md preview
---
name: solace-application-development
description: "Use when the user mentions JCSMP, the com.solacesystems:sol-jcsmp library, JCSMPSession, publishing to a Solace topic, consuming from a Solace queue, or guaranteed messaging, OR asks broadly to build or design a Solace messaging app in Java (publisher, consumer, pub/sub). This is the single front door for Solace API development: it grounds the work in canonical Solace docs and routes the request to the right API (JCSMP today), helping choose a messaging pattern or generate a runnable Maven app. Do NOT trigger for an explicitly named non JCSMP API, which beats the generic Java signal: Solace JMS, or the Solace Python, Go, .NET, or JavaScript APIs. Also do NOT trigger for Apache Kafka, broker administration and configuration, Solace Event Portal event modeling, Schema Registry, OpenTelemetry tracing, or topic-architecture and topic-hierarchy design questions (use solace-topic-best-practices)."
allowed-tools: Read Write Edit Bash Grep Glob WebFetch
---

# Solace API Development

This skill is the front door for building Solace messaging applications grounded in canonical Solace documentation: identify the target API from the API Selection table below, then lazy-load that API's reference files for the detailed, mode-based guidance.

## IMPORTANT: Lazy-Load References Only

**Do NOT read all reference files upfront. Read ONLY what you need, when you need it.**

- User wants a JCSMP application (design help or code generation) then read `references/jcsmp.md`, which selects the right mode within the JCSMP API.
- Read a mode file only at the moment a step needs it.
- Most requests need the API's entry file plus one mode file, not the whole tree.

**Never read multiple reference files preemptively "just in case".**

## What is Solace

Solace is an event-driven messaging platform: an event broker carries messages between applications, brokers connect into an event mesh, publishers send to named topics, and consumers read either directly or from durable queues that subscribe to those topics (the publish and subscribe model). Solace Cloud is the primary broker this skill assumes for the work it generates; a self-hosted Software Broker or an existing Appliance are supported alternatives. The canonical [Solace Core Concepts](https://docs.solace.com/Get-Started/event-mesh-basics.md) page is the doc grounding for this model.

For topic-hierarchy and topic-architecture design questions, the co-installed solace-topic-best-practices skill reads the canonical Topic Architecture Best Practices page online and applies it to those decisions.

## API Selection

Determine which Solace API the developer is building against, then read that API's entry file from the table.

| User intent | API | What to do |
|---|---|---|
| Anything about JCSMP, the `com.solacesystems:sol-jcsmp` library, a Java publisher or consumer, publishing to a topic, or consuming from a queue with guaranteed messaging | **JCSMP** | Read `references/jcsmp.md` |

If the API is unclear but the request is clearly about Solace messaging in Java, default to **JCSMP**. Mode detection (Design, Implement) then happens in that API's entry file.

## Invariants

Non-negotiable rules that apply across every API. Apply all.

1. **Content sourcing**: Every named entity (API, parameter, configuration value) must be traceable to a canonical Solace source. Do not assert behavior, defaults, or best practices that are not in the grounding documentation.
2. **WebFetch-on-demand doc grounding**: This skill bundles no documentation. When a step needs documentation content to ground a generation or design decision, WebFetch the live canonical page on demand (its `docs.solace.com` `.md` URL, the same link the reference files carry), then quote or summarize the fetched page. Do not answer from memory and do not paraphrase guidance the page does not contain. Do not restate doc content in the skill; link the live `.md` URL. Never substitute another channel for that WebFetch: grounding taken from a docs chatbot, a search tool, or decompiling a jar does not satisfy this invariant, and a page never fetched in the session must never be cited as grounding. A short list of references stays live for the same reason it always has (Javadoc HTML, the JCSMP API Release Notes, Maven Central, the tutorials, and the GitHub samples) because those have no `docs.solace.com` `.md` form.
3. **No hardcoded versions**: Never pin a library version anywhere in skill content. The generated build resolves the latest release of every dependency at generation time from the AUTHORITATIVE Maven repository metadata; each API's entry file names the exact coordinate and carries the exact lookup command. Never read a version from the legacy `search.maven.org/solrsearch` index: it lags the repository metadata and reports stale versions. Security floors (a minimum version below which known CVEs live) are enforced as checks on the resolved result, never as pins.
4. **AI-assisted disclaimer header**: Every source file generated under this skill starts with this exact line: `AI-assisted code. Review before production use.` Directly below it: `See the verification checklist: solace-verification-checklist.md`. This applies to EVERY generated source file, including custom builds, web apps, and embedded shapes that adapt the reference samples outside the canonical generator. The pom and other non-source artifacts are exempt; the bundled reference samples themselves carry no header.
5. **Verification artifacts, always**: Any session that generates Solace code from this skill writes a tailored `solace-verification-checklist.md` beside the code as generation output, copies the bundled `verify.sh` (plus its generated `verify-hooks.sh`) into the project, and ends in a real verify run or the compile-only fallback with the exact handed-back commands. The `VERIFY:` markers are non-optional in generated Solace messaging code, whatever the app shape. An improvised check (for example curl against the app's own HTTP API) may TRIGGER traffic but never renders the verdict; the verdict comes from the markers and the verify exit code.
6. **Live-broker heads-up**: Immediately before starting ANY process that will connect to a live broker — verify.sh, `java -jar`, a `mvn` run, a run script, anything — print one line that names the broker host and states the actual broker-side effects of this run (the queues it provisions, the connections it opens, the messages it publishes), scaled to the real app. Environment discovery is never consent and never an answer: a running local broker, an existing config file, or found credentials are facts to report, not answers to consume; report them, then still ask which broker the developer wants to target.

## Reference Files (read on-demand only)

- `references/jcsmp.md`: the JCSMP entry file (mode detection, the JCSMP coordinate, and the live JCSMP doc links); read this for any JCSMP request.
- `references/jcsmp/`: all JCSMP API content (mode files, the reference samples, the verify script, and the compile fixture), reached through `references/jcsmp.md`.
Files in this package (25)
  • SKILL.md 7 KB
  • references/jcsmp.md 10 KB
  • references/jcsmp/custom-mode.md 10 KB
  • references/jcsmp/design-mode.md 16 KB
  • references/jcsmp/implement-direct-pubsub.md 8 KB
  • references/jcsmp/implement-guaranteed-pubsub.md 11 KB
  • references/jcsmp/implement-mode.md 51 KB
  • references/jcsmp/implement-request-reply.md 23 KB
  • references/jcsmp/jcsmp-direct-publisher-sample.java 14 KB
  • references/jcsmp/jcsmp-direct-replier-sample.java 15 KB
  • references/jcsmp/jcsmp-direct-requestor-sample.java 13 KB
  • references/jcsmp/jcsmp-direct-subscriber-sample.java 12 KB
  • references/jcsmp/jcsmp-guaranteed-publisher-sample.java 17 KB
  • references/jcsmp/jcsmp-guaranteed-replier-sample.java 22 KB
  • references/jcsmp/jcsmp-guaranteed-requestor-sample.java 16 KB
  • references/jcsmp/jcsmp-guaranteed-subscriber-sample.java 18 KB
  • references/jcsmp/jcsmp-solace-connection-config.java 9 KB
  • references/jcsmp/prerequisites.md 1 KB
  • references/jcsmp/solace-suggested-mode.md 15 KB
  • references/jcsmp/verification-checklist.md 9 KB
  • references/jcsmp/evals/compile-fixture/.gitignore 1 KB
  • references/jcsmp/evals/compile-fixture/ConfigSmokeTest.java 4 KB
  • references/jcsmp/evals/compile-fixture/compile.sh 11 KB
  • references/jcsmp/evals/compile-fixture/pom.xml 3 KB
  • references/jcsmp/scripts/verify.sh 54 KB

Versions

The database has no other skills named solace-application-development.

Database snapshot: 13.11.2026 · package version 0edf05df0e08 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90solace-topic-best-practices
    Use when the user asks how to structure, design, name, or organize a Solace topic hierarchy: choosing topic levels, ordering levels from general to specific, topic taxonomy or naming conventions, where to place wildcards for subscriptions, or topic-architecture best practices in…
  • 100solace-messaging-feedback
    Formats the current session into copy-paste-ready feedback about the Solace Agent Skills, routed by support-contract status: users with a Solace support contract get an email to Solace Support (support@solace.com) for bugs and a Solace Ideas portal submission for feature ideas,…
  • 100strict-theme-solace
    Build UI in the Solace theme from strictthemes.com. A soft, steady theme for therapists, coaches and private practices. Blush paper, indigo ink, and mauve greys with no signal color. Use it when the project's DESIGN.md is Solace, or when the user asks for the Solace theme. It…
  • 100redis-pubsub
    Redis Pub/Sub and Streams for messaging. Covers publish/subscribe, streams with consumer groups, and real-time patterns. Use for lightweight messaging and real-time features. USE WHEN: user mentions "redis pub/sub", "redis streams", "real-time messaging", "lightweight…
  • 100aws-sdk-java-v2-messaging
    Provides AWS messaging patterns using AWS SDK for Java 2.x for SQS queues and SNS topics. Handles sending/receiving messages, FIFO queues, DLQ, subscriptions, and pub/sub patterns. Use when implementing messaging with SQS or SNS.
  • 100azure-eventgrid-java
    Build event-driven applications with Azure Event Grid SDK for Java. Use when publishing events, implementing pub/sub patterns, or integrating with Azure services via events.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.