Name: rocket-chat
Rating: 61.6 (1 reviews)
Author: membranedev

rocket-chat

Rocket Chat integration. Manage Users, Rooms, Teams, Integrations. Use when the user wants to interact with Rocket Chat data.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/rocket-chat/SKILL.md

Quality

Content

75%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.

A well-structured, highly actionable integration guide with executable commands, clear state-based workflow branching, and a useful feedback loop. The main weakness is conciseness: an unnecessary introductory paragraph and a few inlined sections that padding could be trimmed or moved to a reference file.

Suggestions

Remove or compress the opening paragraph explaining what Rocket.Chat is and who uses it; Claude already knows this.

Move the detailed proxy flags table and the clientAction field breakdown into a separate reference file and link to it from the body.

Add an explicit post-action verification step (e.g. check the response `output`/`error` field and retry on failure) to strengthen the workflow's validation loop.

Dimension	Reasoning	Score
Conciseness	Mostly efficient commands and tables, but the opening paragraph explaining what Rocket.Chat is ("similar to Slack or Microsoft Teams... used by businesses, educational institutions") and the verbose clientAction breakdown pad content Claude largely already knows.	3 / 5
Actionability	Provides copy-paste-ready, executable commands covering the common cases (install, login, connection ensure, action list/run with JSON input, request proxy) plus a flags table, matching the fully-executable anchor.	5 / 5
Workflow Clarity	Clear multi-step sequence (install → login → ensure → wait → search → run) with explicit state-based branching and a re-poll feedback loop for CLIENT_ACTION_REQUIRED, but lacks an explicit success-verification checkpoint after running an action.	4 / 5
Progressive Disclosure	Single-file skill with well-organized flat sections and no nested references, but the long inlined proxy flags table and clientAction breakdown could live in a separate reference file, and there are no external references to signal.	4 / 5
	Total	16 / 20 Passed

Description

71%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.

A solid description that names the domain and four managed entities with an explicit trigger clause, clearly distinct from other skills. Its main weaknesses are the single generic verb "Manage" and thin natural-language trigger coverage with a slightly awkward "when" phrasing.

Suggestions

Replace the generic verb "Manage" with specific concrete actions (e.g. "Create, update, and list Users, Rooms, Teams, and Integrations").

Broaden trigger terms to phrases users naturally say, such as "channels", "direct messages", "send a Rocket Chat message", and "rocket.chat".

Tighten the "when" clause to concrete triggers (e.g. "Use when the user wants to send messages, manage channels, or administer Rocket Chat users/teams").

Dimension	Reasoning	Score
Specificity	Names the domain plus four concrete action objects ("Manage Users, Rooms, Teams, Integrations"), giving breadth beyond 1-2 actions, but the single generic verb "Manage" keeps it just below comprehensive.	4 / 5
Completeness	Explicitly answers both "what" (manage Users, Rooms, Teams, Integrations) and "when" ("Use when the user wants to interact with Rocket Chat data"), with the "when" present and concrete but still generic enough to fall short of the level-5 anchor.	4 / 5
Trigger Term Quality	Contains the natural product keyword "Rocket Chat" and an explicit trigger clause, but lacks common variations users would say ("rocket.chat", "channels", "DM", "send a message") and the phrasing "interact with Rocket Chat data" is not phrased the way users naturally ask.	3 / 5
Distinctiveness Conflict Risk	"Rocket Chat" is a distinct, named product, so the skill occupies a clear niche with minimal risk of triggering for the wrong skill.	5 / 5
	Total	16 / 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/rocket-chat/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.