Name: loopmessage
Rating: 53.6 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

loopmessage

LoopMessage integration. Manage Users, Organizations. Use when the user wants to interact with LoopMessage data.

Quality

60%

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/loopmessage/SKILL.md

Quality

Content

63%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 body is actionable and well-sequenced for the connection workflow, with concrete CLI commands and explicit state-checkpoint handling. Its main weaknesses are a padded marketing intro, an inlined flag/state reference that should live in a separate file (no bundle exists), and unresolved command placeholders.

Suggestions

Delete the opening marketing paragraph ('LoopMessage is a customer engagement platform...') and the filler line 'Use action names and parameters as needed.' — Claude does not need them.

Move the proxy flag-option table and the clientAction state reference into a references/ file (e.g. references/connection-states.md) and link to it from the body, so SKILL.md stays a lean overview.

Resolve or explain the placeholder tokens (CONNECTION_ID, <actionId>, <agentType>) with a concrete example of obtaining each, so commands are copy-paste ready for the common case.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with copy-paste commands, but includes some padding Claude does not need (a marketing paragraph on what LoopMessage is, 'Use action names and parameters as needed', and the explanatory Membrane-auth prose), matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'; not 4 because the opening overview paragraph and several restated reminders are clearly trimmable.	3 / 5
Actionability	Commands are concrete and mostly executable (install, login, connection ensure/get with --wait, action list/run with --input, request with flags), with only minor gaps such as unresolved placeholders (CONNECTION_ID, <actionId>, <agentType>), matching the score-4 anchor; not 5 because placeholders are not concretely resolved for the common cases.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state handling and polling checkpoints (READY skip to Step 2, BUILDING poll with --wait, CLIENT_ACTION_REQUIRED actions, error states), matching 'Clear sequence with most checkpoints present'; not 5 because some checkpoints are implicit (no explicit re-validate step after a CLIENT_ACTION_REQUIRED completion beyond 'poll again').	4 / 5
Progressive Disclosure	There is reasonable section structure, but no bundle files exist (references/scripts/assets absent) while the body inlines a full flag-option table and substantial connector-state reference material that reads like content that should live in a separate reference, matching 'Some structure but could be better organized; references present but not clearly signaled; content that should be separate is inline'; not 4 because the inlined proxy-flags table and clientAction reference are not split out.	3 / 5
	Total	14 / 20 Passed

Description

57%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 identifies the product and gives an explicit (if generic) use-when clause, so activation basics are present. It is weak on specificity and trigger-term coverage, naming only two coarse entities with no concrete operations or natural synonyms.

Suggestions

Replace the vague 'Manage Users, Organizations' with concrete actions (e.g., 'create and update Users, manage Organizations, send and list Messages, query Conversations').

Broaden the trigger clause with natural terms users would say, e.g. 'Use when the user wants to send or read LoopMessage messages, manage LoopMessage users or organizations, or query conversation history'.

Add natural keywords/synonyms (Messages, Conversations, send a message, message history) to improve activation match quality.

Dimension	Reasoning	Score
Specificity	It names the domain (LoopMessage integration) and a couple of coarse entities ('Manage Users, Organizations'), but the actions are minimal and generic with no concrete operations listed, matching the score-2 anchor ('Names the domain but actions are minimal or generic').	2 / 5
Completeness	It states a clear 'what' (LoopMessage integration, manage Users/Organizations) and an explicit 'when' ('Use when the user wants to interact with LoopMessage data'), matching the 'has both what and when; when could be more explicit or specific' anchor; not 5 because the when-clause is generic and not tied to concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the natural product name 'LoopMessage' and the trigger phrase 'interact with LoopMessage data', but lacks common synonyms or variations users might say, landing on the 'Some relevant keywords but missing common variations or synonyms' anchor; not a 4 because coverage is thin rather than merely 'a few terms missing'.	3 / 5
Distinctiveness Conflict Risk	The LoopMessage product name gives it a clear niche with mostly distinct triggers and only minor overlap risk against other Membrane integration skills, matching the score-4 anchor; not 5 because the generic 'Manage Users, Organizations' could overlap with other user-management skills.	4 / 5
	Total	13 / 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/loopmessage/SKILL.md
Commit: f484c82

Reviewed: 6 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.