Name: waiverforever
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

waiverforever

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

Quality

61%

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

Quality

Content

57%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 actionable and reasonably well-structured around the Membrane CLI workflow, but it is weakened by a broken step numbering, missing verification steps for destructive operations, and no progressive disclosure into separate reference files.

Suggestions

Fix the workflow numbering: label the connection steps consistently and define the referenced "Step 2" (searching/running actions).

Add explicit validation/verification after running actions or proxy writes, e.g. check the response `output`/error fields and retry on failure.

Move the proxy flag table and clientAction field reference into a separate REFERENCE.md and link to it from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete CLI commands, but the introductory paragraph explaining what WaiverForever is and the duplicated action-list command in "Popular actions" could be tightened.	3 / 5
Actionability	It provides concrete, copy-pasteable commands (login, connection ensure, action list/run, request) with flags and a documented proxy options table, with only minor gaps such as unresolved placeholders.	4 / 5
Workflow Clarity	The connection flow is sequenced with state-based branching and polling, but it references an undefined "Step 2", uses inconsistent numbering (1b with no 1a), and lacks validation/verification steps for destructive action runs and proxy writes, capping it at 3.	3 / 5
Progressive Disclosure	The content is organized with clear section headers, but it is a single inline file with no bundle references, and reference-style detail (clientAction fields, the proxy flag table) is inlined rather than split into deeper files.	3 / 5
	Total	13 / 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 is well-formed with an explicit "Use when" clause and a clearly distinct product niche, but its action list and trigger terms are generic and miss the natural vocabulary (waivers, templates, kiosks) users would actually say.

Suggestions

Replace generic verbs with concrete WaiverForever actions, e.g. "Create and send waiver templates, track signed documents, and manage kiosks".

Add natural trigger terms users say, such as "waiver", "sign a waiver", "waiver templates", and "kiosks".

Tighten the "Use when" clause to reference those concrete triggers, e.g. "Use when the user wants to create, send, or track waivers in WaiverForever".

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the WaiverForever domain and a couple of actions, but the actions are generic rather than concrete (e.g., no mention of templates, kiosks, or documents).	3 / 5
Completeness	It states both a clear "what" (manage data, records, automate workflows) and an explicit "when" ("Use when the user wants to interact with WaiverForever data"), though the trigger clause could be more specific.	4 / 5
Trigger Term Quality	It includes the brand term "WaiverForever" and "data, records, workflows" but omits the natural terms users actually say such as "waiver", "sign a waiver", "waiver templates", or "kiosks".	3 / 5
Distinctiveness Conflict Risk	"WaiverForever" is a distinct, named product niche with triggers unlikely to collide with other skills, giving minimal conflict risk.	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/waiverforever/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.