Name: mixmax
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mixmax

MixMax integration. Manage Users, Organizations. Use when the user wants to interact with MixMax data.

Quality

74%

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

Quality

Content

82%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 executable CLI commands and a strong connection-setup workflow featuring real validation feedback loops, weakened only by a light intro paragraph and the absence of validation guidance around destructive action execution.

Suggestions

Trim or relocate the opening 'Mixmax is a sales engagement platform...' paragraph to remove content Claude can largely infer and lift conciseness.

Add an explicit validation/confirmation step before destructive or mutating actions (e.g., send-message, cancel-sequence-recipient, add/remove-unsubscribe) to close the workflow_clarity gap.

Consider moving the full popular-actions table into a separate references file referenced from the body to tighten progressive disclosure if the skill grows further.

Dimension	Reasoning	Score
Conciseness	The body is dominated by lean, executable commands and a compact actions table; the only mild over-explanation is the opening paragraph defining what Mixmax is, which Claude could largely infer.	4 / 5
Actionability	It provides fully executable, copy-paste-ready membrane CLI commands for login, connection setup, action search/run with JSON params, and proxy requests, plus a concrete table of popular actions with keys and descriptions covering common cases.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with explicit validation (state checks, polling until non-BUILDING, branching on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after user action), but destructive actions like send-message or cancel-sequence lack pre-flight confirmation or verification steps, leaving a minor validation gap.	4 / 5
Progressive Disclosure	The single SKILL.md is organized into clearly headed sections with no nested external references, and the inline popular-actions table is reasonable as an overview reference; the only minor gap is that the sizable actions table could arguably live in a separate reference file.	4 / 5
	Total	17 / 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 is concise and correctly pairs a 'what' with a 'when' clause anchored on a distinctive brand name, but it under-sells the skill's breadth by naming only Users and Organizations and offers only generic trigger phrasing.

Suggestions

List more concrete capabilities (e.g., sequences, messages, snippets, polls, live feed events) to lift specificity from 3 toward 4-5.

Add natural trigger phrases users would say, such as 'send Mixmax emails', 'manage Mixmax sequences', or 'check Mixmax engagement', to improve trigger term coverage.

Tighten the 'when' clause with concrete examples (e.g., 'Use when the user wants to send, sequence, or track Mixmax emails') rather than the generic 'interact with MixMax data'.

Dimension	Reasoning	Score
Specificity	The description names the MixMax domain and two concrete actions ('Manage Users, Organizations') but omits the many other capabilities the skill covers (sequences, messages, snippets, polls, live feed, webhooks), so it is not comprehensive.	3 / 5
Completeness	Both 'what' ('MixMax integration. Manage Users, Organizations.') and 'when' ('Use when the user wants to interact with MixMax data.') are present and explicit, though the 'when' clause is generic rather than enumerating concrete triggers.	4 / 5
Trigger Term Quality	The brand name 'MixMax' is a relevant keyword a user would naturally say, but the description repeats only that brand term and misses common task-level variations like 'mixmax sequences', 'mixmax email', or 'send mixmax message'.	3 / 5
Distinctiveness Conflict Risk	MixMax is a specific brand niche with a distinct trigger, so the description is clearly distinguishable from other skills and unlikely to fire for the wrong one.	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/mixmax/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.