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

mautic

Mautic integration. Manage Leads, Organizations, Users, Roles, Notes, Activities and more. Use when the user wants to interact with Mautic 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/mautic/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 delivers concrete, executable CLI guidance with a well-sequenced connection workflow and explicit state-handling feedback loops. It could be tightened by trimming the padded intro and moving the long actions table to a reference file.

Suggestions

Cut the marketecture padding in the opening paragraph and the 'Use action names and parameters as needed.' filler line.

Fix the loose step numbering (resolve the 'skip to Step 2' reference that has no labeled Step 1) and add a brief error-checking note after running actions.

Move the Popular actions table into a separate references file (e.g. ACTIONS.md) and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-driven and efficient, but the opening paragraph ('It's typically used by marketing teams and small to medium-sized businesses...') and filler like 'Use action names and parameters as needed.' are unnecessary explanation that could be tightened, matching the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands (npm install, membrane login, connection ensure, action list/run, request) covering the common cases, with only minor gaps from placeholders like <actionId> and CONNECTION_ID, fitting the 'mostly executable guidance with minor gaps' anchor.	4 / 5
Workflow Clarity	The connect→search→run sequence is clear and the connection-state section includes explicit validation checkpoints and a feedback loop (poll until READY, retry after CLIENT_ACTION_REQUIRED), but loose references like 'skip to Step 2' (with no labeled Step 1/2) and no error-checking after running actions leave minor gaps.	4 / 5
Progressive Disclosure	The single-file body is well-organized with clear section headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) and no bundle files to reference; the only gap is the large inline Popular actions table that could live in a separate reference file.	4 / 5
	Total	15 / 20 Passed

Description

73%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 cleanly states what the skill does and when to use it, anchored by a distinctive product name that prevents conflict with other skills. Its main weakness is relying on one generic verb ('Manage') plus 'and more' rather than enumerating specific actions.

Suggestions

Replace the generic 'Manage ... and more' with a few concrete verbs (e.g., 'Create, update, and list leads, companies, segments, and campaigns').

Expand the 'Use when' clause with additional natural trigger phrases such as 'manage Mautic contacts' or 'work with Mautic campaigns' to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domain (Mautic) and six concrete entities ('Manage Leads, Organizations, Users, Roles, Notes, Activities') but relies on a single generic verb ('Manage ... and more') rather than diverse concrete actions, matching the 'names domain and concrete items but not comprehensive actions' anchor.	3 / 5
Completeness	It has both a clear 'what' ('Manage Leads, Organizations...') and an explicit 'when' ('Use when the user wants to interact with Mautic data'), but the 'when' offers only a single trigger phrase rather than the multiple concrete triggers of the top anchor.	4 / 5
Trigger Term Quality	The product name 'Mautic' plus the entity names ('Leads, Organizations, Users, Roles, Notes, Activities') give good natural keyword coverage a user would actually say; only a few common variations are missing, fitting the 'good keyword coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	Mautic is a uniquely named product, so 'interact with Mautic data' is a clear niche trigger with minimal overlap risk against any other skill, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	16 / 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/mautic/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.