Name: mirantis
Rating: 56.8 (1 reviews)
Author: membranedev

mirantis

Mirantis integration. Manage data, records, and automate workflows. Use when the user wants to interact with Mirantis 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/mirantis/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 content is highly actionable with concrete CLI commands and a well-sequenced, state-aware connection workflow. It is held back by a padded company-background intro, some command redundancy, and missing result-verification after action execution.

Suggestions

Remove or sharply condense the opening "Mirantis is a cloud computing company..." paragraph, which explains vendor background Claude already knows.

Add a brief verify step after `membrane action run` (e.g. check the `output`/error fields and confirm the record changed) to close the workflow validation gap.

Standardize on one CLI invocation form (either `membrane` or `npx @membranehq/cli@latest`) throughout to remove the inconsistency.

Dimension	Reasoning	Score
Conciseness	The opening paragraph explaining what Mirantis the company does is background Claude largely already knows, and the "Popular actions" section repeats the action-list command already shown under "Searching for actions", so the body is mostly efficient but includes padding that could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready commands (install, login, connection ensure, action run, request) with a flags table cover the common flows; the minor gap is inconsistent CLI invocation ("membrane" vs "npx @membranehq/cli@latest") and unavoidable placeholders like CONNECTION_ID.	4 / 5
Workflow Clarity	The connection setup is well sequenced with explicit state checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-retry feedback loop, but the "Running actions" and proxy sections lack a verify-result step, leaving a minor validation gap that prevents a 5.	4 / 5
Progressive Disclosure	The body is organized into clearly headed sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references; since no bundle files exist and the detail is moderate, the structure is good with only minor organization gaps.	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 successfully pairs a what-clause with an explicit "Use when" trigger and leans on a distinctive brand name for low conflict risk. Its main weakness is generic, non-concrete action language and limited trigger keyword breadth.

Suggestions

Replace generic verbs with concrete capabilities, e.g. "manage Kubernetes clusters, node pools, images, SSH keys, backups, and registry credentials" instead of "Manage data, records".

Expand trigger terms to match what users actually say, e.g. "Use when the user wants to manage Mirantis clusters, deployments, or infrastructure".

Add a file/extension or product cue (e.g. "Mirantis Container Cloud" or "MKE") to widen natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Mirantis domain and several actions, but the actions are generic ("manage data", "manage records") rather than concrete, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Mirantis data") are present; it falls short of 5 only because the "what" is generic rather than concrete.	4 / 5
Trigger Term Quality	The description includes the brand term "Mirantis" and a trigger phrase ("Use when the user wants to interact with Mirantis data"), but keyword coverage is narrow with no synonyms or common variations a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	The repeated "Mirantis" branding gives the skill a clear niche with distinct triggers and minimal conflict risk, but the generic action verbs leave minor overlap with other data-management skills, so it is not a 5.	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/mirantis/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.