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

Blog Docs Log in Get started

vimeo

Vimeo integration. Manage Videos. Use when the user wants to interact with Vimeo 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

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/vimeo/SKILL.md

Quality

Content

75%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 copy-paste-ready Membrane commands and a well-structured connection workflow including validation checkpoints. Its main weaknesses are an unnecessary introductory explanation of Vimeo and a large inlined actions table that could live in a separate reference file.

Suggestions

Remove or condense the 'Vimeo is a video hosting and sharing platform...' intro paragraph; Claude already knows what Vimeo is.

Move the full popular-actions table to a references file (e.g. ACTIONS.md) and keep only a few representative examples inline.

Add an explicit validation/confirmation note for destructive actions (delete-video, delete-channel, etc.) so the workflow clarity cap is lifted.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and tables, but opens with unnecessary explanation of what Vimeo is ('Vimeo is a video hosting and sharing platform, similar to YouTube...') that Claude already knows; not a 4 because that padding and some auth-plumbing prose could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready commands for install, login, connection ensure/get, action list, action run (with JSON input), and proxy requests, plus a flag table and a popular-actions table with real keys; not lower because the common cases are concretely covered.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a re-poll feedback loop; not a 5 because step references ('Step 2', '1b') are slightly inconsistent and destructive actions (delete-*) are listed without validation guidance.	4 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and a flat structure; not a 5 because the large 20-row popular-actions table is inlined rather than split to a reference file, a minor organization gap for a skill over 50 lines.	4 / 5
	Total	16 / 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 covers both what the skill does and when to use it with a clear, distinct Vimeo niche, but the 'what' is thin (a single generic action) and trigger term coverage is limited to two terms. It is functional but could be more specific and comprehensive.

Suggestions

Expand the 'what' with concrete actions, e.g. 'List, search, create, update, and delete videos, channels, albums, and projects on Vimeo.'

Broaden trigger terms to include synonyms and surface forms users say, such as 'Vimeo videos, channels, albums, showcases, or vimeo.com links'.

Keep the explicit 'Use when...' clause but tie it to specific intents like uploading, organizing, or retrieving Vimeo video details.

Dimension	Reasoning	Score
Specificity	Names the Vimeo domain plus a single concrete action ('Manage Videos'), matching the anchor that lists domain and 1-2 actions but is not comprehensive; not a 2 because an explicit action is named, not a 4 because no additional specific actions are enumerated.	3 / 5
Completeness	Both 'what' ('Vimeo integration. Manage Videos.') and 'when' ('Use when the user wants to interact with Vimeo data.') are present and explicit; not a 5 because the 'what' is thin and lacks concrete trigger phrases beyond the single 'when' clause.	4 / 5
Trigger Term Quality	Includes natural terms 'Vimeo' and 'Videos' that users would say, but misses common synonyms and file/URL variations; not a 4 because coverage is limited to two terms with no extensions or alternates.	3 / 5
Distinctiveness Conflict Risk	Vimeo is a clearly distinct platform niche with unambiguous triggers, giving minimal conflict risk with other skills; not lower because the platform name itself disambiguates.	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/vimeo/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.