CtrlK
BlogDocsLog inGet started
Tessl Logo

fal-lip-sync

Create talking head videos and lip sync audio to video via fal.ai. Useful for explainer avatars, multilingual dubbing previews, and social cuts.

52

Quality

57%

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 ./skills/fal-lip-sync/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a well-organized but content-light catalogue entry that defers essentially all real guidance to an upstream repository. It is concise and cleanly structured but offers little actionable or workflow-specific value on its own.

Suggestions

Replace the browser-opening `open` command with a concrete install step (e.g., `git clone` into the skills directory or the exact `claude skill add` invocation) to raise actionability.

Inline a minimal runnable example of the lip sync call (e.g., the fal.ai endpoint and required inputs) so the skill is useful before the upstream bundle is installed.

Add an explicit validation checkpoint after the install step (e.g., verify the skill appears in the skills list) to give the workflow a real checkpoint.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with no concept over-explanation; the only minor trim opportunity is that the "What it does" section repeats the frontmatter description verbatim, keeping it just below a 5.

4 / 5

Actionability

The only concrete command is `open https://github.com/...` (which merely opens a browser) plus a high-level "install the upstream bundle" instruction; the specific steps to actually perform lip sync are entirely deferred, matching the minimal-concrete-guidance anchor.

2 / 5

Workflow Clarity

A rough sequence is present (inspect upstream README, install bundle, invoke by name/trigger) but it defers specifics to the upstream README and has no checkpoints, fitting the "sequence present but checkpoints missing or implicit" anchor rather than the simple-skill 5 since the workflow is underspecified.

3 / 5

Progressive Disclosure

The short body is well-organized into clear sections and points to a single one-level-deep reference (the upstream repo), but because all real skill content lives externally rather than in a structured local bundle there is a minor organization gap, holding it at 4 rather than 5.

4 / 5

Total

13

/

20

Passed

Description

61%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 clearly states what the skill does and targets a specific niche, but it relies on use-case framing rather than an explicit "Use when..." trigger clause and lists only two concrete actions. It is solid but not exemplary.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when the user wants to lip sync audio to a face video or create a talking head avatar") to lift completeness above 3.

List one or two more concrete actions (e.g., "swap the audio track on an existing video", "render an avatar from a still image plus audio") to push specificity toward 4-5.

Add a couple of natural synonyms (e.g., "voiceover to video", "mouth sync") to round out trigger term coverage.

DimensionReasoningScore

Specificity

Names two concrete actions ("Create talking head videos", "lip sync audio to video via fal.ai") but offers no further coverage, matching the 1-2 concrete actions anchor rather than the "several" required for a 4.

3 / 5

Completeness

The "what" is clear ("Create talking head videos and lip sync audio to video via fal.ai") but the "when" is only weakly implied through use-case framing ("Useful for explainer avatars, multilingual dubbing previews, and social cuts") rather than an explicit "Use when..." trigger clause, so it is capped at 3 per the guideline.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("talking head videos", "lip sync", "audio to video", "avatars", "dubbing") giving good coverage, but common synonyms like "voiceover to video" or "mouth sync" are missing so it is not comprehensive (5).

4 / 5

Distinctiveness Conflict Risk

Names a specific service (fal.ai) and a focused niche (lip sync / talking head) with distinct triggers, giving mostly distinct positioning with only minor overlap risk against general video-generation or avatar skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.