CtrlK
BlogDocsLog inGet started
Tessl Logo

bfl-api

BFL FLUX API integration guide covering endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples.

60

Quality

71%

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 ./.agents/skills/bfl-api/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable, well-sequenced, and uses progressive disclosure effectively with a clean references structure; the main weakness is redundancy from repeated API-key checks and URL-expiration warnings.

Suggestions

Consolidate the duplicated API-key check into a single section to remove the repeated `echo $BFL_API_KEY` block.

State the 10-minute URL-expiration behavior once and reference it rather than repeating it in four locations.

DimensionReasoningScore

Conciseness

The body is mostly efficient and information-dense with genuinely novel API specifics (model paths, pricing, regional endpoints), but it repeats the API-key check (`echo $BFL_API_KEY`) in two sections and states the 10-minute URL expiration in four places, which could be tightened; time-sensitive pricing also sits in the main body rather than a deprecated/old-patterns section.

2 / 3

Actionability

It provides fully executable curl commands for submission, polling, download, and multi-reference editing plus concrete endpoints, parameters, and a copy-paste-ready Quick Start flow.

3 / 3

Workflow Clarity

The Basic Request Flow is a clear submit → poll → download sequence with an explicit feedback loop ("GET polling_url (repeat until complete)" with Pending/Ready/Error states) and a pre-flight API-key validation checkpoint, which meets the anchor for a simple, well-sequenced workflow.

3 / 3

Progressive Disclosure

The body is an overview with quick-reference tables and a clearly signaled, one-level-deep References section listing nine real bundle files (all verified present: api-key-setup, endpoints, polling-patterns, rate-limiting, error-handling, webhook-integration, and code-examples/{curl,python,typescript}) with descriptions; navigation is easy.

3 / 3

Total

11

/

12

Passed

Description

57%

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 is specific to its niche and low-conflict, but it describes a guide's coverage topics rather than concrete actions and omits an explicit "Use when..." trigger clause, capping completeness and trigger quality.

Suggestions

Add an explicit "Use when..." trigger clause (e.g., "Use when integrating the BFL FLUX API for image generation or editing") so both what and when are answered.

Include natural user-facing trigger terms like "image generation", "text-to-image", and "FLUX models" alongside the developer terms.

Reframe the topic nouns as concrete actions (e.g., "Submit generation requests, poll for results, download images, and handle rate limits and webhooks").

DimensionReasoningScore

Specificity

The description names a concrete domain and a broad set of topics ("endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples"), but these are coverage nouns for a "guide" rather than the concrete verb-based actions the anchor 3 example uses ("Extract text..., fill forms, merge documents").

2 / 3

Completeness

It clearly answers what the skill covers, but there is no explicit "Use when..." trigger clause; per the guidelines a missing explicit trigger caps completeness at 2.

2 / 3

Trigger Term Quality

It includes relevant developer terms ("BFL FLUX API", "polling", "rate limiting", "webhooks", "Python and TypeScript") but misses the most natural user-facing variations such as "image generation", "text-to-image", or "FLUX models" that a user would actually say.

2 / 3

Distinctiveness Conflict Risk

It is scoped tightly to "BFL FLUX API integration guide", a clear niche with distinct triggers that is unlikely to fire for unrelated skills.

3 / 3

Total

9

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 6 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository
calesthio/OpenMontage
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.