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

sendx

SendX integration. Manage Persons, Organizations, Deals, Leads, Activities, Notes and more. Use when the user wants to interact with SendX 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/sendx/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 content is a well-structured, actionable guide with strong command coverage and a clear connection state-machine, but it has minor padding in the intro, inconsistent CLI invocation styles, glitchy step numbering, and slight section redundancy.

Suggestions

Trim the marketing intro to one factual line about what SendX is and remove "so you can focus on the integration logic rather than auth plumbing".

Fix the step numbering: label the "Step 2" section explicitly and resolve the orphaned "1b" subheading.

Standardize on one CLI invocation style (`membrane` vs `npx @membranehq/cli@latest`) to avoid confusing the agent.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands, but the marketing-flavored intro ("nurture leads, engage customers, and drive sales") and asides like "so you can focus on the integration logic rather than auth plumbing" are minor over-explanation that could be trimmed.	4 / 5
Actionability	Provides concrete, copy-pasteable commands for every common case (install, login, connection ensure, polling, action list/run, request proxy) plus a flag table, with only minor gaps such as the inconsistent use of `membrane` vs `npx @membranehq/cli@latest` and unfilled placeholders.	4 / 5
Workflow Clarity	The connection setup is a clear state-machine with explicit checkpoints and a polling feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), though step numbering is glitchy ("skip to Step 2" with no labeled Step 2, "1b" with no "1a") and action/proxy execution lacks output validation.	4 / 5
Progressive Disclosure	Single-file skill with no bundle files, organized into clear headed sections covering overview, setup, auth, connection, action discovery, and best practices; minor gaps include redundancy between "Searching for actions" and "Popular actions" and an entity tree that could be tighter.	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 is well-formed with an explicit "Use when" trigger and named entities, but the action vocabulary is generic ("Manage ... and more") and the trigger phrase lacks synonyms or concrete variations. It is distinct thanks to the SendX brand but could be sharpened.

Suggestions

Replace the generic "Manage ... and more" with concrete verbs (e.g., "create, update, search, and delete Persons, Organizations, Deals, Leads, Activities, and Notes").

Expand the trigger with concrete natural phrases, e.g. "Use when the user wants to create or update SendX contacts, manage leads and deals, or log activities in SendX."

Drop the vague "and more" to avoid over-claiming capabilities not enumerated.

Dimension	Reasoning	Score
Specificity	Names the SendX domain and lists several concrete entities ("Persons, Organizations, Deals, Leads, Activities, Notes"), but the action verb is the single generic "Manage ... and more", so coverage of concrete actions is not comprehensive.	3 / 5
Completeness	It has an explicit "Use when..." clause and a clear "what" (SendX integration managing named entities), but the "when" is generic ("interact with SendX data") rather than packed with concrete trigger phrases, fitting the anchor where "when" could be more specific.	4 / 5
Trigger Term Quality	The trigger "Use when the user wants to interact with SendX data" includes the natural keyword "SendX" but offers no synonyms, related phrases, or variations, matching the anchor with some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	The explicit "SendX" branding and SendX-tied trigger make it mostly distinct, though generic CRM-style entities (Leads, Deals, Organizations) create minor overlap risk with related CRM 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/sendx/SKILL.md
Commit: f484c82

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