CtrlK
BlogDocsLog inGet started
Tessl Logo

fal-platform

Platform APIs for model management, pricing, and usage tracking

36

Quality

33%

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-claude/skills/fal-platform/SKILL.md

The canonical home for this skill is fal-platform 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 body is structurally well-organized with clear headers and a single signaled reference, but it carries no actionable guidance, no executable examples, and no workflow — it restates the description three times. The skill body currently adds almost nothing beyond its frontmatter.

Suggestions

Add concrete, executable guidance in the Instructions section: example API calls or commands for listing models, fetching pricing, and tracking usage.

Replace the triple-repeated description sentence with distinct, non-redundant content in each section (Overview = summary, When to Use = triggers, Instructions = how-to).

Provide at least a minimal workflow or worked example so Claude knows the exact sequence of API calls to perform a common task.

DimensionReasoningScore

Conciseness

The body is terse but the Overview, When to Use, and Instructions sections each repeat the same single sentence with minor rewording, which is unnecessary; it avoids verbose concept explanations but earns no lean-value credit because there is no real content.

3 / 5

Actionability

The Instructions section only states 'This skill provides guidance and patterns for platform apis...' with no code, commands, endpoints, or examples, matching the anchor for entirely vague/abstract content that describes rather than instructs.

1 / 5

Workflow Clarity

There are no steps, sequence, or workflow described anywhere in the body — only a 'provides guidance and patterns' statement and an external link, matching the 'steps missing or incoherent' anchor.

1 / 5

Progressive Disclosure

The body is under 50 lines with clearly labeled section headers (Overview, When to Use, Instructions) and a single one-level-deep, clearly signaled link to the source repository; no bundle files exist, and the only gap is that the sections are essentially empty.

4 / 5

Total

9

/

20

Passed

Description

41%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 catalogues capability domains but provides no concrete actions, no explicit trigger guidance, and omits the platform name, leaving it generic and conflict-prone. It is a minimal 'what' statement with no 'when' clause.

Suggestions

Add an explicit 'Use when...' clause naming concrete trigger phrases a user would say (e.g., 'Use when working with fal.ai models, checking fal pricing, or tracking fal API usage').

Replace the noun-phrase capability list with concrete actions (e.g., 'List models, fetch pricing, and track usage via the fal platform APIs').

Include the platform name 'fal' / 'fal.ai' and natural synonyms (endpoints, queue, API keys) to improve distinctiveness and trigger-term quality.

DimensionReasoningScore

Specificity

The phrase 'Platform APIs for model management, pricing, and usage tracking' names three capability domains but uses no concrete action verbs (e.g., list, fetch, track), matching the anchor where the domain is named but actions are minimal or generic.

2 / 5

Completeness

It gives a clear 'what' (platform APIs for the three named areas) but contains no 'Use when...' clause or equivalent trigger guidance; per the guidelines a missing 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

It includes several relevant terms ('model management', 'pricing', 'usage tracking', 'Platform APIs') but lacks natural synonyms and platform-specific keywords a user would actually say (e.g., 'fal', 'fal.ai', 'endpoints', 'queue', 'API keys'), matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

Without naming the platform itself (fal/fal.ai), the description is very broad and would overlap with many other API or platform-management skills, matching the 'very broad; high overlap risk' anchor.

2 / 5

Total

10

/

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.

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.