Name: mx-toolbox
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mx-toolbox

Mx Toolbox integration. Manage Organizations. Use when the user wants to interact with Mx Toolbox 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/mx-toolbox/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 body is a well-structured, actionable CLI integration guide with explicit connection-state feedback loops and concrete commands throughout. Its main weaknesses are mild marketing verbosity in the intro and a couple of structural loose ends (a 'Step 2' reference with no matching heading, slight section redundancy).

Suggestions

Trim the marketing prose: drop 'It helps Mendix developers automate tasks, improve code quality, and manage their projects more efficiently' and 'so you can focus on the integration logic rather than auth plumbing' — keep only the operational facts.

Resolve the dangling 'skip to Step 2' reference by adding explicit Step 1 / Step 2 headings, or rephrase to 'proceed to Searching for actions'.

Add at least one Mx Toolbox-specific action example (e.g., a real `membrane action run` invocation for listing or managing Organizations) so the actionability guidance covers a concrete common case.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clean command blocks, but the marketing intro ('It helps Mendix developers automate tasks, improve code quality...') and the aside 'so you can focus on the integration logic rather than auth plumbing' are unnecessary padding.	3 / 5
Actionability	Concrete, copy-pasteable CLI commands cover install, auth, connection, action discovery, running, and proxying, with a flags table; the gap is that no Mx Toolbox-specific action example with real parameters is shown.	4 / 5
Workflow Clarity	A clear install→login→connect→poll→search→run sequence exists with an explicit state-feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/ERROR), though the dangling 'skip to Step 2' reference (no Step 2 heading) and lack of post-action verification are minor gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references and nothing that clearly belongs in a separate file; minor redundancy between 'Searching for actions' and 'Popular actions' keeps it just below ideal.	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 is functional — it states what the skill does and when to use it with an explicit trigger clause — but it is thin: only one concrete action is named and the trigger keywords are narrow. It would benefit from enumerating the actual capability categories and richer trigger phrasing.

Suggestions

Enumerate concrete capabilities beyond 'Manage Organizations' (e.g., 'inspect File and Folder metadata, run conversions, manage Organizations') so specificity and trigger coverage reflect the body's overview.

Add natural trigger synonyms users would say, such as 'Mendix', 'Mx Toolbox file/folder metadata', or 'Mx Toolbox conversion', to broaden activation.

Sharpen the 'when' clause with concrete triggers, e.g. 'Use when the user wants to read or manage Mx Toolbox organizations, files, folders, or run conversions.'

Dimension	Reasoning	Score
Specificity	It names the domain ('Mx Toolbox integration') and one concrete action ('Manage Organizations'), but coverage is not comprehensive — the body reveals File/Folder/Conversion/Metadata capabilities never surfaced here.	3 / 5
Completeness	Both a 'what' ('Mx Toolbox integration. Manage Organizations.') and an explicit 'when' ('Use when the user wants to interact with Mx Toolbox data') are present, though both could be sharper and more specific.	4 / 5
Trigger Term Quality	'Mx Toolbox' and 'interact with Mx Toolbox data' are relevant keywords, but common variations users might say (Mendix, file, folder, metadata, conversion) are absent.	3 / 5
Distinctiveness Conflict Risk	'Mx Toolbox' is a named product niche with distinct triggers, but the name overlaps the well-known unrelated MxToolbox DNS/email lookup service, creating minor conflict risk.	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/mx-toolbox/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.