Agent skill · Data & Analytics

bria-fibo-image

Build and operate rights-aware Bria FIBO and FIBO Lite image-generation workflows with structured prompts, reference images, asynchronous status handling, webhooks, cost gates, and safe artifact downloads. Use when a user asks for Bria/FIBO generation, refinement, inspiration, reproducibility, hosted API integration, or a licensed-data image workflow; do not use for FIBO Edit, video, generic image editing, or third-party FIBO gateways.

Calesthio43,316★ · +2,384/wk · 2 repos on radarProfile →
claude-codecodexcopilotcursorMIT
Install
npx skills add calesthio/generative-media-skills --skill bria-fibo-image --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 47 KB
Bundled scripts: none
Path: skills/providers/image-generation/bria-fibo-image/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 112 · +8 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Instructs an agent to build and operate rights-aware Bria FIBO and FIBO Lite image-generation workflows, using structured prompts, a reference image, asynchronous status handling, webhooks, and cost gates, with safe artifact downloads. Applies when a user requests Bria/FIBO generation, refinement, inspiration, reproducibility, hosted API integration, or a licensed-data image workflow; excludes FIBO Edit, video, generic image editing, or third-party FIBO gateways.

How it works

  • Uses Bria's first-party hosted v2 API unless the user asks for local weights; keeps local-weight licensing separate from hosted API terms. Never route a first-party request through fal.ai, Replicate, or another gateway.
  • Establishes decision paths and routes via v2 OpenAPI endpoints, selecting among image/generate, image/generate/lite, structured_prompt/generate, and structured_prompt/generate/lite, with designated fields and behaviors for each route. Enforces the exact route schema (one of the allowed combinations) per request.
  • Documents and applies an evidence vocabulary with defined labels (Documented fact, Provider claim, Operational heuristic, Unknown).
  • Requires explicit start with a decision record detailing intent, delivery, inputs, outputs, governance, and spend before writing code or submitting work.
  • Specifies exact routes, required fields, and behavior differences for high-fidelity vs faster iteration vs structured prompts; handles prompts, images, seeds, and structured prompts with attention to licensing and data handling.
  • Provides a complete hosted example client script and price guidance, including per-call costs and rate limits, while enforcing client-side caps and validation.

When to use it

  • Use when a user requests Bria/FIBO image-generation, refinement, inspiration, reproducibility, hosted API integration, or licensed-data image workflows. Do not use for FIBO Edit, video, generic image editing, or third-party FIBO gateways.

What it can touch

  • Interacts with hosted Bria API at base URL https://engine.prod.bria-api.com/v2 via routes: /image/generate, /image/generate/lite, /structured_prompt/generate, /structured_prompt/generate/lite. Includes fields such as resolution, steps_num, negative_prompt, prompt, images, structured_prompt, webhook_url, output_type, and other standard image-generation inputs. The skill notes that the OpenAPI accepts image input as a public URL or raw base64 without data:image prefix and supports JPEG/PNG/WEBP; it enforces validation on field combinations and rejects unknown fields locally.

Caveats

  • Volatile facts and sources were checked 2026-07-10; recheck schemas, pricing, plan limits, model cards, and governing terms before production.
  • Privacy consequences indicate certain data paths and subprocessor details are not fully established; users should confirm contracts/DPAs before handling sensitive inputs. Lite uses hosted data transfer to Bria; local/on-prem requires a separately licensed deployment.
  • The current schemas enforce asynchronous operation by default and may incur hosted-usage costs; approvals and costs are governed by Bria’s pricing and contract terms.
  • The skill emphasizes that structured-prompt routes do not expose image outputs for some endpoints and that unknown fields should be rejected locally.
From the SKILL.md

# Bria FIBO image generation Use Bria's first-party hosted v2 API unless the user explicitly asks for local weights. Keep local-weight licensing separate from hosted-API terms. Never route a first-party request through fal.ai, Replicate, or another gateway. ## Evidence vocabulary Use these labels when presenting material facts: - **Documented fact** - stated by a cited first-party API schema, mode

More from generative-media-skills
All skills →
About this skill
What does the bria-fibo-image skill do?

Build and operate rights-aware Bria FIBO and FIBO Lite image-generation workflows with structured prompts, reference images, asynchronous status handling, webhooks, cost gates, and safe artifact downloads. Use when a user asks for Bria/FIBO generation, refinement, inspiration, reproducibility, hosted API integration, or a licensed-data image workflow; do not use for FIBO Edit, video, generic image editing, or third-party FIBO gateways.

How do I install it?

Run `npx skills add calesthio/generative-media-skills --skill bria-fibo-image --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From calesthio/generative-media-skills, a repository with 112 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going