Name: mendix
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mendix

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

Quality

67%

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

Quality

Content

68%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 highly actionable with concrete, executable commands and a solid connection workflow, but it loses conciseness to marketing prose and omits validation checkpoints for the potentially destructive action/proxy operations.

Suggestions

Trim the opening Mendix marketing paragraph and the 'focus on integration logic' phrasing so the body assumes Claude's competence.

Add an explicit verify/validate step after running actions or proxy requests (e.g., inspect the `output` field, confirm status before destructive methods) to lift workflow clarity above the destructive-operations cap.

Consider moving the proxy flag reference table and action inputSchema/outputSchema detail into a separate REFERENCE.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the opening paragraph ('accelerate their digital transformation initiatives') and phrases like 'so you can focus on the integration logic rather than auth plumbing' are marketing-flavored padding Claude does not need, fitting 'mostly efficient but some unnecessary explanation'.	3 / 5
Actionability	Provides copy-paste-ready commands for every common case (install, login, connection ensure, action list/run, request) plus a thorough proxy flag table, fully executable with specific examples covering the main workflows.	5 / 5
Workflow Clarity	The connection setup has a clear state-driven sequence with a poll-and-retry feedback loop, but the action-run and proxy workflows (which can issue POST/PUT/DELETE) lack any validation or verification step, triggering the destructive/batch cap at 3.	3 / 5
Progressive Disclosure	No bundle files exist, so navigation is a single well-sectioned document with clear ## headers and appropriately placed inline content; not a 5 only because it exceeds 50 lines with some material (proxy flag table, schema details) that could live in separate reference files.	4 / 5
	Total	15 / 20 Passed

Description

66%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 cleanly answers both what and when and is clearly anchored to the distinct Mendix niche, but its action list is generic and it offers only one trigger phrasing without synonyms.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Mendix-specific capabilities (e.g., 'query app data, manage domain model records, trigger microflows') to lift specificity.

Broaden the trigger clause with natural variations users might say (e.g., 'Mendix apps, Mendix data, Mendix APIs, .mpr projects') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Mendix) and a couple of actions ('Manage data, records, and automate workflows'), but the actions are fairly generic rather than concretely specified, matching the '1-2 concrete actions, not comprehensive' anchor; not a 4 because no specific capabilities are enumerated.	3 / 5
Completeness	Explicitly states both what ('Manage data, records, and automate workflows') and when ('Use when the user wants to interact with Mendix data'); the 'when' is present but could be more specific, matching the 'both what and when, when could be more explicit' anchor rather than the fully concrete 5.	4 / 5
Trigger Term Quality	Includes the relevant keyword 'Mendix' and the phrase 'interact with Mendix data', but offers only a single trigger phrasing with no synonyms or variations, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Names the specific product Mendix and ties triggers to 'Mendix data', giving it a clear niche with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	15 / 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/mendix/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.