Name: waylay
Rating: 59.2 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

waylay

Waylay integration. Manage data, records, and automate workflows. Use when the user wants to interact with Waylay 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/waylay/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 efficient, executable, and well-structured CLI documentation with concrete commands and a clear connection state-machine. It would reach the top band by fixing the dangling "Step 2" reference and adding a brief validation step after running actions or proxy requests.

Suggestions

Fix the dangling "Step 2" reference: either introduce explicit "Step 1 / Step 2" headers above the connection subsections or relabel "1b" to a self-contained "Wait for the connection to be ready" heading.

Add a short validation checkpoint after `membrane action run` and proxy requests (e.g. "Check the `output`/response field; if `state` is not READY or the response errors, re-poll or inspect the `error` field") to satisfy the batch/remote-operation feedback-loop guidance.

Trim the opening "Waylay is a low-code automation platform..." paragraph to a single clause plus the docs link, since Claude can derive platform background from the documentation URL.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with minimal padding; the only over-explanation is the opening "Waylay is a low-code automation platform..." paragraph that Claude could derive from the docs link.	4 / 5
Actionability	It provides copy-paste-ready membrane commands, a proxy flag table, and a concrete state-machine walkthrough; minor gaps remain around templated placeholders like --intent "QUERY" and CONNECTION_ID that need user-specific values.	4 / 5
Workflow Clarity	The install -> auth -> connect -> poll-state -> search -> run sequence is clear with a polling feedback loop for connection readiness, but the dangling "Step 2" reference (a "1b" subsection with no matching "Step 1/2" headers) and the absence of a verify-after-run checkpoint keep it just below 5.	4 / 5
Progressive Disclosure	The single self-contained file is well organized into clear sections with no broken or nested references; it stays just below 5 only because no bundle files exist to offload the detailed proxy/state-machine reference, which is acceptable but inline for a focused CLI skill.	4 / 5
	Total	16 / 20 Passed

Description

62%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 is solid third-person prose that answers both what and when and is anchored by a distinctive brand name, but its actions and triggers are generic and narrow. Expanding trigger synonyms and listing more concrete actions would lift it from good to excellent.

Suggestions

Replace generic verbs with concrete actions, e.g. "Query and update Waylay resources, manage thing/property-set records, and run automation flows" rather than "Manage data, records, and automate workflows".

Broaden the trigger clause with natural synonyms and resource names users would say, e.g. "Use when the user wants to interact with Waylay data, manage IoT things, run or inspect automation flows, or query property sets."

Keep the explicit "Use when..." clause (it already satisfies the completeness requirement) and ensure it stays in third person.

Dimension	Reasoning	Score
Specificity	Names the Waylay domain and a few actions ("Manage data, records, and automate workflows"), but the actions are broad and generic rather than the granular, concrete actions of a 4 or 5.	3 / 5
Completeness	It explicitly states both what (Waylay integration; manage data, records, automate workflows) and when ("Use when the user wants to interact with Waylay data"), though the when clause could be more specific about automation triggers.	4 / 5
Trigger Term Quality	The only natural trigger is "interact with Waylay data"; it has a relevant keyword but lacks common variations, synonyms, or file extensions, matching the anchor for missing common variations.	3 / 5
Distinctiveness Conflict Risk	The "Waylay" brand name gives it a clear niche with minimal conflict risk, but the generic action verbs (manage data, records) leave minor overlap with related data-integration skills.	4 / 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/waylay/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.