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

brightcove

Brightcove integration. Manage data, records, and automate workflows. Use when the user wants to interact with Brightcove 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

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/brightcove/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 strongly actionable CLI integration guide with concrete commands, a flag reference, and a robust connection-state feedback loop. Its main weaknesses are an over-explanatory intro paragraph, loose step numbering, and no validation guidance for action execution.

Suggestions

Trim the opening paragraph to one line — drop the 'YouTube for businesses' analogy and the audience description; Claude already understands what a video platform is.

Fix the step numbering so 'Step 2' is actually labeled, or remove the cross-references in favor of inline 'next:' cues.

Add a brief validation/check step before running write or batch actions (e.g., inspect the action's inputSchema and confirm scope with the user before destructive calls).

Dimension	Reasoning	Score
Conciseness	The opening paragraph over-explains a concept ('Brightcove is an online video platform… Think of it as a YouTube for businesses, but with more advanced features and analytics') and includes filler like 'Use action names and parameters as needed.', but the bulk is a tight command reference, fitting 'mostly efficient but includes some unnecessary explanation'.	3 / 5
Actionability	Copy-paste-ready commands throughout (install, login, connection ensure, action list/run, request) with a full flag table, but placeholders (CONNECTION_ID, actionId) and a 'Popular actions' section that only re-states the discovery command rather than naming actions leave minor gaps versus fully executable coverage.	4 / 5
Workflow Clarity	A clear install → authenticate → connect → search → run sequence with an explicit feedback loop for connection state (poll to READY, handle CLIENT_ACTION_REQUIRED, inspect CONFIGURATION_ERROR), but 'skip to Step 2' references an unlabeled step and there is no validation guidance before running potentially destructive/batch actions.	4 / 5
Progressive Disclosure	No bundle files exist and the ~145-line body is organized into clear, well-labeled sections with no nested references, but as a single inline file it offers no one-level-deep pointers to separate reference material, placing it below the anchor-5 'clear overview with well-signaled references'.	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 is well-formed: third-person voice, an explicit 'Use when…' clause, and a brand-specific trigger that distinguishes it from other skills. Its weaknesses are generic action verbs and narrow trigger keyword coverage that omit the video-platform vocabulary users would naturally say.

Suggestions

Replace generic verbs with concrete Brightcove capabilities, e.g. 'Manage videos, playlists, players, and live streams; run reports and automate workflows.'

Broaden trigger terms to include natural video-platform phrasing: 'Use when the user wants to manage Brightcove videos, playlists, live streams, or video analytics.'

Align the 'when' clause with the 'what' clause so it covers records and workflows, not just 'Brightcove data'.

Dimension	Reasoning	Score
Specificity	Phrases 'Manage data, records, and automate workflows' name several action areas but use generic verbs rather than concrete capabilities (no mention of videos, playlists, players, or live streams), sitting just above the anchor-2 'actions are minimal or generic' floor.	3 / 5
Completeness	It answers both 'what' ('Brightcove integration. Manage data, records, and automate workflows.') and 'when' ('Use when the user wants to interact with Brightcove data.'), but the 'when' is narrower than the 'what' (only mentions data, not records or workflows), so it falls short of the anchor-5 'concrete trigger phrases' bar.	4 / 5
Trigger Term Quality	The natural keyword 'Brightcove' and trigger clause 'Use when the user wants to interact with Brightcove data' are present, but coverage is narrow — missing common variations a user would say for a video platform ('video', 'video hosting', 'playlist', 'video platform').	3 / 5
Distinctiveness Conflict Risk	The brand-bound trigger 'interact with Brightcove data' is a distinct niche with low conflict risk, but the generic 'Manage data, records, and automate workflows' portion could theoretically overlap with a generic data-management or automation skill, keeping it just below anchor 5.	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/brightcove/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.