Name: mx-technologies
Rating: 60 (1 reviews)
Author: membranedev

mx-technologies

MX Technologies integration. Manage Users, Organizations, Pipelines, Goals, Filters, Files and more. Use when the user wants to interact with MX Technologies data.

Quality

70%

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/mx-technologies/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.

A well-structured, actionable CLI integration guide with a clear workflow and validation checkpoints. Its main weakness is an unnecessary introductory/marketing paragraph and minor verbosity that slightly inflate token cost.

Suggestions

Cut or condense the opening paragraph explaining what MX Technologies is and who uses it; Claude does not need the market context.

Tighten phrases like "so you can focus on the integration logic rather than auth plumbing" to factual statements only.

Make the step numbering consistent (define Step 1 and Step 2 explicitly) so cross-references like "skip to Step 2" resolve cleanly.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands and examples, but the opening marketing paragraph ("MX Technologies provides APIs that allow developers to connect... gain insights into their spending habits") and phrasing like "so you can focus on the integration logic rather than auth plumbing" are unnecessary padding Claude does not need.	3 / 5
Actionability	Provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request proxy) plus a flag table; placeholders like <actionId> and CONNECTION_ID are appropriate for a CLI skill but keep it just short of fully copy-paste ready.	4 / 5
Workflow Clarity	A clear sequenced workflow (install → authenticate → connect → poll until READY → search → run → proxy) with state-based checkpoints and a feedback loop (re-poll after CLIENT_ACTION_REQUIRED), though step numbering is slightly inconsistent ("1b", "Step 2" referenced without a clear Step 1/2).	4 / 5
Progressive Disclosure	No bundle files exist, but the body is well-organized into clear sections (Working with, Install, Authentication, Connecting, Searching, Popular actions, Proxy requests, Best practices); at ~140 lines it is slightly long for a single file but appropriately sectioned.	4 / 5
	Total	15 / 20 Passed

Description

73%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 third-person description that pairs a concrete entity list with an explicit "Use when..." trigger, anchored to a distinctive brand. Its main weakness is the generic verb "Manage" and a single trigger phrase rather than varied concrete triggers.

Suggestions

Replace the generic verb "Manage" with specific concrete actions per entity (e.g., "Create and update Users, list Organizations, run Pipelines, track Goals").

Expand the trigger with natural variations users would actually say (e.g., "Use when the user wants to query MX transactions, manage members, or pull financial data").

Dimension	Reasoning	Score
Specificity	Names the domain and lists six concrete entities ("Users, Organizations, Pipelines, Goals, Filters, Files") but uses a single generic action verb ("Manage") rather than several distinct concrete actions, leaving it below the "several specific actions" anchor.	3 / 5
Completeness	Both "what" (manage Users, Organizations, Pipelines, Goals, Filters, Files) and "when" ("Use when the user wants to interact with MX Technologies data") are explicitly present, but the trigger is a single phrase rather than multiple concrete trigger variations.	4 / 5
Trigger Term Quality	The trigger phrase "Use when the user wants to interact with MX Technologies data" plus the named entity keywords (Users, Organizations, Pipelines, Goals, Filters, Files) give good natural coverage; a few synonyms or variations are missing.	4 / 5
Distinctiveness Conflict Risk	"MX Technologies" is a distinct named brand niche with clear, unambiguous triggers; minimal risk of conflicting with other skills.	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/mx-technologies/SKILL.md
Commit: f484c82

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