Name: everwebinar
Rating: 52.8 (1 reviews)
Author: membranedev

everwebinar

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

Quality

59%

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

Quality

Content

61%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 a well-structured, mostly executable CLI integration guide with a solid connection-state feedback loop, but it carries unnecessary background padding, inconsistent command invocation, a stub 'Popular actions' section, and lacks validation checkpoints for destructive operations. It is solid and usable with clear room to tighten and harden.

Suggestions

Remove the opening background paragraph and the filler line 'Use action names and parameters as needed.'; lead directly with the install/auth workflow to respect the token budget.

Add a verification/validation checkpoint before destructive operations — e.g. before running an action or sending a DELETE via the proxy, confirm the target connection/action and inspect the response state, with a fix-and-retry loop on CONFIGURATION_ERROR/SETUP_FAILED.

Standardize command invocation (pick `membrane` or `npx @membranehq/cli` and use it consistently) and either populate 'Popular actions' with concrete EverWebinar examples or remove the empty stub.

Dimension	Reasoning	Score
Conciseness	Most of the body is efficient CLI reference, but it opens with unnecessary background Claude does not need ('EverWebinar is an automated webinar platform built on the WebinarJam platform. It's used by businesses and marketers...') and includes filler like 'Use action names and parameters as needed.', fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean 4-anchor.	3 / 5
Actionability	The guide provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request with a full flags table), matching the 4-anchor; it is not a 5 because invocation is inconsistent ('membrane ...' vs 'npx @membranehq/cli ...') and the 'Popular actions' section is a stub that lists no actual actions.	4 / 5
Workflow Clarity	The connection flow has a genuine feedback loop (poll state -> handle READY/BUILDING/CLIENT_ACTION_REQUIRED -> re-poll), but the data-operation workflow (action run, proxy requests including DELETE) has no validation or verification steps before destructive operations, and step numbering is muddled (a referenced 'Step 2' is unlabeled and '1b' appears without a '1a'). The destructive-operations cap of 3 applies.	3 / 5
Progressive Disclosure	No bundle files exist, so there is no nested-reference problem; the body is a single file with well-organized section headers (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices), matching the 4-anchor 'Good structure; most content is appropriately placed'. It is not a 5 because at ~143 lines it exceeds the simple-skill exception and detailed material (clientAction state handling, the proxy flag reference) is inlined rather than split into one-level-deep reference files.	4 / 5
	Total	14 / 20 Passed

Description

57%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 correctly pairs a 'what' with an explicit 'when' clause and is anchored by a distinctive product name, but its action language is generic and its trigger coverage is limited to the product name alone. It is competent but not comprehensive.

Suggestions

Replace generic verbs ('Manage data, records, and automate workflows') with 2-4 concrete EverWebinar operations such as 'list webinars, fetch registrations, manage webinar series, and register attendees'.

Expand the 'when' clause with multiple natural trigger phrases users would actually say, e.g. 'Use when the user wants to manage EverWebinar webinars, view registrations or attendees, or automate webinar workflows.'

Add common synonyms/extensions ('webinar', 'automated webinar', 'webinar series') so the description triggers on the phrasings users naturally use, not just the product name.

Dimension	Reasoning	Score
Specificity	The description names the domain ('EverWebinar integration') but its actions are generic — 'Manage data, records, and automate workflows' lists no concrete operations (e.g. list webinars, register attendees, fetch registrations), matching the anchor 'Names the domain but actions are minimal or generic' rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	Both 'what' ('EverWebinar integration. Manage data, records, and automate workflows.') and an explicit 'when' ('Use when the user wants to interact with EverWebinar data.') are present, matching the 4-anchor; it is not a 5 because the 'when' clause is a single generic trigger rather than concrete trigger phrases with multiple variants.	4 / 5
Trigger Term Quality	The trigger 'Use when the user wants to interact with EverWebinar data' supplies the product name as the natural keyword, but coverage is thin — it omits common variations a user might say ('webinar', 'automated webinar', 'webinar series', 'registrations'), fitting 'Some relevant keywords but missing common variations or synonyms' rather than the 4-anchor's 'good keyword coverage'.	3 / 5
Distinctiveness Conflict Risk	The product name 'EverWebinar' gives it a clear, distinct niche, but the generic action language ('Manage data, records, and automate workflows') is shared across sibling Membrane integration skills (e.g. WebinarJam), creating minor overlap risk with closely related skills rather than the minimal-conflict 5-anchor.	4 / 5
	Total	13 / 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/everwebinar/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.