Tessl • The management layer for AI agent skills

SkillPublic

automizy

Automizy integration. Manage data, records, and automate workflows. Use when the user wants to interact with Automizy data.

Quality

71%

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.

A strongly actionable, command-first integration guide with an unusually good connection-state workflow (explicit polling, clientAction handling, and error states). Its main flaws are the dead 20-row actions table wasting tokens, a broken "Step 2" cross-reference, and the absence of any validation around destructive operations like delete and send-campaign, which caps workflow clarity.

Suggestions

Replace the "No description" descriptions in the Popular actions table with one-line purpose summaries, or move the table to a reference file and inline only the top 5 actions.

Fix the "skip to **Step 2**" reference — no Step 2 exists; number the workflow steps (install → login → connect → search → run) or use section names.

Add a verification checkpoint before destructive or irreversible actions, e.g. confirm with the user before running delete-* actions or send-campaign, and check the output field for success after running.

Dimension	Reasoning	Score
Conciseness	The CLI guidance ("Install the Membrane CLI", "membrane connection ensure", "membrane action run") is efficient and commands-first, but there is real waste: a 20-row "Popular actions" table where every Description cell reads "No description", plus an intro paragraph ("Marketers and business owners use Automizy to create and automate email campaigns...") that pads rather than instructs. Not anchor 4 because the dead table alone is ~20 wasted lines.	3 / 5
Actionability	Every step ships a copy-paste-ready command: "npm install -g @membranehq/cli@latest", "membrane login --tenant --clientName=<agentType>", "membrane connection ensure \"https://Automizy.com\" --json", "npx @membranehq/cli connection get <id> --wait --json", "membrane action run <actionId> --connectionId=... --input '{\"key\": \"value\"}'", plus a complete proxy flag table. The common cases (install, auth, headless auth, connect, wait, search, run, proxy) are each concretely covered.	5 / 5
Workflow Clarity	The connection flow has genuine validation checkpoints and a feedback loop (poll with --wait until state leaves BUILDING, act on clientAction, re-poll to READY, check error on CONFIGURATION_ERROR/SETUP_FAILED) — anchor 4 quality. However the skill documents destructive and outward-facing operations (delete-contact, delete-campaign, send-campaign) with no verification or confirmation steps anywhere, which caps workflow clarity at 3; the broken "skip to Step 2" reference (no Step 2 exists) further muddies the sequence.	3 / 5
Progressive Disclosure	No bundle files exist, and the single body is well-sectioned (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references. Not anchor 5 because the "Popular actions" table and proxy reference material are inline bulk that belongs in a separate reference file, and the "Agent Types" line is an unstructured aside.	4 / 5
	Total	15 / 20 Passed

Description

61%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 has an explicit 'Use when' clause and a distinct brand-anchored trigger, but the capability statement is generic. Replacing "Manage data, records, and automate workflows" with concrete Automizy capabilities (email campaigns, contacts, segments, automations) would fix both specificity and trigger coverage.

Suggestions

Replace the generic "Manage data, records, and automate workflows" with concrete actions such as "Create and send email campaigns, manage contacts and smart lists, build automations and email sequences".

Add natural trigger terms and synonyms users would say, e.g. "email marketing", "newsletters", "email campaigns", "contact lists".

Mention the email marketing domain explicitly so the skill is discoverable even when the user does not name Automizy.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain (Automizy) but the actions are generic — no concrete operations like creating email campaigns, managing contacts, or segmenting audiences. It does not rise to anchor 3 because no 1-2 genuinely concrete actions are listed.	2 / 5
Completeness	Both parts are present: the 'what' ("Automizy integration. Manage data, records, and automate workflows") and an explicit 'when' clause ("Use when the user wants to interact with Automizy data"). Not anchor 5 because the 'what' is vague and the 'when' lacks concrete trigger phrases beyond the brand name.	4 / 5
Trigger Term Quality	"Automizy" (repeated twice) is a strong natural brand trigger a user would actually say, but common variations and synonyms (email marketing, campaigns, newsletters, contacts, open rates) are missing. Not anchor 2 because the keyword present is specific rather than generic like "works with files".	3 / 5
Distinctiveness Conflict Risk	"Automizy integration" and "Use when the user wants to interact with Automizy data" establish a clear brand-anchored niche with minimal conflict risk — other skills would not trigger from these terms. The generic middle sentence slightly weakens it but the trigger is unambiguous.	5 / 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
Revision: f484c82

Reviewed: 16 days ago

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.

automizy

Table of Contents

Is this your skill?