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

automizy

Automizy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Automizy 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/automizy/SKILL.md

Quality

Content

68%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, executable Membrane CLI commands and a well-structured connection workflow. Its weaknesses are padding (a marketing blurb and a 'No description' action table) and the absence of validation/confirmation steps before destructive operations like delete and send.

Suggestions

Remove the marketing-style intro paragraph and trim the 'Popular actions' table to only actions with meaningful descriptions, or drop the 'No description' rows.

Add an explicit validation/confirmation checkpoint before destructive actions (e.g. 'Before running delete-* or send-campaign, confirm the target id with the user and verify the resource exists via the corresponding get-* action').

Move the bulk action catalog and proxy flag reference into a separate reference file referenced from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the opening product-marketing paragraph ('Automizy is an email marketing automation platform...') and the 20-row 'Popular actions' table where every row says 'No description' are padding Claude does not need.	3 / 5
Actionability	It provides copy-paste-ready, executable CLI commands for every common case — install, login, connection ensure, polling get --wait, action list/run, and proxy requests — with concrete flags and JSON output examples.	5 / 5
Workflow Clarity	The connection flow is well sequenced with polling/feedback checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive actions exposed in the table (delete-campaign, delete-contact, send-campaign) have no validation or confirmation step, capping workflow clarity at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	No bundle files exist and content is organized into clear headed sections (install, auth, connecting, searching, running, proxy, best practices); however the skill exceeds 50 lines and inlines bulk material (the 20-row action table and flag tables) that could live in a separate reference file.	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 third-person, names the product clearly, and includes an explicit 'Use when' trigger, satisfying the core what/when requirements. It loses points for generic action verbs and a thin, single-keyword trigger that lacks synonyms or concrete capability terms.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with concrete Automizy capabilities such as 'create and send email campaigns, segment contacts, and build automation workflows'.

Broaden the trigger with natural synonyms users actually say, e.g. 'Use when the user wants to work with Automizy email campaigns, contact lists, segments, or automations'.

Add file-format or entity trigger terms (campaigns, smart lists, custom fields, forms) to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Automizy integration') plus a couple of actions ('Manage data, records, and automate workflows'), but the actions are generic rather than comprehensive and concrete like 'create campaigns' or 'segment contacts'.	3 / 5
Completeness	Both a 'what' (Automizy integration, manage data/records/workflows) and an explicit 'when' clause are present, but the trigger is generic ('interact with Automizy data') rather than listing concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	The trigger relies almost entirely on the product name ('Use when the user wants to interact with Automizy data'); relevant but missing natural synonyms or variations users might say such as 'email campaigns' or 'Automizy contacts'.	3 / 5
Distinctiveness Conflict Risk	The named product ('Automizy') gives it a clear, distinct niche with minimal conflict risk, though the surrounding action language ('manage data, records, automate workflows') is generic enough to leave minor overlap with general automation skills.	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/automizy/SKILL.md
Commit: f484c82

Reviewed: 3 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.