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

omnisend

Omnisend integration. Manage Persons, Organizations, Activities, Notes, Files, Deals and more. Use when the user wants to interact with Omnisend 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/omnisend/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 is highly actionable with concrete CLI commands and a well-documented connection state machine, but it is held back by a padded opening paragraph, a redundant section, and a couple of broken internal cross-references. It is strong and usable with minor tightening needed.

Suggestions

Remove or trim the opening marketing paragraph about what Omnisend is and who uses it; assume Claude's competence and lead directly with the integration workflow.

Delete or merge the redundant 'Popular actions' section, which only restates the 'membrane action list --intent=QUERY' command already shown under 'Searching for actions'.

Fix the workflow cross-references: label the 'connection ensure' step as '1a' and either add an explicit 'Step 2' anchor on 'Searching for actions' or reword the 'skip to Step 2' instruction to point to the section by name.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but the opening marketing paragraph ('Omnisend is an email marketing automation platform ...') and the redundant 'Popular actions' section, which restates the action-list command, are unnecessary padding.	3 / 5
Actionability	Concrete copy-paste CLI commands cover install, auth, connection, search, run, and proxy with a full options table, but they rely on placeholders (CONNECTION_ID, <actionId>, QUERY) and lack a fully-resolved end-to-end worked example.	4 / 5
Workflow Clarity	The connection flow is a clear state machine with explicit polling checkpoints and error handling (READY, BUILDING, CLIENT_ACTION_REQUIRED, CONFIGURATION_ERROR), but broken cross-references ('skip to Step 2' with no Step 2, '1b' with no '1a') introduce minor confusion.	4 / 5
Progressive Disclosure	The single file is well-organized into clearly headed sections with no external references needed, though everything is inlined and the oddly placed 'Popular actions' section is a minor organization gap.	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 answers both what and when with a clear brand-specific trigger, but leans on a single generic verb and omits the natural marketing-domain terms users would actually say. It is solid but not exemplary.

Suggestions

Replace the single generic verb 'Manage' with several distinct concrete actions (e.g. 'Create and send email/SMS campaigns, manage contacts and forms, track automations and products').

Add natural trigger synonyms users would say, such as 'email marketing', 'campaigns', 'SMS', 'contacts', or 'forms', alongside 'Omnisend'.

Tighten the 'when' clause to reference concrete intents (e.g. 'Use when the user wants to send campaigns or manage contacts in Omnisend') rather than the generic 'interact with Omnisend data'.

Dimension	Reasoning	Score
Specificity	Names the domain and lists six concrete entity types ('Persons, Organizations, Activities, Notes, Files, Deals') but applies only one generic verb ('Manage') across them, leaving actions minimal rather than comprehensive.	3 / 5
Completeness	Both 'what' ('Omnisend integration. Manage ...') and 'when' ('Use when the user wants to interact with Omnisend data') are explicitly present, but the 'when' clause is generic and could be more specific.	4 / 5
Trigger Term Quality	The brand name 'Omnisend' and phrase 'interact with Omnisend data' are present, but common natural synonyms users would say (e.g. 'email campaigns', 'SMS marketing', 'contacts', 'forms') are missing.	3 / 5
Distinctiveness Conflict Risk	The Omnisend brand name gives a clear niche trigger, but the generic CRM-style entity list (Persons, Organizations, Activities, Notes, Files, Deals) carries minor overlap risk with other data-management 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/omnisend/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.