Name: exhibitday
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

exhibitday

ExhibitDay integration. Manage Organizations. Use when the user wants to interact with ExhibitDay data.

Quality

74%

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

Quality

Content

82%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 strong, actionable integration guide with executable commands and a well-validated connection workflow. Its main gaps are the absence of verification steps for destructive/batch actions and a long inline actions table that could be split into a reference file.

Suggestions

Add an explicit verify step after destructive or batch actions (e.g., re-list the event or check the response status) to close the workflow_clarity validation gap.

Consider moving the popular-actions table into a separate reference file (e.g. ACTIONS.md) and keeping only a few representative examples inline.

Trim mildly explanatory asides like "so you can focus on the integration logic rather than auth plumbing" to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is operational and command-driven with little padding of concepts Claude already knows, though lines like "so you can focus on the integration logic rather than auth plumbing" could be trimmed. Not a 5 due to minor over-explanation; not a 3 because the bulk is tight and useful.	4 / 5
Actionability	Provides fully executable, copy-paste-ready commands throughout (install, login, connection ensure, action list/run with --input JSON, request proxy) plus a flags table and action keys. Not a 4 because the common cases are covered with complete, runnable examples.	5 / 5
Workflow Clarity	The connection lifecycle is clearly sequenced with explicit polling and state-based validation checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a retry-after-action feedback loop. Not a 5 because destructive/batch actions (delete-event, update-*) are run with no verification step; not a 3 because the primary workflow does contain explicit validation.	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections (install, auth, connect, search, run, proxy, best practices) with no nested references and no bundle files to misplace. Not a 5 because the 20-row popular-actions table is sizable inline content that could live in a separate reference.	4 / 5
	Total	17 / 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 targets a distinct niche and includes an explicit Use when trigger, but its capability list is thin (one broad action) and trigger coverage relies on the brand name without synonyms. Strengthening the what and adding natural keyword variations would raise it.

Suggestions

Replace the single "Manage Organizations" action with 3-4 concrete capabilities the skill actually supports (e.g., manage exhibits, tasks, vendors, and deals) to improve specificity.

Add natural trigger synonyms users say beyond the brand name, such as "trade shows", "exhibitor events", or "event logistics".

Make the "when" clause more concrete, e.g. "Use when the user wants to manage trade show exhibits, tasks, or event logistics in ExhibitDay."

Dimension	Reasoning	Score
Specificity	Names the ExhibitDay domain and one concrete action ("Manage Organizations"), but coverage is minimal and not comprehensive. Not a 2 because it states a concrete verb+noun action beyond merely naming the domain; not a 4 because only one broad action is given.	3 / 5
Completeness	Both a "what" ("ExhibitDay integration. Manage Organizations.") and an explicit "Use when..." clause are present. Not a 5 because the "when" is generic and the "what" is thin; not a 3 because the Use when clause is explicit, lifting it above the missing-trigger cap.	4 / 5
Trigger Term Quality	"interact with ExhibitDay data" supplies a relevant trigger phrase, but coverage is limited to the brand name with no common synonyms (trade shows, events, exhibitors). Not a 4 because several natural variations a user might say are missing.	3 / 5
Distinctiveness Conflict Risk	ExhibitDay is a specific named platform with a distinct trigger ("interact with ExhibitDay data"), giving a clear niche with minimal conflict risk. Not a 4 because the brand-specific trigger is unambiguous.	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/exhibitday/SKILL.md
Commit: f484c82

Reviewed: ~16 hours 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.