Name: jw-player
Rating: 58.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

jw-player

JW Player integration. Manage Medias, Playlists, Players. Use when the user wants to interact with JW Player data.

Quality

67%

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/jw-player/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 content is highly actionable with concrete CLI commands and a clear connection workflow, but it carries some padded explanation and lacks validation steps for its destructive operations. Structure is good for a single-file skill.

Suggestions

Add a validation/verification step before destructive actions (e.g. re-fetch the resource and confirm with the user) plus a fix-and-retry loop, so delete/update workflows meet the feedback-loop requirement.

Trim the explanatory intro paragraph and the "rather than auth plumbing" aside to reduce token overhead.

Consider moving the 20-row popular-actions table into a separate references file linked from the body, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly commands and tables, but the intro ("Think of it as a customizable video player with analytics and advertising capabilities") and the auth aside ("so you can focus on the integration logic rather than auth plumbing") are unnecessary explanation that could be trimmed.	3 / 5
Actionability	It provides concrete, copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request proxy) with parameter examples, though full per-action invocation examples for the 20 listed actions are not shown.	4 / 5
Workflow Clarity	The connection setup is well-sequenced with polling and state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED), but destructive actions (delete-media, delete-playlist) appear only in a table with no validation or verification workflow, capping this dimension at 3.	3 / 5
Progressive Disclosure	The single file is organized into clear, navigable sections (Overview, Working with JW Player, Popular actions, Best practices) with no nested references, though the 20-row actions table is arguably bulk that could live in a separate reference file.	4 / 5
	Total	14 / 20 Passed

Description

73%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 clearly targeted at a named platform and includes an explicit trigger clause, giving it strong distinctiveness and decent completeness. Its main weakness is the generic verb "Manage" and the non-standard plural "Medias", which limit specificity and trigger naturalness.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "Create, list, update, and delete Media, Playlists, and Players", to raise specificity.

Use the standard plural "Media" instead of "Medias" so trigger terms match what users actually say.

Expand the "Use when" clause with concrete scenarios (e.g. managing videos, building playlists, configuring players) rather than the tautological "interact with JW Player data".

Dimension	Reasoning	Score
Specificity	"Manage Medias, Playlists, Players" names the domain and three concrete resource types, but applies a single generic verb ("Manage") rather than several distinct actions, so it is not comprehensive.	3 / 5
Completeness	Both "what" ("Manage Medias, Playlists, Players") and an explicit "when" ("Use when the user wants to interact with JW Player data") are present; the trigger is explicit but somewhat tautological and could name concrete scenarios.	4 / 5
Trigger Term Quality	Includes the natural terms a user would say ("JW Player", "Playlists", "Players", "interact with JW Player data") with good coverage, though it uses the non-standard plural "Medias" and omits some synonyms.	4 / 5
Distinctiveness Conflict Risk	"JW Player integration" targets a specific named platform with distinct triggers, giving it a clear niche and minimal overlap with other skills.	5 / 5
	Total	16 / 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/jw-player/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.