CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

heygen

[DEPRECATED] Use `create-video` for prompt-based video generation or `avatar-video` for precise avatar/scene control. This legacy skill combines both workflows — the newer focused skills provide clearer guidance.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/heygen/SKILL.md

The canonical home for this skill is heygen in calesthio/OpenMontage

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

A well-structured navigation-hub skill: concise routing tables, two clearly sequenced default workflows with explicit fallback criteria, and an exemplary progressive-disclosure layout where every reference link resolves to a real, flat, substantive file. The main gaps are minor — some duplication between the two tool tables and no error-recovery guidance for polling failures.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — routing tables, exact endpoint names, and pointers, with zero explanation of concepts Claude already knows. Minor duplication keeps it below 5: the MCP tools appear in both the 'Tool Selection' and 'Quick Reference' tables, `prompt-optimizer.md` is linked five times, and the deprecation notice repeats the frontmatter's wording.

4 / 5

Actionability

Guidance is concrete and executable: named MCP tools with their parameters ('duration_sec, orientation, avatar_id'), exact endpoints ('POST /v1/video_agent/generate', 'GET /v2/videos/{video_id}'), and the auth header ('X-Api-Key: $HEYGEN_API_KEY'). It falls short of 5 because no request-body or response examples appear in the body — a user must open the references to construct a complete call, which is acceptable but leaves minor gaps.

4 / 5

Workflow Clarity

The 'Default Workflow' gives clearly sequenced numbered steps for both the MCP and direct-API paths, with status polling ('poll status and get the download URL') acting as a natural checkpoint, and explicit criteria for when to fall back to the v2 API ('Only use v2/video/generate when user explicitly needs...'). Not 5: there is no error-recovery guidance (what to do on a failed video status, credit exhaustion, or polling timeout), so feedback loops are implicit rather than explicit.

4 / 5

Progressive Disclosure

The body is a clean routing overview: all 22 referenced files exist, are substantive (8,200+ lines total), and are exactly one level deep — cross-links among references point to flat siblings, never burying content in nested chains. Navigation is well-signaled via the 'Quick Reference' task table, per-path workflow pointers, and a categorized 'Reference Files' index. Every piece of detail (visual styles, scripts, captions, webhooks) is appropriately split out of SKILL.md.

5 / 5

Total

17

/

20

Passed

Description

50%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 a well-written deprecation redirect — brief, honest, and pointing users to the right successors — but judged on its own merits it fails as a skill description: it describes the replacement skills rather than this one, omits the 'HeyGen' product name and natural trigger phrases, and has no 'Use when' guidance. The redirect intent is appropriate for a deprecated skill, yet the trigger machinery would struggle to route relevant requests here or anywhere else from this text alone.

Suggestions

State what this skill does in its own terms before redirecting, e.g. 'Creates HeyGen AI avatar/talking-head videos from prompts or per-scene specs (deprecated).' — this would lift specificity and completeness.

Include natural trigger terms users actually say — 'HeyGen', 'AI avatar video', 'talking-head', 'explainer video' — so the description carries trigger weight even while deprecated (trigger_term_quality).

Add an explicit condition for when this skill still applies, e.g. 'Use only for backward compatibility when the focused skills are unavailable', which gives the missing 'when' clause (completeness).

DimensionReasoningScore

Specificity

The description names the domain and capability areas — 'prompt-based video generation' and 'precise avatar/scene control' — and states 'This legacy skill combines both workflows', but it never enumerates this skill's own concrete actions; the specific capabilities listed belong to the replacement skills, not this one. It is clearly not vague (rules out 1-2), but coverage of what this skill actually does is too thin for 4.

3 / 5

Completeness

The 'what' is only weakly implied ('This legacy skill combines both workflows' requires resolving what 'both' refers to), and there is no 'Use when...' or equivalent trigger clause — the only 'Use' phrasing ('Use `create-video`...') is a redirect to other skills, not usage guidance for this one. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural keywords like 'video', 'avatar', 'scene', and 'prompt' are present, but common variations and synonyms users would actually say are missing — notably 'HeyGen' itself, 'AI avatar video', 'talking-head', and 'explainer' (which the body covers). This matches the 'some relevant keywords but missing common variations' anchor; it never names the product, keeping it below 4.

3 / 5

Distinctiveness Conflict Risk

The niche (AI avatar video generation) is somewhat specific and the named replacement skills (`create-video`, `avatar-video`) help disambiguate within that family, but the description never mentions 'HeyGen' or 'talking-head video', so it could overlap with any generic video-generation skill. Somewhat specific with residual overlap risk — the anchor-3 fit; not 4 because the product name omission creates real conflict risk against unrelated video tools.

3 / 5

Total

12

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

12

/

16

Passed

Repository

calesthio/OpenMontage

Path

.claude/skills/heygen/SKILL.md

Reviewed

Table of Contents

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.