Add Property Type
yontrack/yontrack
Add a complete Yontrack property type — Kotlin PropertyType class, GraphQL mutation provider, and all required frontend UI components (Icon, Display, Form, FormPrepare).
Guide for integrating new device types into the MonsterMQ broker.
Install Monstermq Device Integrator
$ npx skills add vogler75/monster-mq --skill monstermq-device-integrator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vogler75/monster-mq monstermq-device-integrator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vogler75/monster-mq.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/monstermq-device-integrator .claude/skills/monstermq-device-integrator && rm -rf skills-srcUse ~/.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/
Install the "monstermq-device-integrator" agent skill from https://github.com/vogler75/monster-mq/tree/main/.agents/skills/monstermq-device-integrator into .claude/skills/monstermq-device-integrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monstermq-device-integrator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vogler75/monster-mq/tree/main/.agents/skills/monstermq-device-integratorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vogler75/monster-mq --skill monstermq-device-integrator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vogler75/monster-mq monstermq-device-integrator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vogler75/monster-mq.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/monstermq-device-integrator .agents/skills/monstermq-device-integrator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "monstermq-device-integrator" agent skill from https://github.com/vogler75/monster-mq/tree/main/.agents/skills/monstermq-device-integrator into .agents/skills/monstermq-device-integrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monstermq-device-integrator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vogler75/monster-mq --skill monstermq-device-integrator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vogler75/monster-mq monstermq-device-integrator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vogler75/monster-mq.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/monstermq-device-integrator .cursor/skills/monstermq-device-integrator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "monstermq-device-integrator" agent skill from https://github.com/vogler75/monster-mq/tree/main/.agents/skills/monstermq-device-integrator into .cursor/skills/monstermq-device-integrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monstermq-device-integrator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vogler75/monster-mq.git --path .agents/skills/monstermq-device-integrator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vogler75/monster-mq --skill monstermq-device-integrator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vogler75/monster-mq monstermq-device-integrator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vogler75/monster-mq.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/monstermq-device-integrator .gemini/skills/monstermq-device-integrator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "monstermq-device-integrator" agent skill from https://github.com/vogler75/monster-mq/tree/main/.agents/skills/monstermq-device-integrator into .gemini/skills/monstermq-device-integrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monstermq-device-integrator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vogler75/monster-mq monstermq-device-integratorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vogler75/monster-mq --skill monstermq-device-integrator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vogler75/monster-mq.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/monstermq-device-integrator .github/skills/monstermq-device-integrator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "monstermq-device-integrator" agent skill from https://github.com/vogler75/monster-mq/tree/main/.agents/skills/monstermq-device-integrator into .github/skills/monstermq-device-integrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monstermq-device-integrator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vogler75/monster-mq --skill monstermq-device-integrator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vogler75/monster-mq monstermq-device-integrator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vogler75/monster-mq.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/monstermq-device-integrator .opencode/skills/monstermq-device-integrator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "monstermq-device-integrator" agent skill from https://github.com/vogler75/monster-mq/tree/main/.agents/skills/monstermq-device-integrator into .opencode/skills/monstermq-device-integrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "monstermq-device-integrator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
monstermq-device-integrator- GitHub stars
- 143
- Token cost
- ~1.4k tokens
- SKILL.md length
- 461 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Guide for integrating new device types into the MonsterMQ broker.
- Works in 9 steps: Configuration Data Class → Connector Verticle (Per-Device Instance) → Extension Verticle (Coordinator &… → …
- The user wants to add a new device connector
- SKILL.md covers Architecture Blueprint & Core…, End-to-End Implementation Order and Verification Checklist
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Monstermq Device Integrator is an agent skill from vogler75/monster-mq. Guide for integrating new device types into the MonsterMQ broker. Use this skill whenever the user wants to add a new device connector, bridge, or protocol integration to MonsterMQ. This includes creating backend Kotlin verticles (Connector + Extension), GraphQL schema/resolvers, and dashboard UI pages. Trigger on requests like "add a new device type", "integrate Modbus", "create an OPC UA connector", "bridge protocol X to MQTT", "add a new client type", or any mention of connecting external systems/devices to…
Its SKILL.md is about 1.4k 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 Backend & APIs, covering GraphQL and Android development. It works with GraphQL and Kotlin. 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 wants to add a new device connector
- Protocol integration to MonsterMQ
- Requests like add a new device type
- Integrate Modbus
Example prompts
- “add a new device type”
- “integrate Modbus”
- “create an OPC UA connector”
- “/monstermq-device-integrator”
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 8a18e36. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Monstermq Device Integrator loads about 1.4k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 461 words of instructions outside code blocks.
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 8a18e36, republished under its GPL-3.0 licence (© vogler75). 461 words, ~1,407 tokens.
Download SKILL.mdSave it as
.claude/skills/monstermq-device-integrator/SKILL.md (or your agent's skills folder).- name
- monstermq-device-integrator
- description
- Guide for integrating new device types into the MonsterMQ broker. Use this skill whenever the user wants to add a new device connector, bridge, or protocol integration to MonsterMQ. This includes creating backend Kotlin verticles (Connector + Extension), GraphQL schema/resolvers, and dashboard UI pages. Trigger on requests like "add a new device type", "integrate Modbus", "create an OPC UA connector", "bridge protocol X to MQTT", "add a new client type", or any mention of connecting external systems/devices to MonsterMQ.
Device Integration Skill for MonsterMQ
This skill provides step-by-step instructions for adding a new device connector, industrial protocol bridge, or database logger into MonsterMQ across the Kotlin backend, GraphQL API, and Vite dashboard.
Architecture Blueprint & Core Reference
Read the primary specification guide at dev/plans/plan-device-integration.md — it contains the complete Extension + Connector architecture overview, code templates, and verification checklist.
Reference Implementations by Complexity
- Simple Bridge: MQTT Client (
devices/mqttclient/,graphql/MqttClient*, dashboardmqtt-client*) - Medium Protocol: PLC4X (
devices/plc4x/,graphql/Plc4x*, dashboardplc4x-*) - Complex Industrial: WinCC Unified (
devices/winccua/,graphql/WinCCUa*, dashboardwinccua-*)
End-to-End Implementation Order
Follow this 9-step sequence:
1. Configuration Data Class
Location: broker/src/main/kotlin/stores/devices/YourDeviceConfig.kt
- Define data class with
fromJsonObject()companion andtoJsonObject()method. - Support address/tag mappings if the device bridges external points to MQTT topics.
- Include sensible defaults for timeouts, reconnect delays, and retry counts.
2. Connector Verticle (Per-Device Instance)
Location: broker/src/main/kotlin/devices/yourdevice/YourDeviceConnector.kt
- Extends Vert.x
AbstractVerticle. - Loads configuration from
config().getJsonObject("device"). - Implements connection lifecycle: connect, disconnect, exponential backoff reconnect.
- Publishes incoming messages to the message bus or Vert.x eventbus.
- Tracks metrics (
messagesInCounter,messagesOutCounter,isConnected) and responds to eventbus queries.
3. Extension Verticle (Coordinator & Cluster Manager)
Location: broker/src/main/kotlin/devices/yourdevice/YourDeviceExtension.kt
- Manages connector verticles for this device type across the node.
- Cluster-aware: checks
clusterManager.isLocalNodeResponsible(device.id). - Listens for configuration changes on
EventBusAddresses.Device.configChanged(TYPE). - Deploys/undeploys connector verticles via
vertx.deployVerticle().
4. Register Verticle in Main (Monster.kt) & Feature Flag
Location: broker/src/main/kotlin/Monster.kt and Features.kt
- Declare top-level feature flag constant in
broker/src/main/kotlin/Features.kt(const val YourDevice = "YourDevice") and append toFeatures.all. - Declare feature property under
properties.Features.propertiesinbroker/yaml-json-schema.json. - Gate verticle deployment in
Monster.kt(if (Monster.isFeatureEnabled(Features.YourDevice)) { ... }). - Gate all GraphQL query and mutation resolver methods with
if (!Monster.isFeatureEnabled(Features.YourDevice)).
5. GraphQL Schema Definition
Location: broker/src/main/resources/ (schema-types.graphqls, schema-queries.graphqls, schema-mutations.graphqls)
- Add data types and status types in
schema-types.graphqls. - Add query endpoints in
schema-queries.graphqlsand mutation endpoints inschema-mutations.graphqls. - Always keep query output
Typemodels separate from mutation inputInputTypemodels.
Show full SKILL.md (168 more words)Show less
6. GraphQL Resolvers
Location: broker/src/main/kotlin/graphql/YourDeviceConfigQueries.kt and YourDeviceConfigMutations.kt
- Gate resolver methods with
if (!Monster.isFeatureEnabled(Features.YourDevice)). - Query resolver fetches live metrics via EventBus.
- Mutation resolver creates/updates/deletes device configuration via
IDeviceConfigStore. - Preserve existing passwords on update if not provided in input.
7. Dashboard List Page
Location: dashboard/src/pages/yourdevice-clients.html + src/js/yourdevice-clients.js
- Build using List Page Shape (header, metric-cards, table with status indicators and action buttons).
- Use
window.graphqlClientfor queries andwindow.uifor notifications.
8. Dashboard Detail Page
Location: dashboard/src/pages/yourdevice-client-detail.html + src/js/yourdevice-client-detail.js
- Build using Detail Page Shape (breadcrumb header, section-cards, form controls).
- Read ID from URL params (
new URLSearchParams(window.location.search).get('id')). - Handle both Create mode and Edit mode without clearing existing passwords.
9. Dashboard Sidebar Navigation
Location: dashboard/src/js/sidebar.js
- Add menu item to
getMenuConfig()under theBridgingsection withfeature: 'YourDevice'.
Verification Checklist
After implementation, verify:
- Backend verticle starts cleanly when enabled via feature flag.
- GraphQL query returns active device configuration and live metrics.
- GraphQL mutation correctly creates, updates, and deletes devices.
- Dashboard list and detail views function properly without CSS component overrides.
- Reconnection logic handles external device disconnects smoothly.
© 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-device-integrator of vogler75/monster-mq.
Open the folder on GitHubat commit 8a18e36
Compare with similar skills
Monstermq Device Integrator 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Monstermq Device Integrator this skillvogler75/monster-mq | 143 | — | ~1.4k | Automated safety check: Pass | GPL-3.0 | |
| Add Property Typeyontrack/yontrack | 102 | — | ~990 | Automated safety check: Pass | MIT | |
| Apollo Kotlinapollographql/skills | 117 | — | ~547 | Automated safety check: Pass | MIT | |
| Inspect Network TrafficHedvigInsurance/android | 154 | — | ~756 | Automated safety check: Pass | AGPL-3.0 | |
| ShopifyShopify/Shopify-AI-Toolkit | 592 | — | ~4.2k | Automated safety check: Pass | MIT | |
| Kotlin Ktor Patternsaffaan-m/ECC | 276k | 4 repos | ~4.8k | Automated safety check: Pass | MIT |
Similar skills
Apollo Kotlin
apollographql/skills
Guide for building applications with Apollo Kotlin, the GraphQL client library for Android and Kotlin.
Inspect Network Traffic
HedvigInsurance/android
Read the HTTP and GraphQL calls a debug build of the Android app made, with request and response bodies, status codes, timings and errors, over adb.
- Official
Shopify
Shopify/Shopify-AI-Toolkit
Build anything on Shopify. An agent skill from Shopify/Shopify-AI-Toolkit.
Kotlin Ktor Patterns
affaan-m/ECC
Ktor server patterns including routing DSL, plugins, authentication, Koin DI, kotlinx.serialization, WebSockets, and testApplication testing.
Apollo iOS
apollographql/skills
Guide for building Apple-platform applications with Apollo iOS, the strongly-typed GraphQL client for Swift.
More from vogler75/monster-mq
Monstermq Broker Config
vogler75/monster-mq
Guide for configuring, deploying, and operating the MonsterMQ broker.
Monstermq Dashboard Developer
vogler75/monster-mq
Guide for developing the MonsterMQ web dashboard. An agent skill from vogler75/monster-mq.
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.
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…
Related
Categories
Questions about Monstermq Device Integrator
What does Monstermq Device Integrator do?
Guide for integrating new device types into the MonsterMQ broker. Monstermq Device Integrator is an agent skill from vogler75/monster-mq. Guide for integrating new device types into the MonsterMQ broker.
When should I use Monstermq Device Integrator?
Monstermq Device Integrator fits situations like: the user wants to add a new device connector; protocol integration to MonsterMQ; requests like add a new device type; integrate Modbus.
How do I install Monstermq Device Integrator in Claude Code?
Run `npx skills add vogler75/monster-mq --skill monstermq-device-integrator -a claude-code`. Or copy the skill folder (.agents/skills/monstermq-device-integrator in vogler75/monster-mq) into .claude/skills/monstermq-device-integrator in your project. Claude Code loads it when a task matches its description.
How do I install Monstermq Device Integrator in Codex?
Run `npx skills add vogler75/monster-mq --skill monstermq-device-integrator -a codex`. Or copy the skill folder (.agents/skills/monstermq-device-integrator in vogler75/monster-mq) into .agents/skills/monstermq-device-integrator in your project. Codex loads it when a task matches its description.
Can I use Monstermq Device Integrator 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-device-integrator -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-device-integrator, .gemini/skills/monstermq-device-integrator, .github/skills/monstermq-device-integrator and .opencode/skills/monstermq-device-integrator in your project.
What does Monstermq Device Integrator need to run?
SKILL.md names no scripts, command-line tools or credentials: Monstermq Device Integrator is instructions for the agent only.
Does Monstermq Device Integrator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Monstermq Device Integrator 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 Device Integrator use?
Monstermq Device Integrator 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 Device Integrator use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 Device Integrator?
Skills that share tags, products or a category with Monstermq Device Integrator: Add Property Type (yontrack/yontrack, 102 stars), Apollo Kotlin (apollographql/skills, 117 stars), Inspect Network Traffic (HedvigInsurance/android, 154 stars) and Shopify (Shopify/Shopify-AI-Toolkit, 592 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Monstermq Device Integrator?
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 10, 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.