CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fal-audio

Text-to-speech and speech-to-text using fal.ai audio 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 ./skills/fal-audio/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

22%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 a hollow shell: it restates the description three times and defers all substance to an external URL, providing zero executable guidance, model names, or workflow steps. A Claude loading this skill learns nothing it could act on.

Suggestions

Replace the abstract Instructions section with concrete, executable guidance: example fal.ai endpoint IDs, a sample API call for TTS and one for STT, and expected input/output formats.

Move detailed material into local reference files (e.g., references/models.md) and link them one level deep instead of pointing to an external GitHub URL.

Remove the redundant restatements of the description across the Overview, When to Use, and Instructions sections, keeping each section's content distinct.

DimensionReasoningScore

Conciseness

The body is short and avoids explaining concepts Claude already knows, but it consists of three near-identical restatements of the description ("Text-to-speech and speech-to-text using fal.ai audio models" appears in Overview, When to Use, and Instructions). Mostly efficient in length yet noticeably redundant — it could be tightened to a single line, so it does not reach anchor 4's "efficient; minor instances" bar.

3 / 5

Actionability

The Instructions section offers only "This skill provides guidance and patterns for text-to-speech and speech-to-text" — entirely abstract, with no code, commands, model IDs, endpoints, or parameters. This matches anchor 1 ("only describes rather than instructs"); a 2 would at least give high-level concrete steps, which are absent.

1 / 5

Workflow Clarity

No steps or sequence of any kind are present, despite the skill involving a multi-step process (choose model, call fal.ai endpoint, handle result). "Steps missing or incoherent; no sequence; no validation" is an exact match for anchor 1; anchor 2 requires at least a rough sequence, which does not exist.

1 / 5

Progressive Disclosure

The body has organized sections (Overview, When to Use, Instructions), but no local reference files exist in the bundle (references/, scripts/, assets/ are all absent) — the only pointer is to an external GitHub URL rather than one-level-deep bundled references. Structure exists but the actual detailed content is not disclosed anywhere reachable, fitting anchor 3 better than the well-split anchor 5 or the mostly-placed anchor 4.

3 / 5

Total

8

/

20

Passed

Description

53%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 correctly states what the skill does at a domain level and benefits from the distinctive fal.ai qualifier, but it entirely lacks a "when to use" trigger clause and misses common trigger synonyms. It reads as a bare capability label rather than a full invocation description.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to convert text to speech, transcribe audio, or mentions TTS, fal.ai, or voice generation."

Include common user-facing synonyms such as "TTS", "transcribe/transcription", and "voice" alongside the current terms.

Mention concrete capability details (e.g., supported model names or endpoint types) to sharpen specificity.

DimensionReasoningScore

Specificity

The description names the domain ("fal.ai audio models") and two concrete actions ("Text-to-speech and speech-to-text"), but coverage is not comprehensive — no model names, endpoints, or additional operations. It matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive") and does not list the several specific actions required for a 4.

3 / 5

Completeness

The description has a clear "what" (TTS and STT via fal.ai models) but no "Use when..." or equivalent trigger clause at all, which caps completeness at 3 per the judging guidelines. A score of 4 would require both what and when to be present.

3 / 5

Trigger Term Quality

"Text-to-speech" and "speech-to-text" are natural user phrases, but common variations and synonyms are missing ("TTS", "transcribe/transcription", "voice", "audio generation"). This fits anchor 3 ("Some relevant keywords but missing common variations or synonyms") better than anchor 4's fuller coverage.

3 / 5

Distinctiveness Conflict Risk

"fal.ai" pins the skill to a specific provider niche, making it mostly distinct with only minor overlap risk against other generic TTS/STT skills. It falls short of anchor 5 because without the provider qualifier, "audio models" would conflict with any other audio skill.

4 / 5

Total

13

/

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

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