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

waratek

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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/waratek/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 delivers concrete, executable Membrane CLI guidance with a well-validated connection workflow and clean section structure. Its main weaknesses are mild verbosity in the intro/transition prose, an unresolved "Step 2" reference, and an abstract entity-discovery list.

Suggestions

Define or remove the dangling "Step 2" reference so the connection workflow is self-contained.

Trim concept-level padding such as the RASP audience sentence and the "auth plumbing" aside; keep only what aids execution.

Make the entity list actionable by mapping each entity to the action verb or command used to manage it, instead of the generic "Use action names and parameters as needed".

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and code-heavy, but includes unnecessary explanation such as "Security teams and DevOps engineers use it to prevent attacks" and "so you can focus on the integration logic rather than auth plumbing", plus a 15-item entity list closed with the vague "Use action names and parameters as needed." This matches anchor 3 (mostly efficient with some unnecessary explanation) rather than 4, which would require only minor trim opportunities.	3 / 5
Actionability	Concrete, executable commands are given throughout (e.g. `npm install -g @membranehq/cli@latest`, `membrane connection ensure "https://www.waratek.com" --json`, `membrane action run <actionId> --connectionId=CONNECTION_ID --json`) with a clear proxy-options table. It sits at 4 rather than 5 because placeholders like `<actionId>` and `CONNECTION_ID` need substitution and the entity/action-discovery section stays abstract.	4 / 5
Workflow Clarity	The connection workflow is sequenced with explicit validation checkpoints and a feedback loop (poll with `--wait`, branch on READY/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR, re-poll after the user acts). It reaches 4 rather than 5 because of a dangling "skip to Step 2" reference whose Step 2 is never defined, leaving a minor navigation gap.	4 / 5
Progressive Disclosure	Content is organized into clear headed sections (Overview, Install, Authentication, Connecting, Searching, Popular actions, Proxy, Best practices) in a single file with no bundle files present. This fits anchor 4 (good structure, minor organization gaps); it is not 5 because the 150-line single-file scope and inlined entity/proxy reference material could be split out, and not 3 because the sectioning is consistent and navigable.	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 answers both what and when with an explicit trigger clause and leverages a distinctive product name, but its action language is generic and its keyword coverage lacks variations. Strongest on distinctiveness, weakest on specificity and trigger breadth.

Suggestions

Replace generic verbs with concrete Waratek operations, e.g. "manage agents, agent rules, vulnerabilities, and licenses".

Broaden trigger terms to include natural synonyms a user might say, such as "Waratek agents, rules, vulnerabilities, or security policies".

Tighten the "when" clause to enumerate the specific Waratek tasks that should activate the skill.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Waratek domain and several action areas, but the actions are generic rather than concrete (no specific operations like 'create agent rules' or 'scan vulnerabilities'). It clears anchor 3 over anchor 2 because it enumerates multiple action categories, but falls short of 4 since none are specific.	3 / 5
Completeness	It states both a what ("Waratek integration. Manage data, records, and automate workflows.") and an explicit when ("Use when the user wants to interact with Waratek data."), so it is not capped at 3 by the missing-trigger guidance. It lands at 4 rather than 5 because the "when" clause is somewhat narrow and the "what" is generic.	4 / 5
Trigger Term Quality	Natural keywords include "Waratek", "data", "records", and "workflows", plus the trigger phrase "interact with Waratek data". It matches anchor 3 — relevant keywords present but missing common variations or synonyms (no file types, no alternate product phrasings) — rather than 4 which would need broader natural-term coverage.	3 / 5
Distinctiveness Conflict Risk	"Waratek" is a unique named product, giving it a clear niche with distinct, product-specific triggers unlikely to fire for unrelated skills. This matches anchor 5; it is not 4 because the trigger is product-bound rather than merely "mostly distinct".	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/waratek/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.