Name: waitlist
Rating: 55.2 (1 reviews)
Author: membranedev

waitlist

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

Quality

62%

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

Quality

Content

67%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, executable guide to driving Waitlist through the Membrane CLI, with a clear connection-state workflow and useful command reference. It is held back by an unnecessary product-intro paragraph, placeholder-only end-to-end examples, and a dangling 'Step 2' reference.

Suggestions

Remove or compress the opening 'Waitlist is a SaaS application...' paragraph and the auth-plumbing prose; Claude does not need the market positioning.

Add one fully-worked example with a real connectionId and a concrete action (e.g., list participants on a named waitlist) so the run-action flow is copy-paste complete.

Fix the dangling 'Step 2' reference by labeling the post-connection section as Step 2, or rewrite the branch pointers to use section names.

Dimension	Reasoning	Score
Conciseness	Most of the body is lean command-driven guidance, but the opening SaaS description ("Waitlist is a SaaS application that allows businesses to create and manage waitlists... Marketing teams and product managers are the primary users") explains context Claude does not need, fitting 'Mostly efficient but includes some unnecessary explanation'; not a 4 because that intro paragraph and the auth-plumbing prose are trimmable padding.	3 / 5
Actionability	Concrete, copy-paste-ready commands populate every section (npm install, membrane login, connection ensure, action run) plus a flags table, matching 'Mostly executable guidance; concrete code or commands with minor gaps'; not a 5 because discovery/proxy examples rely on unresolved placeholders (CONNECTION_ID, /path/to/endpoint) without a worked end-to-end example.	4 / 5
Workflow Clarity	The connection flow is well sequenced with explicit state branches (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop after user action, matching 'Clear sequence with most checkpoints present; minor validation gaps'; not a 5 because the text references a 'Step 2' that is never labeled, leaving one navigational gap.	4 / 5
Progressive Disclosure	Content is organized into clear topical sections (Overview, Install, Authentication, Connecting, Searching, Proxy, Best practices) with no nested references, matching 'Good structure; most content appropriately placed; minor organization gaps'; not a 5 because the thin 'Popular actions' section duplicates 'Searching for actions' and no detail is split out despite the body exceeding 50 lines.	4 / 5
	Total	15 / 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 and a when clause anchored on the distinct Waitlist niche, but its action verbs are generic and it relies on a single trigger term without synonyms. It is functional but would benefit from more concrete capabilities.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Waitlist-specific actions (e.g., 'Create and manage waitlists, add and remove participants, build signup forms').

Add natural trigger synonyms and phrases such as 'waitlist signups', 'launch waitlist', or 'lead capture' so users phrasing the need differently still match.

Tighten the 'Use when' clause to name concrete scenarios (e.g., 'Use when the user wants to set up a product-launch waitlist or collect signup leads').

Dimension	Reasoning	Score
Specificity	The actions "Manage data, records, and automate workflows" name the domain but are generic rather than concrete (no specific operations like create/list/delete records), matching the anchor 'Names the domain but actions are minimal or generic'; not a 3 because the listed actions are not concrete verbs tied to Waitlist entities.	2 / 5
Completeness	Both a 'what' ("Manage data, records, and automate workflows") and an explicit 'when' ("Use when the user wants to interact with Waitlist data") are present, matching 'Has both what and when; when could be more explicit or specific'; not a 5 because the when clause is generic and the what lacks concrete triggers.	4 / 5
Trigger Term Quality	"Waitlist" and "interact with Waitlist data" are natural terms a user would say, but coverage lacks synonyms or extensions, fitting 'Some relevant keywords but missing common variations or synonyms'; not a 4 because only the single brand term is present.	3 / 5
Distinctiveness Conflict Risk	The specific "Waitlist" app niche gives it distinct triggers with only minor overlap risk against other SaaS-integration skills, matching 'Mostly distinct; minor overlap risk'; not a 5 because the generic 'Manage data, records, and automate workflows' portion could overlap with adjacent CRM/lead skills.	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/waitlist/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.