CtrlK
BlogDocsLog inGet started
Tessl Logo

fal-kling-o3

Generate images and videos with Kling O3 — Kling's most powerful model family — via fal.ai.

49

Quality

53%

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-kling-o3/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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 lean, well-organized catalogue pointer, but it delegates essentially all actionable content to an external upstream repo and provides no concrete install or generation steps, leaving it descriptive rather than instructive.

Suggestions

Replace the bare `open <url>` with concrete, executable steps for installing the upstream bundle into the skills directory (or vendor the key reference files locally).

Add at least one minimal, copy-paste-ready example of invoking Kling O3 generation via fal.ai so the skill is actionable on its own.

Cut the frontmatter-duplicating "What it does" and "Source" sections and the meta prose about Open Design to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is short and free of concept over-explanation, but "What it does" and "Source" duplicate the frontmatter and the "catalogue entry advertises the skill in Open Design" prose is mild padding that could be tightened.

2 / 3

Actionability

The only concrete command is `open https://github.com/fal-ai-community/skills`, which merely opens a browser; there is no executable guidance for the actual image/video generation task, so the guidance is concrete but incomplete and missing all key details.

2 / 3

Workflow Clarity

A loose prose sequence exists (inspect upstream README, install the bundle, invoke by name or trigger), but the install step is abstract and there are no validation checkpoints, leaving the workflow implicit rather than concrete.

2 / 3

Progressive Disclosure

Sections are well organized and the file is short, but there are no local reference files; all substantive content is delegated to an external GitHub URL rather than structured as one-level-deep local references.

2 / 3

Total

8

/

12

Passed

Description

57%

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 specific and clearly occupies a distinct niche (Kling O3 via fal.ai), but it lacks explicit "Use when..." trigger guidance and the natural trigger phrases are split off into a separate frontmatter field rather than woven into the description.

Suggestions

Add an explicit "Use when..." clause naming the trigger scenarios (e.g., "Use when generating Kling O3 images or videos via fal.ai").

Fold the natural trigger phrases ("fal kling", "kling video", "kling image") into the description so it carries its own trigger coverage.

Enumerate the concrete generation actions (image generation, video generation, and any modes/endpoints) to lift specificity toward comprehensive.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ("Generate images and videos ... via fal.ai") but does not list multiple distinct operations, so it stops short of comprehensive.

2 / 3

Completeness

It clearly states what the skill does but lacks any "Use when..." clause or explicit trigger guidance, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

The description includes relevant keywords ("images", "videos", "Kling O3", "fal.ai") but the natural phrase variations ("fal kling", "kling video", "kling image") live only in the separate triggers field, not the description text.

2 / 3

Distinctiveness Conflict Risk

"Kling O3 ... via fal.ai" names a clear, specific niche with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

9

/

12

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.