Name: otter-waiver
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

otter-waiver

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/otter-waiver/SKILL.md

Quality

Content

61%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 skill delivers highly actionable, executable Membrane CLI commands with a well-structured connection workflow, but it is held back by padded prose, a broken "Step 2" cross-reference, and absent post-action verification.

Suggestions

Fix the dangling "skip to Step 2" reference by either labeling the next section as Step 2 or rewording to "proceed to Searching for actions."

Trim explanatory filler (the intro paragraph, "rather than auth plumbing") to tighten token efficiency.

Add a brief verification step after running actions, e.g. inspecting the `output` field or confirming the returned state, especially for operations that create or modify waiver records.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but contains padded prose such as the product intro paragraph and "so you can focus on the integration logic rather than auth plumbing" that Claude does not need.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action run, request) plus a flags table, but the action-run examples rely on placeholders rather than a fully concrete end-to-end example.	4 / 5
Workflow Clarity	The connection flow has good state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED polling), but "skip to Step 2" references a non-existent Step 2 and there is no verification step after running actions on waiver data.	3 / 5
Progressive Disclosure	The body is organized into clear sections (Install, Authentication, Connecting, Searching, Running, Proxy, Best practices) with content appropriately inlined for a single-purpose CLI integration guide; no bundle files are present or needed.	4 / 5
	Total	14 / 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 clearly identifies the product niche and provides an explicit use-when trigger, but its action language is generic and it omits the natural domain vocabulary (waivers, signers, templates) that users would actually say.

Suggestions

Replace generic verbs with concrete Otter Waiver actions, e.g. "Create and distribute waivers, manage signers and fields, and automate waiver workflows."

Expand the trigger clause with natural domain terms: "Use when the user wants to create or send waivers, collect signatures, or manage waiver templates and signer records."

Add the key domain nouns (waivers, templates, signers, fields) that already appear in the body's Overview so the description matches user vocabulary.

Dimension	Reasoning	Score
Specificity	It names the domain (Otter Waiver) and a few actions ("Manage data, records, and automate workflows"), but the actions are generic ("manage data") rather than concrete Otter Waiver operations like creating waivers or managing signers.	3 / 5
Completeness	Both a clear "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Otter Waiver data") are present, but the "when" is generic and could name concrete trigger phrases.	4 / 5
Trigger Term Quality	It includes the core brand keyword ("Otter Waiver") and "interact with Otter Waiver data" as a trigger, but misses the natural domain terms users would actually say such as waivers, signers, templates, or fields.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to the specific Otter Waiver product gives it a clear niche with low conflict risk, though the generic "manage data" phrasing leaves minor overlap with other data-management 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/otter-waiver/SKILL.md
Commit: f484c82

Reviewed: 5 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.