CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fal-workflow

Generate workflow JSON files for chaining AI models

Quality

49%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/fal-workflow/SKILL.md

The canonical home for this skill is fal-workflow in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

26%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 skill body is an empty stub: it repeats the frontmatter description three times (with degraded grammar) and provides no executable guidance, examples, workflow steps, or validation. Structure and brevity are acceptable, but the skill delivers no actionable content for its stated task.

Suggestions

Replace the filler Instructions section with concrete, executable guidance: a minimal complete example of a fal workflow JSON chaining two models (e.g., a text-to-image model feeding an image-to-image model).

Add a step sequence for building workflows (gather user inputs, add model nodes, wire outputs to inputs, validate the JSON, export/deploy) with an explicit validation checkpoint before export.

Either inline the actual patterns from the linked source repository or add a real references/ file with example workflows, instead of the bare external GitHub link.

DimensionReasoningScore

Conciseness

The body is tiny but restates the same one-line description three times ("Generate workflow JSON files for chaining AI models", "Use this skill when you need to work with generate workflow json files...", "This skill provides guidance and patterns for generate workflow json files..."), so two of three content sentences are unnecessary and could be cut — matching the anchor 'Mostly efficient but includes some unnecessary explanation or could be tightened'. It is not score 2 because the body is not padded with concept explanations, and not score 4 because the redundancy is more than minor relative to the body's size.

3 / 5

Actionability

The Instructions section contains only "This skill provides guidance and patterns for generate workflow json files for chaining ai models" — no code, no commands, no schema examples, no concrete steps — matching the anchor 'Entirely vague or abstract; no concrete code or commands; only describes rather than instructs'. Score 2 is not reached because there are not even high-level hints toward execution; the entire skill content is a restatement of the description.

1 / 5

Workflow Clarity

No sequence of steps exists anywhere in the body — the anchor 'Steps missing or incoherent; no sequence' fits exactly. Building a chained-model workflow JSON is a multi-step generative task, yet the skill provides no workflow, no ordering, and no validation guidance, so the simple-skill exception (single unambiguous action) does not apply.

1 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories), the body is well under 50 lines with labeled sections, and the single link (the source repository) is clearly signaled and one level deep — matching the anchor 'Good structure; most content is appropriately placed; references mostly clear; minor organization gaps'. It does not reach 5 because the sections are redundant filler rather than well-organized substance, and the skill arguably needs real referenced material given its body contains none.

4 / 5

Total

9

/

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 states a clear, single-action 'what' with a specific artifact and purpose, but completely lacks a 'when to use' trigger clause and natural trigger terms such as "fal", "fal.ai", or "pipeline". It reads as a domain statement rather than an actionable, discoverable trigger description.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to build fal.ai workflows, chain AI models into a pipeline, or mentions workflow JSON or fal workflows."

Include natural trigger terms and synonyms users would actually say: "fal", "fal.ai", "model pipeline", "chain models", and relevant file extensions.

List 1-2 more concrete actions to broaden coverage, e.g. "define model nodes, wire inputs/outputs between steps, validate and export workflow JSON".

DimensionReasoningScore

Specificity

The description "Generate workflow JSON files for chaining AI models" names the domain and one concrete action with a specific artifact (workflow JSON files) and purpose (chaining AI models), matching the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'. It is above score 2 ('Processes PDF files') because it specifies the output format and goal rather than just naming the domain, and below score 4 because only one action is listed with no coverage of related operations.

3 / 5

Completeness

The 'what' is clearly stated (generate workflow JSON files for chaining AI models) but there is no 'Use when...' clause or equivalent trigger guidance, matching the anchor 'Has a clear what but when is missing or only weakly implied' and hitting the guideline cap of 3 for a missing explicit trigger. Score 4 is not warranted because 'when' is entirely absent rather than just under-specified.

3 / 5

Trigger Term Quality

Relevant keywords exist ("workflow", "JSON", "chaining", "AI models") but common variations are missing, matching the anchor 'Some relevant keywords but missing common variations or synonyms'. It does not reach score 4 because natural user phrases like "fal", "fal.ai", "pipeline", or file extensions are absent, and it is above score 2 because the terms present are on-topic rather than purely generic.

3 / 5

Distinctiveness Conflict Risk

"Generate workflow JSON files for chaining AI models" is somewhat specific (AI model chaining) but "workflow JSON" overlaps with general workflow-generation and orchestration skills, matching the anchor 'Somewhat specific but could still overlap with similar skills'. It falls short of score 4 because the description omits the platform name ("fal" appears only in the name field), weakening its niche signal.

3 / 5

Total

12

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/fal-workflow/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.