CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fal-train

Train custom AI models (LoRA) on fal.ai for personalized image generation tailored to a brand, character, or style.

51

Quality

64%

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

Quality

Content

47%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 lean, well-sectioned catalogue stub, but it delegates essentially all operational content to an external GitHub URL with no concrete install steps or verification. Converting the pointer into executable commands (clone, install path, post-install check) would substantially raise actionability and workflow clarity.

Suggestions

Replace the 'open <URL>' hint with concrete install commands, e.g. 'git clone https://github.com/fal-ai-community/skills <skills-dir>/fal-train' plus the actual target path for the active agent.

Add a validation checkpoint after installation, e.g. verify 'fal-train/SKILL.md exists and the triggers match the frontmatter' before telling the user to invoke it.

Drop the 'What it does' and 'Source' sections that duplicate the frontmatter description and metadata, or fold them into a single line, to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is short (~25 lines), sectioned, and free of concept explanations Claude already knows — near the 'lean and efficient' anchor. It drops below 5 because 'What it does' and 'Source' repeat the frontmatter description and metadata verbatim, which is redundant token spend.

4 / 5

Actionability

The only executable content is a comment plus 'open https://github.com/fal-ai-community/skills', and the core instruction — 'install the upstream bundle into your active agent's skills directory' — is a high-level hint with no concrete steps (no clone command, no target path), matching 'minimal concrete guidance; high-level hints but missing the specific steps to execute'. It is above score 1 only because a real URL and a runnable command are present.

2 / 5

Workflow Clarity

A rough sequence exists (inspect upstream README → install bundle → invoke by name), but each step is loosely defined ('install the upstream bundle' is underspecified) and there are no validation checkpoints confirming the skill actually installed before invoking it, matching the 'rough sequence present but many gaps; validation absent' anchor.

2 / 5

Progressive Disclosure

As a short single-purpose catalogue entry with well-organized sections ('What it does', 'Source', 'How to use'), it satisfies the simple-skill guideline for good structure. It falls short of 5 because the sole 'reference' is an external website URL rather than a bundled, verifiable local reference — no references/, scripts/, or assets/ exist in the bundle — so navigation depends on an out-of-tree resource the agent cannot reliably resolve.

4 / 5

Total

12

/

20

Passed

Description

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

A crisp, third-person description with a well-defined niche and strong natural keywords, but it only states one action and entirely omits 'when to use' guidance, which caps its completeness. Adding an explicit 'Use when...' clause with trigger synonyms would move it into the top tier.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user wants to fine-tune an image model, train a LoRA on fal.ai, or generate images in a consistent brand/character/style.'

Broaden natural synonyms such as 'fine-tune', 'custom model', and 'custom image generation' to lift trigger-term coverage.

Optionally enumerate 2-3 concrete sub-capabilities (e.g., dataset upload, launching a training queue, using the trained LoRA endpoint) to raise specificity.

DimensionReasoningScore

Specificity

The description names a concrete domain and technique — 'Train custom AI models (LoRA) on fal.ai' — with several tailoring targets ('brand, character, or style'), but it lists only one action (training) rather than several distinct capabilities, matching the 'names domain and 1-2 concrete actions' anchor. It sits below the score-4 anchor because there is no list of multiple specific actions such as dataset prep, queueing a training run, or using the resulting model.

3 / 5

Completeness

The 'what' is clear ('Train custom AI models (LoRA) on fal.ai for personalized image generation tailored to a brand, character, or style'), but there is no 'Use when...' clause or equivalent explicit trigger guidance inside the description, which caps completeness at 3 per the judging guidelines. The frontmatter's separate triggers list cannot substitute for explicit 'when' guidance in the description.

3 / 5

Trigger Term Quality

Natural phrases users would say appear directly: 'Train', 'LoRA', 'fal.ai', 'personalized image generation', 'brand', 'character', 'style' — good keyword coverage consistent with the score-4 anchor. It falls short of score 5 because common synonyms like 'fine-tune', 'custom model', or 'style transfer' are absent from the description text itself (they appear only in the separate triggers field).

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — LoRA training specifically on fal.ai — with distinct terms ('LoRA', 'fal.ai', 'brand') that few other skills would share, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor. It is not score 4 because the platform and technique naming leaves virtually no overlap with generic image-generation or document skills.

5 / 5

Total

15

/

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.

Validation — 15 / 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

Path

skills/fal-train/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.