Name: mumara
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

mumara

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

Quality

70%

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

Quality

Content

75%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 executable commands and a clear connection workflow featuring state-based checkpoints, but it carries some redundancy and mild padding that could be tightened.

Suggestions

De-duplicate the action-list command (shown in both "Searching for actions" and "Popular actions") and trim filler sentences like "This is the fastest way to get a connection".

Add brief output/error-validation guidance to the "Running actions" and "Proxy requests" sections so failures are caught rather than only described in best practices.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but contains padding ("so you can focus on the integration logic rather than auth plumbing", "This is the fastest way to get a connection") and repeats the action-list command across the "Searching for actions" and "Popular actions" sections.	3 / 5
Actionability	Copy-paste-ready commands cover install, login, connection ensure/get with --wait, action list/run, and the proxy request with a full flag table, fully executable for the common cases.	5 / 5
Workflow Clarity	A clear install→authenticate→connect→search→run sequence with explicit state-based checkpoints and a feedback loop (poll until READY, re-poll after CLIENT_ACTION_REQUIRED), though the run/proxy steps lack output validation guidance.	4 / 5
Progressive Disclosure	No bundle files exist, but the single-file body is well-organized with clear headers and a self-contained structure; dynamic action discovery via the CLI substitutes for external reference files.	4 / 5
	Total	16 / 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 clear and distinct, naming Mumara and offering an explicit Use-when trigger, but it undersells the skill's breadth (only Users and Organizations out of many entities) and uses a somewhat generic trigger phrase.

Suggestions

Expand the action list beyond Users and Organizations to reflect the full entity set (Campaigns, Email Lists, Templates, Domains, Suppression Lists, etc.).

Replace the generic "interact with Mumara data" trigger with concrete natural-language phrases users would say, e.g. "Use when managing email campaigns, lists, templates, or domains in Mumara."

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ("Manage Users, Organizations") but omits the many other entities the body exposes (Campaigns, Email Lists, Templates, Domains, etc.), so coverage is not comprehensive.	3 / 5
Completeness	Both a "what" (Mumara integration, manage Users/Organizations) and an explicit "when" clause are present, but the "what" is thin relative to the skill's full scope, keeping it below a 5.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with Mumara data" names the product but relies on the generic phrase "interact with... data" rather than natural synonyms users would say (campaigns, email lists, templates).	3 / 5
Distinctiveness Conflict Risk	Targeting a named platform (Mumara) gives it a clear niche with distinct triggers and minimal risk of firing for unrelated 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/mumara/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.