Skills
Reusable playbooks the agent loads on demand.
A skill is a written playbook — a set of rules and a worked approach for a specific kind of video. Where a snippet is a few standing rules, a skill is a full method the agent reads before it starts building.
Open Skills and Connectors in the sidebar to see them.
Built-in skills
fluos ships with a library of skills covering the video types it makes most often — product launches, explainers, social cuts, data stories, logo animation, caption styling, and the motion craft underneath all of them.
You do not need to enable these. The agent picks the relevant ones on its own based on your brief. Browsing them is still worth ten minutes: the skill list is effectively a map of what fluos is good at, and reading one tells you exactly what vocabulary to use in your prompts.
Calling a skill directly
Type / in the composer to open the skill picker, or @ followed by the skill name. That inserts an @skill-name mention, which loads that skill up front instead of leaving the choice to the agent.
@social-vertical Make a 12-second cut of this for TikTok.Use this when you know exactly which playbook you want, or when the agent picked a different one than you expected.
Writing your own
Ask for it in chat:
Write a skill for our weekly changelog videos:
16:9, 25 seconds, dark background, one feature per scene,
our orange accent, always end on the docs URL.fluos writes the skill and saves it to your workspace. This is a conversational request, not a build — it does not consume a build or produce a video.
Custom skills are workspace-scoped, so everyone on the team gets them.
Snippet or skill?
If it is a handful of constraints you always want applied, use a snippet. If it is a repeatable format — a recurring video type with its own structure and pacing — write a skill.