Name: maintainx
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

maintainx

MaintainX integration. Manage Organizations. Use when the user wants to interact with MaintainX data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/maintainx/SKILL.md

Quality

Content

61%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 skill is highly actionable with concrete CLI commands and a solid connection-state workflow, but it carries some verbosity and lacks validation guidance for the destructive action and proxy operations it enables. Adding verification checkpoints would meaningfully improve workflow clarity.

Suggestions

Add a validation/verification checkpoint after running actions or proxy requests (e.g., check the response `output`/status and confirm the intended change before proceeding) to lift workflow_clarity above the destructive-operation cap.

Label the referenced "Step 2" explicitly (e.g., a numbered "## 2. Search and run actions" section) so the connection-to-action flow is unambiguous.

Trim marketing language and the duplicated action-list command, and consider moving the entity overview or flags table into a reference file to tighten conciseness and improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but includes marketing fluff ("focus on the integration logic rather than auth plumbing"), a redundant repeated action-list command, and a padded entity list that could be tightened, matching the score-3 anchor 'Mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands and a clear flags table, but uses generic placeholders (CONNECTION_ID, QUERY) and shows no real MaintainX-specific action example beyond {"key": "value"}, fitting score-4 'concrete code or commands with minor gaps'.	4 / 5
Workflow Clarity	The connection flow has an explicit state-polling feedback loop, but destructive action/proxy runs lack any validation or verification step and "skip to Step 2" references a Step 2 that is never labeled, so the destructive-operation cap of 3 applies.	3 / 5
Progressive Disclosure	Content is well-organized into clear sections with no nested references and no problematic inlining, but at ~180 lines with no bundle files it relies on a single monolithic file, matching score-4 'Good structure; most content appropriately placed; minor organization gaps'.	4 / 5
	Total	14 / 20 Passed

Description

61%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 has an explicit trigger clause and is clearly tied to the distinct MaintainX product, but its capability list is thin and generic. Strengthening the action verbs would lift specificity and trigger quality.

Suggestions

Replace the generic "Manage Organizations" with several concrete capabilities (e.g., create work orders, track assets, log meter readings, manage locations and parts) so the what is specific.

Add natural trigger synonyms users actually say (e.g., "work orders", "preventive maintenance", "CMMS") alongside "MaintainX" to improve trigger term coverage.

Keep the explicit "Use when..." clause but pair it with the more specific action list to fully satisfy both what and when at score-5 level.

Dimension	Reasoning	Score
Specificity	The description names the MaintainX domain but offers only one generic action ("Manage Organizations"), matching the score-2 anchor 'Names the domain but actions are minimal or generic' better than the two-action score-3 example.	2 / 5
Completeness	It states a (vague) what ("MaintainX integration. Manage Organizations.") and an explicit when ("Use when the user wants to interact with MaintainX data"), matching score-4 where both are present but the what could be more specific; the present 'Use when...' clause avoids the score-3 cap.	4 / 5
Trigger Term Quality	"MaintainX" and "Organizations" are relevant keywords a user might say, but coverage lacks common variations or synonyms, fitting the score-3 anchor 'Some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The skill is bound to a uniquely named product (MaintainX) with a product-specific trigger, giving it a clear niche with minimal conflict risk per the score-5 anchor.	5 / 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/maintainx/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.