CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fal-vision

Analyze images — segment objects, detect, run OCR, describe, and answer visual questions via fal.ai vision models.

52

Quality

65%

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

Quality

Content

43%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 catalogue stub, not an operational skill: the body is concise and clearly structured but defers every substantive instruction to an external repository, leaving the agent with no executable guidance for the advertised vision-analysis tasks. Its only actionable content is a URL-open command and the skill's own name and triggers.

Suggestions

Add an executable quick-start (e.g., a concrete install command for the upstream bundle, or better, inline a minimal fal.ai API example for one task like OCR or object detection) so the agent can act without fetching an external repo.

Replace the vague 'install the upstream bundle into your active agent's skills directory' with a specific, copy-paste-ready sequence, and add a verification checkpoint confirming the skill is discoverable before instructing the agent to invoke it.

Deduplicate the upstream URL (frontmatter, 'Source' section, and bash block repeat it) and drop the zero-information 'Curated from...' blockquote to reach full token efficiency.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows. It falls short of the 5 anchor due to redundancy: the upstream URL appears in both the 'Source' section and the bash block (duplicating the frontmatter 'od.upstream'), and the 'Curated from the fal.ai community team' blockquote adds little — matching the 4 anchor ('minor instances that could be trimmed').

4 / 5

Actionability

The only concrete command is 'open https://github.com/fal-ai-community/skills', which merely opens a browser rather than performing the task, and the actual instruction — 'install the upstream bundle into your active agent's skills directory' — is a high-level hint with no specific steps or code. This matches the 2 anchor ('minimal concrete guidance; high-level hints but missing the specific steps'), not the 3 anchor, since there is no partially-complete executable guidance (no install command, no model invocation example).

2 / 5

Workflow Clarity

A rough sequence exists (inspect upstream README → install bundle → invoke by name or trigger), but steps are poorly defined — no install command, no paths, no verification that the skill was installed correctly. This matches the 2 anchor ('rough sequence present but many gaps; steps poorly defined; validation absent') rather than the 3 anchor, whose steps are at least concretely listed.

2 / 5

Progressive Disclosure

Sections ('What it does', 'Source', 'How to use') are well-organized and the upstream reference is clearly signaled one level deep, but no local bundle files exist (no references/, scripts/, or assets/), so all substantive detail is deferred to an external GitHub URL that cannot be navigated offline. This sits between the 3 anchor (some structure, references not fully serving navigation) and the 4 anchor — the total absence of local material and usable content pulls it to 3.

3 / 5

Total

11

/

20

Passed

Description

71%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 strong, lean description: third-person, specific, and comprehensive about capabilities. Its one structural weakness is the missing 'Use when...' trigger clause, which caps completeness; explicit trigger phrases exist only in the separate frontmatter 'triggers' field, not in the description itself.

Suggestions

Append a 'when' clause to the description, e.g. 'Use when the user mentions image analysis, OCR, object detection, segmentation, or visual questions, or references fal.ai vision models.'

Add natural synonyms or file extensions users would actually say (e.g., 'image recognition', '.png/.jpg') to broaden trigger-term coverage from good to comprehensive.

Mention the trigger phrases inside the description text itself so the description is self-contained for skill-matching, rather than relying solely on the separate frontmatter triggers list.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'segment objects, detect, run OCR, describe, and answer visual questions' — comprehensively covering the fal.ai vision-model task space. It matches the 5 anchor (multiple specific actions, comprehensive coverage) rather than the 4 anchor, which requires 'minor gaps in coverage' that aren't evident here.

5 / 5

Completeness

It has a clear 'what' (five concrete vision-analysis actions via fal.ai models) but no 'Use when...' clause or equivalent explicit trigger guidance inside the description, which caps completeness at 3 per the judging guidelines. It fits the 3 anchor ('clear what, when missing') and cannot be a 4 without any 'when' statement at all.

3 / 5

Trigger Term Quality

Natural keywords are present and relevant ('Analyze images', 'segment objects', 'run OCR', 'visual questions'), giving good keyword coverage. It falls short of the 5 anchor because common synonyms and file extensions users would say (e.g., 'image recognition', 'caption', '.png', '.jpg') are missing, but it is well above the 3 anchor's 'missing common variations' since several natural phrases are included.

4 / 5

Distinctiveness Conflict Risk

'via fal.ai vision models' names a specific platform, establishing a clear niche, and terms like 'fal vision' are distinctive. It is not a 5 because generic verbs such as 'Analyze images' and 'segment' could overlap with other image-analysis skills, matching the 4 anchor ('mostly distinct; minor overlap risk with closely related skills').

4 / 5

Total

16

/

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-vision/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.