Name: waitwhile
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

waitwhile

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

Quality

66%

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/waitwhile/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 strong, executable CLI integration guide with a well-sequenced workflow and validation checkpoints for connection state. Main weaknesses are a marketing-style intro that pads tokens and a 'Popular actions' section that defers to runtime discovery instead of listing concrete Waitwhile actions.

Suggestions

Remove the marketing-style overview paragraph ('Waitwhile is a waitlist and scheduling platform...retail, healthcare, and restaurants') to save tokens.

Add a few concrete Waitwhile action examples (e.g. list guests, create a visit, get location) instead of only pointing to runtime discovery.

Consider moving the detailed connection-state handling and proxy flags table into a reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete command blocks, but includes unnecessary padding such as the marketing intro ('helps businesses manage customer flow...retail, healthcare, and restaurants') and 'so you can focus on the integration logic rather than auth plumbing'; not 2 because most sections are tight and code-driven.	3 / 5
Actionability	Provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests plus a flags table; not 5 because 'Popular actions' defers to runtime discovery rather than showing concrete Waitwhile action examples.	4 / 5
Workflow Clarity	Clear sequence (install -> auth -> connect -> wait/handle state -> search -> run -> proxy) with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop; not 5 because the action-run and proxy steps lack explicit validation of the returned result.	4 / 5
Progressive Disclosure	Well-organized single file with clear section headers and no nested references; with no bundle files present, structure is good, though the detailed connection-state handling and proxy flags table are candidates for a separate reference file. Not 5 because some inlined detail could be split out.	4 / 5
	Total	15 / 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 clearly identifies the Waitwhile niche and provides both a what and a when clause, but the action verbs are generic and the trigger relies almost entirely on the brand name. Tightening the actions and adding concrete trigger phrases would raise specificity and completeness.

Suggestions

Replace generic verbs ('Manage data, records') with concrete Waitwhile actions (e.g. 'manage waitlists, guests, locations, and staff records').

Expand the 'when' clause with concrete trigger phrases users actually say (e.g. 'Use when the user mentions waitlists, queues, Waitwhile guests, or booking/scheduling data').

Add natural keyword variations/synonyms (waitlist, queue, booking, scheduling) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Manage data, records, and automate workflows' name the Waitwhile domain and list three actions, but the actions are generic ('manage data') rather than concrete like the anchor-4 examples; not a 2 because more than one action is named.	3 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and an explicit 'when' ('Use when the user wants to interact with Waitwhile data') are present, matching anchor 4; not 5 because the 'when' clause is generic and circular rather than using concrete trigger phrases.	4 / 5
Trigger Term Quality	The natural trigger is essentially the brand name 'Waitwhile' plus 'data'; it lacks the common variations and synonyms that the anchor-4 example ('PDF files, forms, document extraction') shows.	3 / 5
Distinctiveness Conflict Risk	'Waitwhile' is a specific named platform giving a clear niche with distinct triggers and minimal conflict risk, matching anchor 5.	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/waitwhile/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.