Name: integromat
Rating: 59.2 (1 reviews)
Author: membranedev

integromat

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

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/integromat/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, built around concrete, copy-paste-ready Membrane CLI commands with a clear connection-state workflow and polling feedback loops. Its weaknesses are a padded introductory paragraph and inconsistent step numbering (a referenced "Step 2" and an orphan "1b").

Suggestions

Trim the introductory paragraph to one line and remove filler like "Use action names and parameters as needed." since the commands already demonstrate usage.

Fix the workflow numbering: define "Step 1"/"Step 2" explicitly or drop the "skip to Step 2" and "1b" labels so the connection flow is unambiguous.

Add a brief validation note for destructive proxy methods (POST/PUT/PATCH/DELETE), e.g. confirming the endpoint and payload before running `membrane request`.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient command examples, but the introductory paragraph ("used by businesses and individuals looking to integrate their favorite tools...") and filler like "Use action names and parameters as needed." over-explain what Claude already knows, matching the mostly-efficient-with-some-unnecessary-explanation anchor.	3 / 5
Actionability	It provides copy-paste-ready `membrane` commands throughout — install, login, connection ensure/get, action list/run, and request — each with concrete flags, plus a full proxy-options table, fully covering the common cases.	5 / 5
Workflow Clarity	The connect-to-Integromat flow has clear state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) with a polling feedback loop, but it references an undefined "Step 2" and labels a section "1b" with no "1a", which is a minor sequencing gap keeping it below 5.	4 / 5
Progressive Disclosure	The content is organized into well-labeled sections (Overview, Working with Integromat, Install, Auth, Connecting, Searching, Running, Proxy, Best practices) with no nested references, and no bundle files exist to split out; structure is good with only minor organization gaps.	4 / 5
	Total	16 / 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 cleanly states both what the skill does and when to use it, anchored by the distinct Integromat brand name. Its main weaknesses are generic action verbs and a missing "Make" synonym that would broaden trigger coverage.

Suggestions

Replace generic verbs with concrete Integromat/Make actions, e.g. "Create and run scenarios, manage connections, and run module actions."

Add the "Make" synonym and platform terms like "scenarios" and "modules" so the trigger matches how users actually refer to the platform.

Expand the "Use when" clause with multiple concrete triggers, e.g. "Use when the user wants to build Integromat/Make scenarios, run modules, or manage data and records."

Dimension	Reasoning	Score
Specificity	The description names the Integromat domain and lists a few actions ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete, matching the anchor that names domain plus 1-2 actions without being comprehensive.	3 / 5
Completeness	It gives an explicit "what" ("Integromat integration. Manage data, records, and automate workflows.") and an explicit "when" ("Use when the user wants to interact with Integromat data."), but the trigger is a single phrase rather than multiple concrete trigger phrases, so it stops short of a 5.	4 / 5
Trigger Term Quality	It includes the natural brand keyword "Integromat" plus "data", "records", and "workflows", but misses the major synonym "Make" (the platform's current name, referenced in the body) and the platform-specific term "scenarios", so coverage has gaps.	3 / 5
Distinctiveness Conflict Risk	The "Integromat" brand name carves a clear niche with low conflict risk, but the generic "automate workflows" phrasing could overlap slightly with other automation skills, keeping it just below a 5.	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/integromat/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.