Name: robomq
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

robomq

RoboMQ integration. Manage data, records, and automate workflows. Use when the user wants to interact with RoboMQ data.

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/robomq/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable with executable commands and a well-instrumented connection state machine, supported by clean section structure. Its main weaknesses are a padded marketing-style intro, unexplained overview bullets, a dangling step reference, and a few examples that still need placeholder substitution.

Suggestions

Cut the opening "RoboMQ is an open-source integration platform..." paragraph and the bare Overview bullet list, or replace them with a one-line purpose statement; Claude does not need the product primer.

Fix the dangling step reference: label the connection sub-steps consistently (e.g. Step 1 ensure, Step 2 search/run actions) so "skip to Step 2" resolves, instead of the lone "1b".

Provide one fully-substituted runnable example for `membrane action run` with realistic values, or note explicitly which placeholders must be replaced before execution.

Dimension	Reasoning	Score
Conciseness	The opening paragraph ("RoboMQ is an open-source integration platform that facilitates communication...") and the unexplained Overview bullets (Channel, Message, Integration, API Key) are padding Claude does not need, while the command-driven sections are efficient, matching the anchor for mostly efficient content with some unnecessary explanation that could be tightened.	3 / 5
Actionability	Concrete, copy-pasteable commands appear throughout (npm install, membrane login, connection ensure, action run) plus a full flag table for proxy requests; it falls just short of fully copy-paste-ready because several examples require substituting placeholders like CONNECTION_ID and QUERY before they run.	4 / 5
Workflow Clarity	The connection flow is sequenced with a real validation checkpoint via state polling (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a re-poll feedback loop, but a dangling reference to "Step 2" with no labeled Step 2 (and a lone "1b") leaves a minor gap, fitting the anchor for a clear sequence with most checkpoints present.	4 / 5
Progressive Disclosure	The body is well organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) in a single self-contained file with no nested references and no need for separate files; minor organization gaps (the proxy flag table and clientAction field reference could live in a reference file) keep it just below the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description successfully pairs a what-and-when structure around a distinct named product, but its action verbs are generic and it offers only a single trigger phrase. Tightening the verbs and adding a couple of natural trigger terms would lift it toward the top anchors.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete operations a user would request, e.g. "Search records, run workflows, send messages, and proxy API requests."

Add a few natural trigger terms beyond "interact with RoboMQ data", such as "Use when the user mentions RoboMQ channels, messages, integrations, or API keys."

Keep the explicit "Use when..." clause but tie it to the specific entities already listed in the Overview (Channel, Message, Integration) to sharpen the trigger.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus three actions, but the verbs are generic ("manage") rather than concrete operations like extract, fill, or merge, so it sits at the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with RoboMQ data"); the trigger is present and explicit but could be more specific with concrete trigger phrases, fitting the anchor where both are present yet the when could be sharper.	4 / 5
Trigger Term Quality	The only trigger phrase is "Use when the user wants to interact with RoboMQ data"; it supplies a relevant keyword (RoboMQ, data) but lacks common variations or synonyms users might say, matching the anchor with some relevant keywords but missing natural variations.	3 / 5
Distinctiveness Conflict Risk	"RoboMQ integration" anchors a clear product-specific niche with low conflict risk, but the generic "manage data, records" phrasing leaves minor overlap risk with other data-integration skills, so it is mostly distinct rather than fully minimal-conflict.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/robomq/SKILL.md
Commit: f484c82

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.