Agent skill

Monstermq Graphql Data

by vogler75 in 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…

GPL-3.0Auto-check passedBackend & APIs

Install Monstermq Graphql Data

skills CLI
$ npx skills add vogler75/monster-mq --skill monstermq-graphql-data -a claude-code

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

GitHub CLI
$ gh skill install vogler75/monster-mq monstermq-graphql-data --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-graphql-data .claude/skills/monstermq-graphql-data && 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-graphql-data
GitHub stars
143
Token cost
~4k tokens
SKILL.md length
641 words
Files
1
Skills in repo
5
Repo updated
First seen
Licence
GPL-3.0

At a glance

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

  • Works in 10 steps: Connection & Endpoint Overview → Broker Status & Telemetry Queries → Archive Groups & Storage Discovery Queries → …
  • You need to fetch data
  • SKILL.md covers 1. Connection & Endpoint…, 2. Broker Status & Telemetry…, 3. Archive Groups & Storage… and 4. Topic Values & Live…, plus 5 more sections
  • Calls curl

What it does

Monstermq Graphql Data is an agent skill from 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 browsing, topic schemas, flow engine statuses, AI agent conversations, and real-time GraphQL subscriptions. Use this skill whenever you need to fetch data, monitor broker health, read topic values, query historical data, check available archive groups/backends, or subscribe to live MQTT updates from MonsterMQ via GraphQL…

Its SKILL.md is about 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 Forecasting and time series. It works with GraphQL. 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

  • You need to fetch data
  • Monitor broker health
  • Read topic values
  • Query historical data

Example prompts

  • “query topic”
  • “get metrics”
  • “read message archive”
  • “/monstermq-graphql-data”

Workflow steps

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

  1. Connection & Endpoint Overview
  2. Broker Status & Telemetry Queries
  3. Archive Groups & Storage Discovery Queries
  4. Topic Values & Live Telemetry Queries
  5. Historical Message Archives & Analytics Queries
  6. Client Sessions & System Logs
  7. Device Connector & OPC UA Queries
  8. Flow Engine, AI Agents & Topic Schemas
  9. Real-Time GraphQL Subscriptions
  10. End-to-End Client Implementation Example

What it can do on your machine

Read from SKILL.md and the folder at commit 5920123. 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:

    • curl

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

  • Network

    No URLs in SKILL.md. Its commands use curl, 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 no API keys, tokens, secrets or passwords.

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

Context cost

Monstermq Graphql Data loads about 4k tokens when it runs. Until then it costs about 211 tokens; SKILL.md has 641 words of instructions outside code blocks.

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

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 5920123, republished under its GPL-3.0 licence (© vogler75). 641 words, ~3,997 tokens.

Download SKILL.mdSave it as .claude/skills/monstermq-graphql-data/SKILL.md (or your agent's skills folder).
name
monstermq-graphql-data
description
Guide for querying MonsterMQ broker data, telemetry, metrics, sessions, live topic values, retained messages, historical message archives, time-series aggregations, ArchiveGroups, OPC UA node browsing, topic schemas, flow engine statuses, AI agent conversations, and real-time GraphQL subscriptions. Use this skill whenever you need to fetch data, monitor broker health, read topic values, query historical data, check available archive groups/backends, or subscribe to live MQTT updates from MonsterMQ via GraphQL. Trigger on "query topic", "get metrics", "read message archive", "browse topics", "check sessions", "get broker status", "list archive groups", "check archives", "archive stats", "GraphQL query", "GraphQL subscription", "opcua read", "aggregated messages", or any read-only/monitoring action on MonsterMQ.

MonsterMQ GraphQL Data Retrieval AI Skill

This skill provides instructions, query schemas, parameter reference, and code examples for reading data, monitoring status, fetching telemetry, querying historical archives, discovering storage backends, and streaming real-time updates from MonsterMQ via the GraphQL API.


[!IMPORTANT] Archive Group Isolation & Parameter Requirement: In MonsterMQ, topic values and historical messages are stored in isolated databases/tables per ArchiveGroup. When reading historical data (archivedMessages, aggregatedMessages), current values (currentValue, currentValues), or searching/browsing topics (searchTopics, browseTopics), you MUST specify the archiveGroup argument if your data is stored in a group other than "Default".

Recommended 2-Step Data Access Pattern:

  1. Discover Archives: Run archiveGroups to find which group covers your target MQTT topic filter.
  2. Fetch Data: Pass the discovered archiveGroup name (e.g. archiveGroup: "Industrial") into archivedMessages, aggregatedMessages, or currentValue.

1. Connection & Endpoint Overview

  • HTTP GraphQL Endpoint: http://localhost:4000/graphql (default port 4000)
  • WebSocket Endpoint (Subscriptions): ws://localhost:4000/graphql
  • HTTP Method: POST
  • Headers:
    http
    Content-Type: application/json
    Authorization: Bearer <jwt-token>   # Required if Auth.UserStoreType / User Management is enabled

2. Broker Status & Telemetry Queries

Current User (currentUser)

Returns authentication details for the requesting API connection.

graphql
query GetCurrentUser {
  currentUser {
    username
    isAdmin
  }
}
Broker Configuration (brokerConfig)

Returns the complete static configuration loaded from config.yaml.

graphql
query GetBrokerConfig {
  brokerConfig {
    nodeId
    version
    clustered
    tcpPort
    wsPort
    tcpsPort
    wssPort
    sessionStoreType
    retainedStoreType
    configStoreType
    userManagementEnabled
    anonymousEnabled
    mcpEnabled
    prometheusEnabled
    i3xEnabled
    graphqlEnabled
    metricsEnabled
  }
}
Node Metrics & Cluster Status (broker, brokers)

Query real-time throughput, active session counts, message bus rates, and node health.

graphql
# Current node or specific node status
query GetBroker($nodeId: String) {
  broker(nodeId: $nodeId) {
    nodeId
    version
    userManagementEnabled
    isLeader
    isCurrent
    enabledFeatures
    metrics {
      messagesIn
      messagesOut
      nodeSessionCount
      clusterSessionCount
      queuedMessagesCount
      subscriptionCount
      messageBusIn
      messageBusOut
      mqttClientIn
      mqttClientOut
      opcUaClientIn
      opcUaClientOut
      winCCOaClientIn
      timestamp
    }
  }
}

# All nodes in cluster
query GetAllBrokers {
  brokers {
    nodeId
    isLeader
    isCurrent
    enabledFeatures
    metrics {
      messagesIn
      messagesOut
      clusterSessionCount
    }
  }
}

3. Archive Groups & Storage Discovery Queries

Before querying historical messages or time-series aggregations, you should discover which Archive Groups, storage backends, database connections, and topic scopes are available in the broker.

Discover All Archive Groups (archiveGroups, archiveGroup)

Query all registered ArchiveGroups to inspect their topic filters, storage backends (archiveType, lastValType), connection status, and retention policies.

graphql
query GetArchiveGroups($enabled: Boolean) {
  archiveGroups(enabled: $enabled) {
    name
    enabled
    deployed
    topicFilter        # Match this filter against your topic of interest!
    retainedOnly
    lastValType        # MEMORY, HAZELCAST, POSTGRES, CRATEDB, MONGODB, SQLITE
    archiveType        # POSTGRES, CRATEDB, MONGODB, SQLITE, NONE
    databaseConnectionName
    payloadFormat
    lastValRetention
    archiveRetention
    purgeInterval
    connectionStatus {
      nodeId
      messageArchive
      lastValueStore
      error
    }
  }
}

query GetSingleArchiveGroup($name: String!) {
  archiveGroup(name: $name) {
    name
    enabled
    topicFilter
    archiveType
    lastValType
    databaseConnectionName
    archiveRetention
  }
}
Archive Volume & Daily Statistics (archiveStats)

Fetch storage statistics for an archive group, including the earliest recorded timestamp (minTimestamp) and daily historical message counts (dailyCounts).

graphql
query GetArchiveStats($archiveGroup: String!, $startTime: String, $endTime: String) {
  archiveStats(
    archiveGroup: $archiveGroup,
    startTime: $startTime,
    endTime: $endTime
  ) {
    minTimestamp
    dailyCounts {
      date
      count
    }
  }
}
Database Connections (databaseConnections, databaseConnectionNames, databaseConnection)

Inspect configured database connections backing the message archives (PostgreSQL, MongoDB, SQLite).

graphql
query GetDatabaseConnections {
  databaseConnections {
    name
    type
    url
    database
    schema
  }
  databaseConnectionNames(type: POSTGRES)
}

4. Topic Values & Live Telemetry Queries

Current Topic Value (currentValue)

Retrieves the most recent message for an exact topic from the LastValueStore.

  • topic: Exact topic string (no wildcards allowed).
  • format: JSON or BINARY (base64).
  • archiveGroup: Name of the ArchiveGroup containing the last value store (default: "Default").
graphql
query GetCurrentValue($topic: String!, $archiveGroup: String = "Default") {
  currentValue(topic: $topic, format: JSON, archiveGroup: $archiveGroup) {
    topic
    payload
    format
    timestamp
    qos
    retained
  }
}
Multi-Topic Values (currentValues)

Retrieves the most recent messages matching an MQTT wildcard filter.

  • topicFilter: MQTT filter with + (single-level) or # (multi-level). E.g. "factory/+/temperature".
  • limit: Max records to return (default: 100).
  • archiveGroup: Target ArchiveGroup name.
graphql
query GetCurrentValues($filter: String!, $archiveGroup: String = "Default", $limit: Int = 100) {
  currentValues(topicFilter: $filter, format: JSON, limit: $limit, archiveGroup: $archiveGroup) {
    topic
    payload
    timestamp
    qos
  }
}
Topic Discovery & Hierarchical Browsing (searchTopics, browseTopics)

Note: Topic search and browsing operate on the LastValueStore of the specified archiveGroup.

graphql
# Search topics using SQL LIKE pattern (% and _)
query SearchTopics($pattern: String!, $archiveGroup: String = "Default") {
  searchTopics(pattern: $pattern, limit: 50, archiveGroup: $archiveGroup)
}

# Browse topic hierarchy one level down
query BrowseTopics($topic: String!, $archiveGroup: String = "Default") {
  browseTopics(topic: $topic, archiveGroup: $archiveGroup) {
    name
    hasChildren
    messageCount
  }
}
Show full SKILL.md (256 more words)Show less
Retained Messages (retainedMessage, retainedMessages)

Query messages published with retain=true.

graphql
query GetRetainedMessages($filter: String) {
  retainedMessages(topicFilter: $filter, format: JSON, limit: 100) {
    topic
    payload
    timestamp
    qos
  }
}

5. Historical Message Archives & Analytics Queries

[!IMPORTANT] Always specify archiveGroup when querying history. Different archive groups can be backed by different databases (e.g. PostgreSQL vs CrateDB vs MongoDB).

Raw Message History (archivedMessages)

Queries historical MQTT messages matching a time window and topic filter.

  • topicFilter: MQTT wildcard topic filter (e.g. "sensors/#").
  • archiveGroup: Name of the target ArchiveGroup (default "Default").
  • startTime / endTime: ISO 8601 strings (e.g. "2026-07-28T00:00:00Z").
  • includeTopic: Boolean (set to false for performance when querying a single topic).
graphql
query GetArchivedMessages(
  $topicFilter: String!,
  $archiveGroup: String = "Default",
  $startTime: String,
  $endTime: String,
  $limit: Int = 100
) {
  archivedMessages(
    topicFilter: $topicFilter,
    archiveGroup: $archiveGroup,
    startTime: $startTime,
    endTime: $endTime,
    format: JSON,
    limit: $limit
  ) {
    topic
    payload
    timestamp
    qos
  }
}
Time-Series Aggregations (aggregatedMessages)

Performs database-level bucketing and aggregation across archived messages.

  • topics: Array of exact topic strings.
  • archiveGroup: ArchiveGroup to perform aggregation on (default "Default").
  • interval: SECOND_1, SECOND_5, SECOND_10, MINUTE_1, MINUTE_5, MINUTE_15, HOUR_1, DAY_1.
  • functions: AVG, MIN, MAX, SUM, COUNT, FIRST, LAST.
  • fields: Optional JSON path fields (e.g. ["temperature", "humidity"]).
graphql
query GetAggregatedMessages(
  $topics: [String!]!,
  $archiveGroup: String = "Default",
  $interval: AggregationInterval!,
  $startTime: String!,
  $endTime: String!
) {
  aggregatedMessages(
    topics: $topics,
    archiveGroup: $archiveGroup,
    interval: $interval,
    startTime: $startTime,
    endTime: $endTime,
    functions: [AVG, MAX, MIN],
    fields: ["value"]
  ) {
    timestamps
    topics {
      topic
      field
      function
      values
    }
  }
}

6. Client Sessions & System Logs

Active Sessions (sessions, session)
graphql
query GetSessions($connected: Boolean, $clientIdFilter: String) {
  sessions(connected: $connected, clientId: $clientIdFilter) {
    clientId
    nodeId
    connected
    cleanSession
    subscriptions {
      topicFilter
      qos
    }
    metrics {
      messagesIn
      messagesOut
    }
  }
}

query GetSingleSession($clientId: String!) {
  session(clientId: $clientId) {
    clientId
    nodeId
    connected
    cleanSession
    keepAlive
    lastConnectedTime
  }
}
System Logs (systemLogs)

Inspect in-memory circular log buffer with filtering.

graphql
query GetSystemLogs($lastMinutes: Int, $level: [String!], $message: String) {
  systemLogs(
    lastMinutes: $lastMinutes,
    level: $level,
    message: $message,
    limit: 50,
    orderByTime: DESC
  ) {
    timestamp
    level
    logger
    message
    node
    sourceClass
    sourceMethod
  }
}

7. Device Connector & OPC UA Queries

Device Configurations & Runtime Status

Fetch active bridge and connector configurations:

  • mqttClientConfigs, opcUaClientConfigs, plc4xClientConfigs, winccOaClientConfigs, winccUaClientConfigs
  • kafkaClientConfigs, natsClientConfigs, redisClientConfigs, telegramClientConfigs, neo4jClientConfigs
  • opcUaServerConfigs, jdbcLoggerConfigs, influxDbLoggerConfigs, timeBaseLoggerConfigs, sparkplugBDecoderConfigs
graphql
query GetDeviceConfigs {
  opcUaClientConfigs {
    name
    endpointUrl
    enabled
    nodeId
    connectState
    subscriptions {
      nodeId
      mqttTopic
    }
  }
  plc4xClientConfigs {
    name
    connectionString
    enabled
    connectState
  }
}
Live OPC UA Browsing & Reading (opcUaBrowse, opcUaRead)
graphql
# Browse OPC UA address space
query BrowseOpcUaNode($name: String!, $nodePath: String) {
  opcUaBrowse(name: $name, nodePath: $nodePath) {
    nodeId
    displayName
    browseName
    nodeClass
    hasChildren
  }
}

# Read OPC UA tag value directly
query ReadOpcUaNode($name: String!, $nodePath: String!) {
  opcUaRead(name: $name, nodePath: $nodePath) {
    value
    statusCode
    serverTimestamp
  }
}

8. Flow Engine, AI Agents & Topic Schemas

Flow Engine Status (flowClasses, flowInstances)
graphql
query GetFlows {
  flowClasses {
    name
    namespace
    version
    description
  }
  flowInstances {
    name
    flowClassId
    nodeId
    enabled
    status {
      running
      lastExecution
      executionCount
      errorCount
      lastError
    }
  }
}
AI Agents (agents, agent)
graphql
query GetAgents {
  agents {
    name
    namespace
    nodeId
    enabled
    provider
    model
    inputTopics
    outputTopics
  }
}
Topic Schemas (topicSchemas, topicSchema)
graphql
query GetTopicSchemas {
  topicSchemas {
    topicFilter
    jsonSchema
    description
  }
}

9. Real-Time GraphQL Subscriptions

MonsterMQ supports WebSocket subscriptions for live streaming data (ws://localhost:4000/graphql).

Real-Time Topic Updates (topicUpdates)
graphql
subscription OnTopicUpdates($filters: [String!]!) {
  topicUpdates(topicFilters: $filters, format: JSON) {
    topic
    payload
    format
    timestamp
    qos
    retained
    clientId
  }
}
Bulk Batch Updates (topicUpdatesBulk)
graphql
subscription OnTopicUpdatesBulk($filters: [String!]!) {
  topicUpdatesBulk(topicFilters: $filters, format: JSON, timeoutMs: 500, maxSize: 50) {
    count
    timestamp
    updates {
      topic
      payload
      timestamp
    }
  }
}
Real-Time System Log Streaming (systemLogs)
graphql
subscription OnSystemLogs($level: [String!]) {
  systemLogs(level: $level) {
    timestamp
    level
    logger
    message
    node
  }
}

10. End-to-End Client Implementation Example

Complete Python Archive Discovery & Historical Query Pattern
python
import requests

GRAPHQL_URL = "http://localhost:4000/graphql"
headers = {"Content-Type": "application/json"}

# Step 1: Discover available Archive Groups & match target topic filter
archive_query = """
query DiscoverArchives {
  archiveGroups(enabled: true) {
    name
    topicFilter
    archiveType
    lastValType
  }
}
"""
res = requests.post(GRAPHQL_URL, json={"query": archive_query}, headers=headers).json()
groups = res["data"]["archiveGroups"]
print("Available Archive Groups:")
for g in groups:
    print(f" - Group: {g['name']} | Filters: {g['topicFilter']} | Store: {g['archiveType']}")

# Assume target topic "opcua/plc1/temperature" matches group "Industrial"
target_group = "Industrial"

# Step 2: Query historical messages specifying the discovered archive group
history_query = """
query GetHistory($topicFilter: String!, $archiveGroup: String!) {
  archivedMessages(
    topicFilter: $topicFilter,
    archiveGroup: $archiveGroup,
    limit: 50
  ) {
    topic
    payload
    timestamp
  }
}
"""
params = {
    "topicFilter": "opcua/plc1/temperature",
    "archiveGroup": target_group
}

history_res = requests.post(GRAPHQL_URL, json={"query": history_query, "variables": params}, headers=headers).json()
print("Historical Messages:", history_res["data"]["archivedMessages"])
Curl Example with ArchiveGroup Argument
bash
curl -X POST http://localhost:4000/graphql \
  -H "Content-Type: application/json" \
  -d '{
    "query": "query GetHistory($filter: String!, $group: String!) { archivedMessages(topicFilter: $filter, archiveGroup: $group, limit: 10) { topic payload timestamp } }",
    "variables": {
      "filter": "telemetry/#",
      "group": "Industrial"
    }
  }'

© 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-graphql-data of vogler75/monster-mq.

Open the folder on GitHubat commit 5920123

Compare with similar skills

Monstermq Graphql Data 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 Graphql Data compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Monstermq Graphql Data this skillvogler75/monster-mq143—~4kAutomated safety check: PassGPL-3.0
Nodejs Backend Patternsever-works/ever-works16218 repos~4kAutomated safety check: PassAGPL-3.0
API DesignerJeffallan/claude-skills12k1 repos~2kAutomated safety check: PassMIT
GraphQL Operations with CodegenChrisWiles/claude-code-showcase6.1k3 repos~1.5kAutomated safety check: PassNone
API Design Principlesjh941213/my-cc-harness12618 repos~3.4kAutomated safety check: PassNone
API And Interface Designdzhalaevd/Donatello1358 repos~2.6kAutomated safety check: PassApache-2.0

Similar skills

  • Nodejs Backend Patterns

    ever-works/ever-works

    Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.

    162 GitHub starsUsed in 18 repos~4k tokens
    Backend & APIsAuto-check passed
  • API Designer

    Jeffallan/claude-skills

    Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.

    12k GitHub starsUsed in 1 repo~2k tokens
    Backend & APIsAuto-check passed
  • GraphQL Operations with Codegen

    ChrisWiles/claude-code-showcase

    Sets the rules for writing GraphQL queries and mutations in .gql files, running codegen, and using generated Apollo hooks with proper error and loading handling.

    6.1k GitHub starsUsed in 3 repos~1.5k tokens
    Backend & APIsAuto-check passed
  • API Design Principles

    jh941213/my-cc-harness

    REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.

    126 GitHub starsUsed in 18 repos~3.4k tokens
    Backend & APIsAuto-check passed
  • API And Interface Design

    dzhalaevd/Donatello

    Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.

    135 GitHub starsUsed in 8 repos~2.6k tokens
    Backend & APIsAuto-check passed
  • Registers a new syncable entity in three NestJS modules and adds its service and GraphQL resolver layers when contributing to the Twenty server.

    58k GitHub stars~2.9k tokensUpdated today
    Backend & APIsAuto-check passed

More from vogler75/monster-mq

  • Monstermq Broker Config

    vogler75/monster-mq

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

    143 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • 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 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

Works with

Categories

Questions about Monstermq Graphql Data

What does Monstermq Graphql Data do?

Guide for querying MonsterMQ broker data, telemetry, metrics, sessions, live topic values, retained messages, historical message archives, time-series aggregations, ArchiveGroups, OPC UA node…. Monstermq Graphql Data is an agent skill from 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 browsing, topic schemas, flow engine statuses, AI agent conversations, and real-time GraphQL subscriptions.

When should I use Monstermq Graphql Data?

Monstermq Graphql Data fits situations like: you need to fetch data; monitor broker health; read topic values; query historical data.

How do I install Monstermq Graphql Data in Claude Code?

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

How do I install Monstermq Graphql Data in Codex?

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

Can I use Monstermq Graphql Data 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-graphql-data -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-graphql-data, .gemini/skills/monstermq-graphql-data, .github/skills/monstermq-graphql-data and .opencode/skills/monstermq-graphql-data in your project.

What does Monstermq Graphql Data need to run?

Going by SKILL.md and its folder, Monstermq Graphql Data needs the command-line tools its instructions call (curl).

Does Monstermq Graphql Data access the network?

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

Is Monstermq Graphql Data 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 Graphql Data use?

Monstermq Graphql Data 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 Graphql Data use?

About 4k tokens (SKILL.md is roughly 16k 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 Graphql Data?

Skills that share tags, products or a category with Monstermq Graphql Data: Nodejs Backend Patterns (ever-works/ever-works, 162 stars), API Designer (Jeffallan/claude-skills, 12k stars), GraphQL Operations with Codegen (ChrisWiles/claude-code-showcase, 6.1k stars) and API Design Principles (jh941213/my-cc-harness, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Monstermq Graphql Data?

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 9, 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.