Name: wistia
Rating: 56.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

wistia

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

Quality

65%

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/wistia/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, command-driven guide with concrete executable CLI examples, a clear connect-to-run workflow, and state-based polling feedback loops. Its main weaknesses are mild verbosity from value-proposition prose and inconsistent step numbering that muddies the workflow sequence.

Suggestions

Trim explanatory prose (the Wistia definition, Membrane value props, 'this is the fastest way') to keep the body lean and command-focused.

Fix the step numbering: the body references 'Step 2' and uses '1b' but never defines a Step 1/2 header — relabel with a consistent explicit sequence.

Show one fully-resolved example with real values (e.g. a concrete action id and intent) so the action-run path is copy-paste ready rather than placeholder-only.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-driven content, but includes several unnecessary explanatory sentences (what Wistia is, Membrane's value proposition, 'this is the fastest way') that could be trimmed.	3 / 5
Actionability	Provides concrete, executable CLI commands with flags throughout (install, login, connection, action list/run, proxy), though several use placeholders (`<actionId>`, `CONNECTION_ID`, `QUERY`) requiring substitution.	4 / 5
Workflow Clarity	Clear sequenced workflow (connect -> poll for READY -> search -> run) with state-based branching and a polling feedback loop, though step numbering is inconsistent ('Step 2' referenced without a matching header) and validation of action results is implicit.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and no problematic nesting; all content lives inline in one file (no bundle files exist), which is appropriate for this scope, with minor organization gaps.	4 / 5
	Total	15 / 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 correctly includes both a 'what' and a 'Use when' trigger clause tied to the distinct Wistia brand, but the stated capabilities ('manage data, records, automate workflows') are generic and lack concrete, task-specific keywords like videos, media, or statistics.

Suggestions

Replace generic capability verbs with concrete Wistia actions, e.g. 'Manage videos, projects, media statistics, and share links. Automate workflows.'

Expand the trigger clause with natural task phrases users would say, e.g. 'Use when the user wants to manage Wistia videos, projects, media stats, or share links.'

Add common synonyms/extensions (videos, media, .wistia) to the trigger to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the Wistia domain plus several actions ('manage data, records, automate workflows'), but the actions are generic rather than concrete capabilities.	3 / 5
Completeness	Both 'what' (manage data/records/workflows) and 'when' (use when user wants to interact with Wistia data) are present, but neither is highly specific.	4 / 5
Trigger Term Quality	The only natural keyword is the brand name 'Wistia'; it lacks task-level synonyms (videos, media, projects, statistics) users would actually say.	3 / 5
Distinctiveness Conflict Risk	The Wistia brand name gives it a clear, distinct niche with minimal conflict risk, though the action phrasing ('interact with data') is generic.	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/wistia/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.