Name: visitor-queue
Rating: 58.4 (1 reviews)
Author: membranedev

visitor-queue

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

Quality

68%

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

Quality

Content

75%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 an efficient, actionable guide with executable Membrane CLI commands and a clear end-to-end workflow including connection-state validation. It falls just short of top marks because some inline reference material could be externalized and batch/destructive action workflows lack explicit validate-then-retry feedback loops.

Suggestions

Add an explicit validation/retry feedback loop for batch or destructive action runs (e.g. check the output/error field and re-run with corrected input before proceeding).

Consider moving the full request-flag table and connection state-machine details into a separate REFERENCE.md to keep the core workflow lean and one level deep.

Show a concrete worked example of action list/run with a real Visitor Queue intent and a sample output field, rather than only the generic QUERY placeholder.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable command blocks and a compact flag table; assumes Claude's competence and avoids explaining generic CLI or auth concepts, with only minor prose around connection states that could be trimmed.	4 / 5
Actionability	Provides concrete, executable commands for install, login, connection ensure/get, action list/run, and proxy requests, plus a flag table; minor gaps such as placeholder CONNECTION_ID and generic QUERY intent are clearly flagged.	4 / 5
Workflow Clarity	Clear sequence from install to auth to connection (with polling and READY/BUILDING/CLIENT_ACTION_REQUIRED branching) to action discovery and execution, with state checks serving as validation checkpoints; not a full 5 because batch/destructive operations lack explicit validate-fix-retry feedback loops.	4 / 5
Progressive Disclosure	Single-file skill with no bundle directories, organized into well-labeled sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices); clean navigation though some reference-style material (full flag descriptions, state-machine details) is inlined.	4 / 5
	Total	16 / 20 Passed

Description

61%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 target product and includes an explicit "Use when" trigger, giving it solid completeness and distinctiveness. Its weakness is specificity and trigger term quality: the listed actions are generic and it omits natural user vocabulary like leads, companies, or website visitors.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete Visitor Queue capabilities such as retrieving lead/company data, listing website visitors, and triggering workflows.

Add natural trigger terms users would actually say, e.g. "Use when the user asks about companies visiting their website, B2B leads, or Visitor Queue records."

Include file-format or entity synonyms (leads, companies, visitors) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the Visitor Queue domain plus a few generic actions ("Manage data, records, and automate workflows"), but the actions are minimal and generic rather than concrete capabilities like extracting leads or listing companies.	2 / 5
Completeness	Explicitly states both what it does (manage data, records, automate workflows) and when to use it ("Use when the user wants to interact with Visitor Queue data"), though the trigger phrasing could be more concrete and varied.	4 / 5
Trigger Term Quality	Includes the product name and a generic "Use when the user wants to interact with Visitor Queue data" trigger, but misses natural user phrases such as leads, companies, website visitors, or B2B prospects.	3 / 5
Distinctiveness Conflict Risk	Names the specific product Visitor Queue with a clear niche trigger, making it unlikely to conflict with other skills.	5 / 5
	Total	14 / 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/visitor-queue/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.