Name: vidizmo
Rating: 60 (1 reviews)
Author: membranedev

vidizmo

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

Quality

70%

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/vidizmo/SKILL.md

Quality

Content

82%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 highly actionable with executable commands and a well-sequenced, state-driven connection workflow, supported by clean section structure. Its main gaps are a light over-explanation of Membrane auth mechanics and the absence of an explicit validation/retry loop around action runs.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient and command-driven, with only minor over-explanation such as "Membrane handles authentication and credentials refresh automatically" that restates CLI behavior rather than assuming Claude's competence.	4 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (login, connection ensure, polling, action list/run, proxy requests) plus a concrete flag reference table.	5 / 5
Workflow Clarity	The connection flow has a clear sequence with explicit state-based checkpoints (READY / BUILDING polling / CLIENT_ACTION_REQUIRED handling), but there is no validate-then-proceed feedback loop for the destructive/batch action runs that the skill ultimately enables.	4 / 5
Progressive Disclosure	Content is well organized into clear sections (Install, Authentication, Connecting, Searching, Popular actions, Best practices) with no nested references, but there are no bundle files or external references, so it is structured rather than split for progressive disclosure.	4 / 5
	Total	17 / 20 Passed

Description

57%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 pairs a clear 'what' with an explicit 'when' trigger and is anchored to a distinct VIDIZMO niche, but its capability list is generic and its trigger phrasing lacks natural synonyms or file/term variations. Tightening the action verbs and broadening trigger terms would lift specificity and trigger quality.

Suggestions

Replace generic verbs with concrete VIDIZMO actions, e.g. "Search and play videos, manage channels and playlists, review analytics" instead of "Manage data, records, and automate workflows".

Broaden the trigger phrase with natural terms users would say, e.g. "Use when the user wants to search, play, or manage VIDIZMO videos, channels, playlists, or analytics".

Drop the generic "automate workflows" claim unless a concrete automation capability is documented, to avoid over-claiming.

Dimension	Reasoning	Score
Specificity	The description names the domain ("VIDIZMO integration") but the stated actions are minimal and generic — "Manage data, records, and automate workflows" — without listing concrete operations like ingest, search, or playlist management.	2 / 5
Completeness	It explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with VIDIZMO data"), though the 'when' clause is fairly generic and could be more specific.	4 / 5
Trigger Term Quality	It includes some relevant natural keywords ("VIDIZMO", "data", "records") but lacks common variations or synonyms a user would naturally say, so it falls below comprehensive coverage rather than at the minimal-generic level.	3 / 5
Distinctiveness Conflict Risk	The VIDIZMO-specific framing carves a clear niche with minimal conflict risk; it is mostly distinct, with only minor overlap risk against other generic data-management skills.	4 / 5
	Total	13 / 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/vidizmo/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.