Name: eventzilla
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

eventzilla

Eventzilla integration. Manage Events, Contacts. Use when the user wants to interact with Eventzilla data.

Quality

71%

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

Quality

Content

76%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 with copy-paste commands and a clean connection workflow, but workflow clarity is capped by a dangling 'Step 2' reference and the absence of verification steps for destructive actions, and a few prose passages could be trimmed.

Suggestions

Fix the dangling cross-reference: label the connection steps (e.g. 'Step 1: Connect', 'Step 2: Search & run actions') or remove the 'skip to Step 2' phrasing so the target exists.

Add a verification checkpoint after destructive/batch actions (e.g. re-fetch the order with get-transaction or get-attendee to confirm cancel/check-in took effect).

Trim the introductory paragraph and 'Agent Types' line to the essentials, removing explanatory framing Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is dominated by executable commands and compact tables with little padding, but the opening paragraph ('Think of it as a streamlined solution for handling event logistics') and the Agent Types prose are mild over-explanation Claude does not need.	4 / 5
Actionability	It provides copy-paste-ready commands for every common case (install, login, connection ensure, polling, action list/run, proxy) plus a flag reference table, fully covering the typical workflow.	5 / 5
Workflow Clarity	The connection flow is well sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but 'skip to Step 2' references a non-existent Step 2, and destructive actions like cancel-order and toggle-event-sales are run with no verification step, capping this dimension.	3 / 5
Progressive Disclosure	The skill is a single file with clearly organized sections and headers and no bundle references to navigate; the large Popular actions table is a reasonable inline quick-reference, with only minor organization gaps keeping it from a 5.	4 / 5
	Total	16 / 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 correctly pairs a 'what' and a 'when' clause and targets a clearly distinct platform, but its action verbs are generic ('Manage') and its trigger phrasing ('interact with Eventzilla data') is less natural and less comprehensive than ideal.

Suggestions

Replace the generic 'Manage Events, Contacts' with concrete operations, e.g. 'Create and list events, manage contacts and registrants, process check-ins and orders in Eventzilla'.

Broaden the 'Use when' trigger with natural phrasings users actually say, e.g. 'Use when the user wants to manage Eventzilla events, registrations, attendees, or contacts'.

Add high-frequency nouns (registrations, tickets, attendees, check-in, orders) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Eventzilla) and two actions ('Manage Events, Contacts'), but 'Manage' is a generic verb rather than concrete operations like create/list/cancel, so it is not comprehensive enough for a 4.	3 / 5
Completeness	Provides both a clear 'what' ('Manage Events, Contacts') and an explicit 'when' ('Use when the user wants to interact with Eventzilla data'), but the trigger could be more specific with concrete phrases rather than the generic 'interact with ... data'.	4 / 5
Trigger Term Quality	Includes the natural nouns 'Eventzilla', 'Events', and 'Contacts', but the trigger phrase 'interact with Eventzilla data' is slightly generic and misses common variations users would actually say (e.g. 'registrations', 'tickets', 'check-in').	3 / 5
Distinctiveness Conflict Risk	'Eventzilla' is a named platform with a clear niche and distinct triggers, so there is minimal risk of this firing for an unrelated skill.	5 / 5
	Total	15 / 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/eventzilla/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.