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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/bfl-api/SKILL.md

Quality

Content

78%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 content is highly actionable with executable examples and well-structured progressive disclosure, but loses conciseness points to repeated warnings and time-sensitive pricing tables that are not isolated in a deprecated section, and to workflow validation that is delegated to a reference rather than shown inline.

Suggestions

State the 10-minute URL-expiration warning once in the Basic Request Flow and remove the duplicate mentions in the top 'Important' block and the Quick Start tip to reduce redundancy.

Collapse the duplicated 'First: Check API Key' section into the later 'API Key Setup' section so the key check is described a single time.

Move or isolate the detailed credit/pricing tables into a reference file (or mark them as time-sensitive) and surface a brief inline note pointing there, since per-credit and per-megapixel prices are likely to change.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient domain-specific content Claude would not already know, but repeats the URL-expiry warning three times and the 'echo $BFL_API_KEY' check twice, and inlines extensive time-sensitive pricing tables outside any deprecated/old-patterns section, which penalizes conciseness.	3 / 5
Actionability	Provides copy-paste-ready, fully executable curl commands with real endpoint URLs and complete JSON payloads (e.g. the Quick Start submit/poll/download sequence and multi-reference example), covering the common cases concretely.	5 / 5
Workflow Clarity	The POST → poll → download flow is clearly sequenced with a numbered diagram and a 4-step Quick Start, but error-recovery feedback loops live only in the referenced error-handling file rather than inline, leaving minor validation gaps.	4 / 5
Progressive Disclosure	The body is a clear overview that signals one-level-deep references (six reference docs plus three code-example files, all verified to exist) with descriptive labels, keeping quick-reference content inline and detailed material in separate files for easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

75%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 is specific and clearly distinct to the BFL FLUX API, but it omits any explicit 'when to use' trigger guidance, which caps its completeness and leaves the most natural user-facing trigger term ('image generation') absent.

Suggestions

Add a 'Use when...' clause naming concrete user triggers, e.g. 'Use when integrating BFL FLUX APIs for image generation, editing, or processing, or when the user mentions FLUX models, BFL, or async image-generation polling.'

Include the primary user-facing term 'image generation' (and 'image editing') so the description matches what users naturally say, not just developer terminology.

Add common synonyms/extensions (e.g. 'FLUX.2', 'FLUX.1', 'image generation', 'image editing') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'endpoints, async polling patterns, rate limiting, error handling, webhooks, and regional endpoints with Python and TypeScript code examples' — giving comprehensive coverage of the integration domain.	5 / 5
Completeness	Clearly answers 'what' (an integration guide covering enumerated capabilities) but provides no 'Use when...' clause or equivalent trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Contains natural developer terms like 'API integration', 'endpoints', 'rate limiting', 'webhooks', and 'error handling', but misses the core use-case phrase users would actually say ('image generation') and any model-name or file-extension synonyms.	4 / 5
Distinctiveness Conflict Risk	The 'BFL FLUX API' framing carves out a clear, vendor-specific niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .agents/skills/bfl-api/SKILL.md
Commit: 08e2151

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.