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

warpwire

Warpwire integration. Manage data, records, and automate workflows. Use when the user wants to interact with Warpwire 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/warpwire/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 is a well-structured, actionable guide to driving Warpwire through the Membrane CLI, with strong command coverage and genuine validation checkpoints in the connection workflow. Its main weaknesses are minor redundancy and padding, an unlabeled 'Step 2' reference, and the absence of a complete worked example.

Suggestions

De-duplicate the action-discovery command: keep it once under 'Searching for actions' and have 'Popular actions' reference it or list concrete example intents instead.

Label the workflow steps consistently (1a/1b/2) so the 'skip to Step 2' reference resolves to an actual header.

Add one fully-worked end-to-end example with realistic values (connect, list, run) so the actionability gap from placeholders is closed.

Dimension	Reasoning	Score
Conciseness	Mostly efficient CLI command examples, but the 'membrane action list --intent=QUERY' command is shown twice (Searching for actions and Popular actions) and the intro ('Users include educators, students, and staff...') plus 'so you can focus on the integration logic rather than auth plumbing' add padding that could be trimmed.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands for install, login, connection ensure, action search/run, and proxy requests with a flag table, but relies on placeholders (CONNECTION_ID, <agentType>, QUERY, <actionId>) and offers no fully-worked end-to-end example.	4 / 5
Workflow Clarity	Clear install → authenticate → connect → poll-for-ready → search → run sequence with state-check validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a retry-after-action feedback loop, but the referenced 'Step 2' has no labeled header and the action-running phase lacks validation guidance.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Overview, Working with Warpwire, Authentication, Connecting, Searching, Running actions, Proxy requests, Best practices) with no external references needed for a CLI-wrapper skill, though the 'Popular actions' section duplicates earlier content and the inline hierarchy could be tightened.	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 correctly follows the what+when pattern with an explicit 'Use when' trigger and is highly distinct thanks to the unique product name. Its weakness is generic, non-concrete action language and a thin set of trigger terms that omit the domain's natural vocabulary (video, media, collection).

Suggestions

Replace generic verbs with concrete Warpwire capabilities, e.g. 'Manage Warpwire media assets, collections, users, and groups; automate video workflows.'

Expand the 'Use when' clause with natural trigger phrases users actually say, e.g. 'Use when the user wants to manage Warpwire videos, media assets, collections, or user/group records.'

Add domain keywords (video, media, library, collection) so the description surfaces for the terms users naturally mention.

Dimension	Reasoning	Score
Specificity	Names the domain (Warpwire) and lists three actions ('Manage data, records, and automate workflows'), but the actions are generic rather than concrete to Warpwire's actual video/media/library capabilities, so coverage is not comprehensive.	3 / 5
Completeness	Explicitly answers both what ('Warpwire integration. Manage data, records, and automate workflows.') and when ('Use when the user wants to interact with Warpwire data.'), though the when-clause is generic rather than listing concrete trigger phrases.	4 / 5
Trigger Term Quality	Includes one natural keyword a user would say ('Warpwire') in 'Use when the user wants to interact with Warpwire data', but misses common variations and synonyms users would actually use (video, media, library, collection).	3 / 5
Distinctiveness Conflict Risk	'Warpwire' is a unique product name giving a clear niche, and the trigger ('interact with Warpwire data') is distinct with minimal risk of matching an unrelated skill.	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/warpwire/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.