FLUX agent skills for video direction, and Sume's skill install

BFL released six Agent Skills for directing FLUX 3 video from a coding agent on 2026-08-07, and they apply to BFL's model. Sume ships a separate packaged skill: sume skills install writes it into .agents/skills or .claude/skills, and it is a Sume skill, not a FLUX 3 one.

BFL's line is from its release notes; Sume's is from the Agent skills page, both read 2026-09-29. The release note gives a count and a purpose only, so this post says nothing about what BFL's skills contain.

How do I install Sume's skill?

The CLI has commands to list, install, update, export and remove it. Export first if you want to read the source files before a custom install.

sume skills list
sume skills install
sume skills export sume

What does a skill not do?

A skill is instructions for an agent, not a permission. Sume's docs tell agents to prefer read commands while planning and not to submit paid provider work without explicit operator confirmation. Image, Video and Music generation are not CLI submit commands yet, so an agent generates video through the Developer API or hosted MCP, and a skill cannot change that.

Which one should my coding agent use?

If the video comes from FLUX 3, use BFL's skills and BFL's API. If it comes from Sume's catalog, use Sume's skill for the CLI conventions, and hosted MCP or the API for generation. They do not conflict, since they teach different services.

How do I keep a skill from spending money?

Use the gates the docs give. In the CLI, --confirm-paid marks generation that can reserve or spend credits, and --confirm-submit covers non-paid writes such as cancelling a job. On hosted MCP, paid tools need an idempotency_key and support dry_run=true.

A skill can tell an agent to use these, but the gates are what enforce it, so put the rule in both places.

Can I read a skill before I trust it?

For Sume's, yes: sume skills export sume writes the source files out so you can review them before a custom install. Do the same for any third-party skill, BFL's included, before you point an agent that can spend at it.

What should I check after installing one?

List what landed on disk, confirm the directory is the one your agent reads, and run one read-only task before any paid one. For Sume, sume doctor --agent --json and sume catalog list --json are the read commands the docs give for planning. Then try a dry run of a paid call and confirm you see the cost preview before anything is submitted.