Agent skill

Monstermq Broker Config

by vogler75 in vogler75/monster-mq

Guide for configuring, deploying, and operating the MonsterMQ broker.

GPL-3.0Auto-check passedDevOps & Cloud

Install Monstermq Broker Config

skills CLI
$ npx skills add vogler75/monster-mq --skill monstermq-broker-config -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install vogler75/monster-mq monstermq-broker-config --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/vogler75/monster-mq.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/monstermq-broker-config .claude/skills/monstermq-broker-config && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
monstermq-broker-config
GitHub stars
143
Token cost
~2.2k tokens
SKILL.md length
342 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
GPL-3.0

At a glance

Guide for configuring, deploying, and operating the MonsterMQ broker.

  • Works in 3 steps: Broker fails to start → Feature Verticles not loading → Messages not archiving
  • The user needs help with YAML configuration (config.yaml)
  • SKILL.md covers Configuration File (config.yaml), Command-Line Arguments, Docker Deployment and Storage Backend Selection Guide, plus 2 more sections
  • Calls docker; needs GENAI_GEMINI_API_KEY and GENAI_CLAUDE_API_KEY

What it does

Monstermq Broker Config is an agent skill from vogler75/monster-mq. Guide for configuring, deploying, and operating the MonsterMQ broker. Use this skill whenever the user needs help with YAML configuration (config.yaml), Docker deployment, clustering, database setup, storage backend selection, queue store types, feature flags, TLS/SSL certificates, Kafka/NATS integration, or any operational/DevOps task related to MonsterMQ. Also trigger when the user asks about config.yaml structure, environment variables, command-line arguments, or troubleshooting broker startup issues. Trigger…

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud, covering NoSQL databases, Containers and Event-driven systems. It works with Docker, PostgreSQL, MongoDB and Apache Kafka. The repository describes itself as: MonsterMQ is a MQTT broker built on Vert.X and Hazelcast with data persistence through PostgreSQL or CrateDB or MongoDB.. The licence is GPL-3.0.

When your agent uses it

  • The user needs help with YAML configuration (config.yaml)
  • Docker deployment
  • Storage backend selection
  • Queue store types

Example prompts

  • “config.yaml”
  • “Docker”
  • “deploy”
  • “/monstermq-broker-config”

Requirements

  • Docker
  • A credential in GENAI_GEMINI_API_KEY
  • A credential in GENAI_CLAUDE_API_KEY

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Broker fails to start
  2. Feature Verticles not loading
  3. Messages not archiving

What it can do on your machine

Read from SKILL.md and the folder at commit 9edc277. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • docker

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use docker, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GENAI_GEMINI_API_KEY
    • GENAI_CLAUDE_API_KEY
    • GENAI_OPENAI_API_KEY
    • POSTGRES_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Monstermq Broker Config loads about 2.2k tokens when it runs. Until then it costs about 187 tokens; SKILL.md has 342 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~187
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vogler75/monster-mq at commit 9edc277, republished under its GPL-3.0 licence (© vogler75). 342 words, ~2,229 tokens.

Download SKILL.mdSave it as .claude/skills/monstermq-broker-config/SKILL.md (or your agent's skills folder).
name
monstermq-broker-config
description
Guide for configuring, deploying, and operating the MonsterMQ broker. Use this skill whenever the user needs help with YAML configuration (config.yaml), Docker deployment, clustering, database setup, storage backend selection, queue store types, feature flags, TLS/SSL certificates, Kafka/NATS integration, or any operational/DevOps task related to MonsterMQ. Also trigger when the user asks about config.yaml structure, environment variables, command-line arguments, or troubleshooting broker startup issues. Trigger on "config.yaml", "Docker", "deploy", "cluster", "PostgreSQL setup", "MongoDB setup", "Kafka", "TLS", "certificate", "archive group", "storage backend", "feature flags", "queue store", or "how to configure".

MonsterMQ Broker Configuration & Operations Skill

This skill provides instructions for configuring, deploying, operating, and troubleshooting the MonsterMQ MQTT broker process via YAML (config.yaml), environment variables, Docker containers, and CLI flags.

[!NOTE] This skill covers static/startup configuration (config.yaml, Docker, JVM args, clustering, storage backends). For runtime management via GraphQL API (publishing, mutating sessions, creating devices at runtime), use the graphql-config skill instead.


Configuration File (config.yaml)

The broker is configured via config.yaml. The single source of truth for all YAML settings, property types, and default values is the JSON Schema file at broker/yaml-json-schema.json.

Core Structure Example
yaml
# Network listener ports (0 = disabled)
Port:
  TCP: 1883       # Plain MQTT
  TCPS: 8883      # MQTT over TLS
  WS: 1884        # WebSocket
  WSS: 8884       # Secure WebSocket
  HTTP: 4000      # GraphQL API + Dashboard + REST API
  NATS: 4222      # Native NATS listener

# Server Ports (Protocol & Service Servers)
MCP:
  Enabled: true
  Port: 3000
Prometheus:
  Enabled: false
  Port: 3001
I3x:
  Enabled: false
  Port: 3002
RedisServer:
  Enabled: false
  Port: 6379
KafkaServer:
  Enabled: false
  Port: 9092

# Storage backend defaults
DefaultStoreType: POSTGRES | MONGODB | SQLITE # Global default for store types if not overridden
SessionStoreType: POSTGRES | MONGODB | SQLITE | MEMORY
RetainedStoreType: MEMORY | HAZELCAST | POSTGRES | CRATEDB | MONGODB | SQLITE
LastValueStoreType: MEMORY | HAZELCAST | POSTGRES | CRATEDB
QueueStoreType: POSTGRES | MONGODB | SQLITE    # Defaults to DefaultStoreType or persistent SessionStoreType. V2 single-table design.

# Zenoh Broker Federation (Optional)
Zenoh:
  Enabled: false
  Mode: peer | client
  Connect: []
  RemotePrefix: "monstermq/mqtt"
  LocalPrefix: ""

# High-load performance batching
BulkProcessing:
  Enabled: false
  TimeoutMS: 50
  BulkSize: 1000
  WorkerThreads: 4

BulkMessaging:
  Enabled: true
  TimeoutMS: 100
  BulkSize: 1000

# Database connection pools
Postgres:
  Url: "jdbc:postgresql://localhost:5432/monster"
  User: "system"
  Password: "manager"
  Schema: "public"            # Optional PostgreSQL schema name

CrateDB:
  Url: "jdbc:postgresql://localhost:5433/monster"
  User: "crate"
  Password: ""

MongoDB:
  ConnectionString: "mongodb://system:manager@localhost:27017"
  DatabaseName: "monster"

SQLite:
  Path: "sqlite"
  EnableWAL: true

# Message Archiving Groups
ArchiveGroups:
  - Name: "Default"           # Required for MCP Server & general topics
    TopicFilter: ["#"]
    StoreType: Postgres | CrateDB | MongoDB | Kafka
    RetainedStoreType: Postgres | CrateDB
    LastValueStoreType: Postgres | CrateDB

# Top-level Feature Flags (Gating Verticles & GraphQL Mutations)
Features:
  OpcUa: true                 # OPC UA Client bridge
  OpcUaServer: true           # Embedded OPC UA Server
  MqttClient: true            # Remote MQTT broker bridge
  Kafka: true                 # Kafka client bridge
  KafkaServer: true           # Kafka-compatible server
  Nats: true                  # NATS bridge
  Redis: true                 # Redis Pub/Sub & KV bridge
  RedisServer: true           # Redis-compatible protocol server
  Telegram: true              # Telegram bot bridge
  WinCCOa: true               # WinCC OA connector
  WinCCUa: true               # WinCC Unified connector
  Plc4x: true                 # PLC4X connector (S7, Modbus, AB)
  Neo4j: true                 # Neo4j graph database logger
  JdbcLogger: true            # JDBC SQL logger
  InfluxDBLogger: true        # InfluxDB logger device
  TimeBaseLogger: true        # TimeBase logger device
  SparkplugB: true            # SparkplugB decoder
  FlowEngine: true            # Visual flow engine
  Agents: true                # AI agent framework
  GenAi: true                 # GenAI provider management
  Mcp: true                   # MCP server management
  SchemaPolicy: true          # Topic schema policy management
  TopicNamespace: true        # Topic namespace management
  DeviceImportExport: true    # Device configuration import/export
  Zenoh: true                 # Zenoh broker federation transport
  I3xClient: true             # i3X client bridge

# User Management & Auth
Auth:
  UserStoreType: Postgres | MONGODB | SQLITE
  JwtSecret: "your-secret-key"
  TokenExpiry: 3600            # seconds
  PasswordAlgorithm: bcrypt

# GenAI Providers
GenAI:
  Enabled: true
  Providers:
    Gemini:
      ApiKey: "${GENAI_GEMINI_API_KEY}"
    Claude:
      ApiKey: "${GENAI_CLAUDE_API_KEY}"
    OpenAI:
      ApiKey: "${GENAI_OPENAI_API_KEY}"
    Ollama:
      BaseUrl: "http://localhost:11434"

Command-Line Arguments

bash
cd broker
./run.sh [options]

# Run options:
-cluster              Enable Hazelcast clustering mode
-log LEVEL            Set logging verbosity: INFO | FINE | FINER | FINEST | ALL
-config FILE          Path to custom YAML config file (default: config.yaml)
-build                Rebuild Vite dashboard + package JAR before running

Docker Deployment

Build Image
bash
cd docker
./build.sh
Run Container
bash
docker run -d \
  -p 1883:1883 \
  -p 4222:4222 \
  -p 4000:4000 \
  -v ./config.yaml:/app/config.yaml \
  -v ./log:/app/log \
  rocworks/monstermq:latest
Docker Compose Example (PostgreSQL Backend)
yaml
services:
  monstermq:
    image: rocworks/monstermq:latest
    ports:
      - "1883:1883"
      - "4000:4000"
      - "4222:4222"
    volumes:
      - ./config.yaml:/app/config.yaml
    depends_on:
      - postgres

  postgres:
    image: postgres:16
    environment:
      POSTGRES_DB: monster
      POSTGRES_USER: system
      POSTGRES_PASSWORD: manager
    ports:
      - "5432:5432"
    volumes:
      - pgdata:/var/lib/postgresql/data

volumes:
  pgdata:

Storage Backend Selection Guide

Use CaseSession StoreQueue StoreRetained / Last ValueArchive Store
Single Node (Default)PostgreSQLPostgreSQL (V2)PostgreSQLPostgreSQL
High-Volume AnalyticsPostgreSQLPostgreSQLCrateDBCrateDB
Document-OrientedMongoDBMongoDB (V2)MongoDBMongoDB
Lightweight / EmbeddedSQLiteSQLite (V2)Memory / SQLiteSQLite
High-Throughput StreamPostgreSQLPostgreSQLMemoryKafka
Multi-Node ClusterPostgreSQL / MongoDBPostgreSQL / MongoDBHazelcastPostgreSQL / CrateDB
  • Queue Store V2: Uses a PGMQ-inspired single-table design with visibility timeout for high throughput.
  • CrateDB: Best for time-series message archives, but not supported for Session/Queue stores due to eventual consistency.
  • SQLite: Not supported in multi-node clustered setups.

Clustering & High Availability

  • Enable clustering using ./run.sh -cluster.
  • Uses Hazelcast for distributed coordination and message routing.
  • Sessions and Retained Messages live in the shared database store.
  • HA Scope: MQTT client connections can reconnect to any surviving node. Device connectors (OPC UA, PLC4X, bridges) are pinned to their assigned nodeId and recover when their node restarts or when reassigned via GraphQL.

Troubleshooting Startup Issues

1. Broker fails to start
  • Check YAML syntax against broker/yaml-json-schema.json.
  • Verify database connection strings and credentials.
  • Ensure ports (1883, 4000, 4222, 3000, 3001, 3002, 6379, 9092) are not occupied by other processes.
2. Feature Verticles not loading
  • Check the Features block in config.yaml. Verticles for disabled features (e.g. OpcUa: false) are skipped at startup.
3. Messages not archiving
  • Verify an ArchiveGroup exists with a matching TopicFilter.
  • Confirm database connection status in logs or via archiveGroups GraphQL query.

© vogler75, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/monstermq-broker-config of vogler75/monster-mq.

Open the folder on GitHubat commit 9edc277

Compare with similar skills

Monstermq Broker Config next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Monstermq Broker Config compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Monstermq Broker Config this skillvogler75/monster-mq143—~2.2kAutomated safety check: PassGPL-3.0
Use Sealoshashgraph-online/awesome-codex-plugins1.3k—~2.2kAutomated safety check: PassApache-2.0
Fly Io DeployerLeoYeAI/openclaw-master-skills2.2k—~6.3kAutomated safety check: NotesMIT
Releasear-io/ar-io-node127—~4.2kAutomated safety check: NotesAGPL-3.0
Odoo Docker Deploymentsickn33/agentic-awesome-skills47k2 repos~1.2kAutomated safety check: NotesMIT
Create Environmentgodatadriven/whirl205—~1.9kAutomated safety check: PassApache-2.0

Similar skills

  • Use Sealos

    hashgraph-online/awesome-codex-plugins

    Deploy and operate apps on Sealos Cloud: sign in to a Sealos account, deploy any project or self-hosted app (from the template store, an official Docker image, or project source code), provision…

    1.3k GitHub stars~2.2k tokensUpdated yesterday
    DatabasesAuto-check passed
  • Fly Io Deployer

    LeoYeAI/openclaw-master-skills

    Deploy and operate Node, Python, Go, Rust, Elixir, and Docker apps on Fly.io with production-grade fly.toml authoring, Machines API orchestration, region selection (latency vs sovereignty vs…

    2.2k GitHub stars~6.3k tokensUpdated 2 mo ago
    DevOps & CloudAuto-check: notes
  • Release

    ar-io/ar-io-node

    Drive the AR.IO Node release process end-to-end — preflight checks, prepare commit, finalize with image SHAs, test docker compose profiles, tag & publish, and post-release cleanup.

    127 GitHub stars~4.2k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Odoo Docker Deployment

    sickn33/agentic-awesome-skills

    Production-ready Docker and docker-compose setup for Odoo with PostgreSQL, persistent volumes, environment-based configuration, and Nginx reverse proxy.

    47k GitHub starsUsed in 2 repos~1.2k tokens
    DevOps & CloudAuto-check: notes
  • Create Environment

    godatadriven/whirl

    Create a new Whirl environment in the envs/ directory. An agent skill from godatadriven/whirl.

    205 GitHub stars~1.9k tokensUpdated 9 days ago
    Backend & APIsAuto-check passed
  • Self-Hosted n8n Deployment

    czlonkowski/n8n-skills

    Deploys a production n8n instance to a fresh Linux server over SSH with Docker Compose and Caddy HTTPS, in single or queue mode, and covers updates, backups and hardening.

    6.4k GitHub stars~3.5k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes

More from vogler75/monster-mq

  • Guide for developing the MonsterMQ web dashboard. An agent skill from vogler75/monster-mq.

    143 GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Monstermq Graphql Config

    vogler75/monster-mq

    Guide for configuring, managing, and mutating MonsterMQ settings, devices, flows, AI agents, users, loggers, archive groups, topic schemas, and publishing messages via the GraphQL API.

    143 GitHub stars~2.3k tokensUpdated today
    Auto-check passed
  • Monstermq Graphql Data

    vogler75/monster-mq

    Guide for querying MonsterMQ broker data, telemetry, metrics, sessions, live topic values, retained messages, historical message archives, time-series aggregations, ArchiveGroups, OPC UA node…

    143 GitHub stars~4k tokensUpdated today
    Auto-check passed
  • Monstermq Device Integrator

    vogler75/monster-mq

    Guide for integrating new device types into the MonsterMQ broker.

    143 GitHub stars~1.4k tokensUpdated today
    Auto-check passed

Questions about Monstermq Broker Config

What does Monstermq Broker Config do?

Guide for configuring, deploying, and operating the MonsterMQ broker. Monstermq Broker Config is an agent skill from vogler75/monster-mq. Guide for configuring, deploying, and operating the MonsterMQ broker.

When should I use Monstermq Broker Config?

Monstermq Broker Config fits situations like: the user needs help with YAML configuration (config.yaml); Docker deployment; storage backend selection; queue store types.

How do I install Monstermq Broker Config in Claude Code?

Run `npx skills add vogler75/monster-mq --skill monstermq-broker-config -a claude-code`. Or copy the skill folder (.agents/skills/monstermq-broker-config in vogler75/monster-mq) into .claude/skills/monstermq-broker-config in your project. Claude Code loads it when a task matches its description.

How do I install Monstermq Broker Config in Codex?

Run `npx skills add vogler75/monster-mq --skill monstermq-broker-config -a codex`. Or copy the skill folder (.agents/skills/monstermq-broker-config in vogler75/monster-mq) into .agents/skills/monstermq-broker-config in your project. Codex loads it when a task matches its description.

Can I use Monstermq Broker Config in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vogler75/monster-mq --skill monstermq-broker-config -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/monstermq-broker-config, .gemini/skills/monstermq-broker-config, .github/skills/monstermq-broker-config and .opencode/skills/monstermq-broker-config in your project.

What does Monstermq Broker Config need to run?

Going by SKILL.md and its folder, Monstermq Broker Config needs the command-line tools its instructions call (docker) and credentials named GENAI_GEMINI_API_KEY, GENAI_CLAUDE_API_KEY, GENAI_OPENAI_API_KEY and POSTGRES_PASSWORD. Our summary lists: Docker; A credential in GENAI_GEMINI_API_KEY; A credential in GENAI_CLAUDE_API_KEY.

Does Monstermq Broker Config access the network?

SKILL.md contains no URLs. Its commands use docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Monstermq Broker Config safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Monstermq Broker Config use?

Monstermq Broker Config is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Monstermq Broker Config use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Monstermq Broker Config?

Skills that share tags, products or a category with Monstermq Broker Config: Use Sealos (hashgraph-online/awesome-codex-plugins, 1.3k stars), Fly Io Deployer (LeoYeAI/openclaw-master-skills, 2.2k stars), Release (ar-io/ar-io-node, 127 stars) and Odoo Docker Deployment (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Monstermq Broker Config?

vogler75 (a GitHub user) maintains it in vogler75/monster-mq, which has 143 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 11, 2026.

Source: vogler75/monster-mq on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.