How do I install the Flora Run Technique skill?

Run npx skillmds@latest add florafauna-ai/flora-run-technique-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Flora Run Technique safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Flora Run Technique?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Flora Run Technique free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Flora Run Technique?

florafauna-ai (@florafauna-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Flora Run Technique by florafauna-ai

Name: Flora Run Technique
Author: florafauna-ai

Flora Run Technique

Run a saved FLORA technique — a multi-step visual workflow such as background swap, relighting, upscale, model swap, or sketch-to-render. Use when the user names a technique, asks to transform an image they already have ("put this on a clean background", "match this lighting", "upscale this", "make this look photographed"), or asks what FLORA can do. Do not use for a plain text-to-image request with no source image, and do not use to inspect existing project work.

florafauna-ai Updated Sep 21, 2026

File contents

Run a FLORA technique

A technique is a saved workflow that chains several models. It is the thing FLORA does that a single image model cannot: the steps, prompts, and model choices are fixed by whoever authored it, so the same technique gives the same treatment every time.

Input: the user's intent, plus any source image. Output: the technique's output URLs, the charged cost, and the project the run landed in.

Steps

Resolve the workspace. Call flora_list_workspaces. If there is more than one, ask which to bill before spending anything.
Find the technique. Call flora_list_techniques and match on the user's intent. It returns run_cost and a summary of inputs for each. If nothing fits, say so and offer flora_generate instead — do not force an unrelated technique.
Get the exact input ids. Call flora_get_technique. Its declared input ids are the keys flora_run_technique expects. Never guess them from the name.
Get each image input to an HTTPS URL (see Image inputs below).
Run it. Call flora_run_technique with workspace_id, technique_id, and an inputs object keyed by those ids. Omit optional text inputs entirely when the user gave no direction — an empty string is rejected, not treated as absent.
Poll and report. Poll flora_get_run until status is completed or failed. Report the output URL, the charged cost, and a link to the project.

Image inputs

FLORA fetches images server-side from an HTTPS URL. Files the user attaches in ChatGPT already have one — they are hosted on files.openai.com or cdn.openai.com, both allowlisted. Pass that URL straight to flora_create_asset as source, or into the technique input directly.

Never base64-encode a file or try to upload bytes. If the image genuinely has no URL, say that this environment cannot upload it and point the user at their FLORA project to add it there.

Rules

State the cost before running. run_cost comes back from flora_list_techniques. Techniques range from free to several dollars per run.
You cannot see the output. Runs return URLs, not pixels. Describe what was produced from the technique and the inputs; never claim to have looked at it.
On input_validation_error, re-read flora_get_technique, rebuild inputs from what it returns, and retry once. Do not retry other failures — retries bill.
On insufficient credits, surface the message and stop.

---name: flora-run-technique-2description: Run a saved FLORA technique — a multi-step visual workflow such as background swap, relighting, upscale, model swap, or sketch-to-render. Use when the user names a technique, asks to transform an image they already have ("put this on a clean background", "match this lighting", "upscale this", "make this look photographed"), or asks what FLORA can do. Do not use for a plain text-to-image request with no source image, and do not use to inspect existing project work.---# Run a FLORA techniqueA technique is a saved workflow that chains several models. It is the thing FLORAdoes that a single image model cannot: the steps, prompts, and model choices arefixed by whoever authored it, so the same technique gives the same treatment everytime.**Input:** the user's intent, plus any source image.**Output:** the technique's output URLs, the charged cost, and the project the runlanded in.## Steps1. **Resolve the workspace.** Call `flora_list_workspaces`. If there is more than one, ask which to bill before spending anything.2. **Find the technique.** Call `flora_list_techniques` and match on the user's intent. It returns `run_cost` and a summary of inputs for each. If nothing fits, say so and offer `flora_generate` instead — do not force an unrelated technique.3. **Get the exact input ids.** Call `flora_get_technique`. Its declared input ids are the keys `flora_run_technique` expects. Never guess them from the name.4. **Get each image input to an HTTPS URL** (see Image inputs below).5. **Run it.** Call `flora_run_technique` with `workspace_id`, `technique_id`, and an `inputs` object keyed by those ids. Omit optional text inputs entirely when the user gave no direction — an empty string is rejected, not treated as absent.6. **Poll and report.** Poll `flora_get_run` until status is `completed` or `failed`. Report the output URL, the charged cost, and a link to the project.## Image inputsFLORA fetches images server-side from an HTTPS URL. **Files the user attaches inChatGPT already have one** — they are hosted on `files.openai.com` or`cdn.openai.com`, both allowlisted. Pass that URL straight to`flora_create_asset` as `source`, or into the technique input directly.Never base64-encode a file or try to upload bytes. If the image genuinely has noURL, say that this environment cannot upload it and point the user at their FLORAproject to add it there.## Rules- **State the cost before running.** `run_cost` comes back from `flora_list_techniques`. Techniques range from free to several dollars per run.- **You cannot see the output.** Runs return URLs, not pixels. Describe what was produced from the technique and the inputs; never claim to have looked at it.- **On `input_validation_error`,** re-read `flora_get_technique`, rebuild `inputs` from what it returns, and retry once. Do not retry other failures — retries bill.- **On insufficient credits,** surface the message and stop.

Frequently asked questions