Introducing Luma Skills: Build a Creative Workflow Once, Run It Forever

Setting the Scene

Every creative team knows the feeling. You land on a result that is exactly right, the kind of output that makes the room go quiet, and then the question arrives. How did I get here? How do I do this again tomorrow with a different subject, a different image, a different brand?

Luma Skills answer that question. A Skill is a repeatable workflow inside Luma Agents. Instead of producing one great asset, you produce a repeatable method for producing great assets, and that method travels. Build a Skill once and run it again and again on new assets, reaching the same level of quality every time.

What Is a Luma Skill?

A Skill is a repeatable workflow inside Luma Agents: a clear set of instructions that anyone can follow to reach a consistent, high-quality creative result. It works a little like a good recipe, where a clear list of steps lets almost anyone arrive at something great.

Once you have built a Skill, you can run it tomorrow, the day after, or at any point in the future, with entirely different assets, and still reach the same level of quality. That is the whole idea. The expertise that used to live in one person's head becomes a repeatable workflow the whole team can use.

The Anatomy of a Skill

Every Skill is built from three parts.

The first is your input: the prompt you write, plus any image or video you want to work with.

The second is the tools the Skill draws on: the models, tasks, and actions available inside Luma Agents.

The third is the instructions: the step-by-step guidance for applying those tools to your input. This is the heart of the Skill, and it is where consistency comes from. Change the input, keep the instructions, and you reach the same quality on a new asset every time.

Two Ways to Build a Skill

Build one from scratch

You will find the Skills menu in the bottom right of Luma Agents. Creating a Skill from scratch starts with a thumbnail, a name, and a description, followed by the body of instructions.

The description carries real weight. It is what the agent reads to decide when to reach for this Skill instead of another one, so writing it clearly pays off later.

You write the instructions in plain language, the same way you would explain the task to another person. There is no special syntax to learn.

Say you wanted a Skill that adds smiles to everyone in a photo. You might name it "Make Happy People," write a description explaining that the Skill adds smiles to people's faces, and then build out the instructions in the body: take an image, detect the people in it, and add a smile to each one.

The instructions are also where you handle the edge cases, and specifying them is one of the best things you can do for a reliable Skill. What happens when a person is detected but their face is occluded? Should the Skill add smiles to dogs or cartoon characters, or only to real people? Spelling this out is what separates a Skill that works once from a Skill that works every time.

Build one with the agent

Prefer to have it built for you? Ask the agent. Luma Agents can create a Skill from a plain description of what you want.

Here is a real example. Imagine you have hundreds of hours of footage of yourself riding motorcycles, and you want to share it, but most of that footage shows you without a helmet. You can simply tell the agent: help me create a Skill that takes a video and adds a helmet to anyone riding a motorcycle.

From there, the agent runs a three-stage process to generate the Skill for you. In this case it recognized an existing workflow for the task and produced a Skill called "Safety First," complete with a thumbnail and a full set of instructions. You write no prompts and assemble nothing by hand. The agent does the work, and the finished Skill is ready to use.

Three Ways to Run a Skill

Luma gives you more than one path to invoking a Skill, so you can use whichever fits your moment.

The first is direct selection. Open the Skills menu, choose your Skill, click use, select your asset, and run it.

The second is the slash command. Begin with a slash, choose your Skill from the list that appears, point it at an asset, and run it inside the agent.

The third is the most natural of all. You can hand the agent a video and ask it to do something, and the agent will scan the Skills you have available and apply the right one on its own. Give it footage of a person riding a motorcycle without a helmet, and the agent recognizes the situation and reaches for the relevant Skill automatically. This is where a well-written description earns its keep.

Sharing and Scaling Skills Across a Team

A Skill is useful the moment you build it, and it goes further when you share it. One person's proven workflow becomes something the whole team can run.

Share a single Skill with a link

Once you have iterated on a Skill and reached results you are confident in, you can share it. Right-click the Skill or use the share button, and Luma copies a link to your clipboard. Send that link to anyone, and they can install your Skill for themselves. When they open it, they choose a board and install the Skill directly onto it, ready to run.

Installing comes with a built-in checkpoint. When someone imports a Skill, Luma confirms the action and reminds them to trust the creator before adding it, which keeps the process deliberate.

Bundle Skills into a package

When several Skills belong together, you can ship them as a package. Select the Skills you want, name the bundle, describe what it does, and share all of them with a single link. The recipient picks a board and installs the whole set at once. For teams that rely on a consistent toolkit, this turns distribution into a single step.

Download a Skill as a file

You can also download an individual Skill as a zip file. It is the same artifact you would otherwise upload, which gives you another straightforward way to hand a Skill to someone or move it between workspaces.

Why Skills Matter for Creative Teams and Enterprises

Skills change the unit of creative work. The thing you build and keep is a repeatable workflow, and that workflow travels.

For marketing and creative organizations, that has real consequences. A Skill captures a proven approach once and lets every team member run it, so quality stops depending on who happens to be at the keyboard. Sharing and packaging mean an agency or an in-house team can standardize a workflow and roll it out to everyone in a single link. And because the agent can choose the right Skill on its own, the library you build keeps getting more useful as it grows.

The result is creative output that stays consistent as it scales, with the craft preserved inside a process anyone can follow.