Name: zendesk-sell
Rating: 51.2 (1 reviews)
Author: membranedev

zendesk-sell

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

Quality

57%

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/zendesk-sell/SKILL.md

Quality

Content

48%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 CLI usage guidance is genuinely actionable and the connection workflow is well-sequenced with state checkpoints, but these strengths are buried under an enormous padded bullet list of mostly fictitious 'entities' that wastes the context window. The skill needs radical trimming of the Overview section.

Suggestions

Delete the ~480-line entity bullet list (Lead through Better World); most are not real Zendesk Sell objects and it is pure padding that violates token efficiency.

Move any genuine entity reference content into a references/ file and link to it one level deep, or replace the list with a short prose summary of the core objects (Lead, Contact, Deal, Task, Note).

Add a brief result-verification note after 'membrane action run' so the workflow has an explicit feedback checkpoint on the action-execution side.

Dimension	Reasoning	Score
Conciseness	Roughly 480 of ~640 lines are a padded bullet list of 'entities' running from Lead/Contact through Love, Happiness, Meaning, Purpose, Compassion, and Better World — heavily padded junk, most of which are not real Zendesk Sell objects, matching the 'severely verbose; heavily padded' anchor; the lean CLI section does not rescue it.	1 / 5
Actionability	The working section gives concrete, executable commands (npm install -g @membranehq/cli@latest, membrane login, membrane connection ensure, membrane action list/run, membrane request) with flags and JSON examples, fitting 'mostly executable guidance; concrete commands with minor gaps'; not 5 because parameter construction for action run is only sketchily shown.	4 / 5
Workflow Clarity	The connection flow is a clear sequenced process (install -> login -> connection ensure -> poll --wait -> handle CLIENT_ACTION_REQUIRED -> search -> run) with explicit state checkpoints (READY/BUILDING/CONFIGURATION_ERROR) and a poll-again feedback loop, matching 'clear sequence with most checkpoints present'; held at 4 because result verification after running actions is not addressed.	4 / 5
Progressive Disclosure	Section headers exist (Working with, Popular actions, Best practices) but the Overview is a ~480-line inlined entity list that belongs in a separate reference file or should be removed, and no bundle files exist to offload it, matching 'some structure but content that should be separate is inline'.	3 / 5
	Total	12 / 20 Passed

Description

66%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 distinct and includes an explicit 'Use when' trigger, but its capability language is generic ('manage data, records, and automate workflows') and lacks the concrete entity keywords (leads, deals, contacts) users would naturally say. It is solid but not exemplary.

Suggestions

Replace generic verbs with concrete Zendesk Sell actions, e.g. 'Create and update leads, contacts, and deals; log tasks and notes; automate sales workflows.'

Add the natural entity terms users say (leads, deals, contacts, tasks) to the trigger clause, e.g. 'Use when the user wants to manage Zendesk Sell leads, deals, contacts, or tasks.'

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Zendesk Sell domain and a couple of action phrases, but the verbs (manage, automate) are generic rather than concrete like extract/fill, fitting the 'names domain and 1-2 actions but not comprehensive' anchor; not a 2 because it lists multiple distinct action phrases.	3 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and an explicit when ("Use when the user wants to interact with Zendesk Sell data"), so it is not capped at 3; held at 4 rather than 5 because the 'what' is generic rather than concrete trigger phrases.	4 / 5
Trigger Term Quality	"Zendesk Sell" and "interact with Zendesk Sell data" provide the core brand keyword a user would say, but common entity synonyms users actually mention (leads, deals, contacts, CRM) are missing, matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	Naming the specific product "Zendesk Sell" carves out a clear niche with distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (647 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: membranedev/application-skills
Path: skills/zendesk-sell/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.