CtrlK
BlogDocsLog inGet started
Tessl Logo

fal-platform

Platform APIs for model management, pricing, and usage tracking

26

Quality

18%

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

Quality

Content

11%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 skill is essentially a placeholder stub with no actionable content. It repeats its own description three times and provides no concrete guidance, code, commands, or workflows for working with Fal platform APIs. The only useful element is a link to an external repository, but the skill itself teaches Claude nothing.

Suggestions

Add concrete API examples (e.g., listing models, checking pricing, querying usage) with executable code snippets or curl commands.

Define a clear workflow for common tasks like model management, including specific endpoints, authentication patterns, and expected responses.

Remove the redundant 'When to Use' and 'Instructions' boilerplate sections that merely restate the overview, and replace them with actual technical content.

If detailed API reference is extensive, create bundle files (e.g., REFERENCE.md, EXAMPLES.md) and link to them from the main SKILL.md.

DimensionReasoningScore

Conciseness

The content is padded with repetitive boilerplate—the description, 'When to Use', and 'Instructions' sections all say essentially the same thing. However, it's short, so the verbosity is more about redundancy than length.

2 / 5

Actionability

There is zero concrete guidance—no code, no commands, no API endpoints, no examples. It merely describes what the skill is about and links to an external repository without providing any actionable instructions.

1 / 5

Workflow Clarity

No steps, no sequence, no validation checkpoints are provided. The content is entirely abstract with no workflow of any kind.

1 / 5

Progressive Disclosure

There is a single external link to a source repository, but no bundle files, no structured references, and no meaningful content organization. The sections that exist are hollow placeholders rather than real progressive disclosure.

2 / 5

Total

6

/

20

Passed

Description

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

This description is too vague and abstract to effectively guide skill selection. It names a broad domain without specifying concrete actions, lacks a 'Use when...' clause, and doesn't include enough natural trigger terms or platform-specific details to distinguish it from other API-related skills.

Suggestions

Add a 'Use when...' clause with specific trigger phrases, e.g., 'Use when the user asks about API pricing, model availability, usage quotas, billing, or rate limits.'

Specify concrete actions with verbs, e.g., 'Queries model endpoints, retrieves pricing tiers, monitors API usage and billing, manages API keys.'

Name the specific platform (e.g., 'Anthropic API', 'OpenAI API') and include natural synonyms like 'billing', 'quota', 'rate limits', 'API keys' to improve trigger term coverage and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('Platform APIs') and lists three areas ('model management, pricing, and usage tracking'), but these are high-level categories rather than concrete actions. No specific verbs describe what the skill actually does with these areas.

2 / 5

Completeness

Provides a vague 'what' (platform APIs for three areas) but completely lacks a 'when' clause. There is no guidance on when Claude should select this skill, which per the rubric caps completeness at 3 maximum, and the 'what' itself is too vague to reach 3.

2 / 5

Trigger Term Quality

Contains some relevant terms like 'APIs', 'pricing', and 'usage tracking', but lacks natural user phrases, specific platform names, synonyms (e.g., 'billing', 'quota', 'rate limits', 'API keys'), or file/endpoint references users would mention.

2 / 5

Distinctiveness Conflict Risk

'Platform APIs' is very broad and could overlap with many API-related skills. Without specifying which platform or distinguishing itself from general API documentation skills, there is high overlap risk.

2 / 5

Total

8

/

20

Passed

Validation

90%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

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.