Name: mslm-cloud
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mslm-cloud

Mslm Cloud integration. Manage Users, Organizations. Use when the user wants to interact with Mslm Cloud 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/mslm-cloud/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-branched connection workflow including a polling feedback loop. Its main weakness is redundancy between the action-search sections and light opening padding that could be tightened.

Suggestions

Merge the 'Searching for actions' and 'Popular actions' sections, which both demonstrate `action list --intent=QUERY`, into one to remove duplication.

Tighten or remove the opening sentence 'Mslm Cloud is a cloud storage and collaboration platform...' since it explains product context Claude can infer from the docs link.

Fix the dangling cross-reference ('skip to Step 2') by explicitly labeling the workflow steps (Step 1a/1b/2) so the sequence is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-driven, but the opening 'what is Mslm Cloud' sentence and the near-duplicate 'Searching for actions' / 'Popular actions' sections add padding that could be trimmed, keeping it just below the 'efficient' level.	3 / 5
Actionability	It provides many concrete, copy-paste-ready CLI commands with real flags (e.g. `membrane connection ensure "https://mslm.io/cloud" --json`, the proxy flag table), with only minor gaps such as placeholder CONNECTION_ID values that the user must substitute.	4 / 5
Workflow Clarity	The connection flow is clearly sequenced with explicit state checkpoints (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR) and a poll-again feedback loop, but the cross-reference to an unlabeled 'Step 2' and a '1b' heading with no '1a' are minor sequencing gaps.	4 / 5
Progressive Disclosure	It is a single-file skill with no bundle files and is organized into clear topical sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices); the main gap is the duplicated action-list content that could be consolidated, but structure is otherwise good.	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 well-formed with an explicit 'Use when' trigger and a clear branded niche, but its action coverage and natural trigger terms are narrower than the skill actually supports. Tightening the trigger phrase to mirror the body's full scope would lift it.

Suggestions

Expand the action list to match the body's coverage, e.g. 'Manage Users, Organizations, Files, Folders, and Shared Links' instead of only Users and Organizations.

Make the 'when' trigger more concrete with natural user phrases, e.g. 'Use when the user wants to manage Mslm Cloud users, organizations, files, folders, or shared links.'

Add a natural file/extension or synonym term where applicable so users searching for 'Mslm Cloud files' or 'sharing' land on this skill.

Dimension	Reasoning	Score
Specificity	The description names the domain ("Mslm Cloud integration") and two concrete actions ("Manage Users, Organizations"), matching the 1-2 concrete actions anchor; it omits the file/folder/shared-link actions the body covers, so it is not comprehensive enough for a 4.	3 / 5
Completeness	It answers both 'what' ("Mslm Cloud integration. Manage Users, Organizations.") and 'when' ("Use when the user wants to interact with Mslm Cloud data"), but the 'when' is generic rather than listing concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	It includes relevant brand keywords ("Mslm Cloud", "Users", "Organizations") and a trigger clause, but lacks common natural variations or synonyms a user might say (e.g. files, folders, sharing), keeping it at the 'some relevant keywords' level rather than good coverage.	3 / 5
Distinctiveness Conflict Risk	The branded "Mslm Cloud" trigger gives it a clear niche with minimal conflict risk, but the generic "Manage Users, Organizations" portion could overlap with other user-management skills, leaving minor overlap risk rather than full distinctiveness.	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/mslm-cloud/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.