Name: heygen
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

heygen

HeyGen integration. Manage Videos, Avatars, Templates. Use when the user wants to interact with HeyGen data.

Quality

61%

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/heygen/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 body is a strongly actionable CLI integration guide with concrete commands and a clear connection-state workflow. It loses points for trimmable explanatory prose, broken step numbering, and the absence of validation before destructive action runs.

Suggestions

Fix the step numbering: replace "skip to Step 2" with a real labeled "Step 2" (and add a "1a" alongside the existing "1b") so the sequence is unambiguous.

Add a validation checkpoint before destructive/batch action runs, e.g. confirm the target video id via get-video-status before running delete-video.

Trim the opening HeyGen marketing paragraph and filler lines ("Use action names and parameters as needed.") to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient CLI commands, but the opening paragraph explaining what HeyGen is and filler like "Use action names and parameters as needed." and the "so you can focus on the integration logic rather than auth plumbing" aside could be trimmed.	3 / 5
Actionability	Copy-paste-ready commands are provided throughout (install, login, connection ensure, action run with --input, proxy with full flag table) plus a popular-actions table; minor gaps remain in that placeholders like <actionId> are never shown in a fully worked example.	4 / 5
Workflow Clarity	The connection flow has explicit states and a poll-again feedback loop, but step numbering is broken ("skip to Step 2" with no Step 2; "1b" with no "1a") and destructive actions (delete-video, translate-video) run with no validation, triggering the destructive/batch cap at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the skill is self-contained with well-organized sections; at over 50 lines the simple-skill 5-exception does not apply, so good structure with minor organization gaps lands at 4.	4 / 5
	Total	14 / 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 cleanly states both what the skill does and when to use it, anchored to a distinct named product. Its main weakness is the generic "Manage" verb and a "when" clause ("interact with HeyGen data") that lacks concrete natural-language trigger phrases.

Suggestions

Replace the generic verb "Manage" with concrete actions, e.g. "List, generate, translate, and delete HeyGen videos and manage avatars and templates."

Strengthen the trigger clause with natural phrases users would say, e.g. "Use when the user wants to create or translate HeyGen videos, generate avatar videos, or list HeyGen templates and voices."

Dimension	Reasoning	Score
Specificity	"Manage Videos, Avatars, Templates" names the domain and several concrete targets, but the single generic verb "Manage" does not enumerate distinct specific actions, matching anchor 3 rather than 4.	3 / 5
Completeness	Both what ("Manage Videos, Avatars, Templates") and when ("Use when the user wants to interact with HeyGen data") are present, but the when clause is generic rather than concrete trigger phrases, so it is not a 5.	4 / 5
Trigger Term Quality	Relevant keywords ("HeyGen", "Videos", "Avatars", "Templates") are present, but "interact with HeyGen data" is not a natural user phrase and common synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	"HeyGen integration" targets a clear named-product niche with minimal conflict risk, but the weak trigger guidance keeps it just below the strongest distinctiveness anchor.	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/heygen/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.