Create and Manage Skills

Turn a creative method you use repeatedly into a Skill and continue maintaining it across projects.

What you can do

Create a Skill from a goal, existing Markdown, or a completed project, then continue editing Skills saved to your account. Keep knowledge and rules that change the Agent's creative decisions; do not repeat generic steps the Agent already knows.

Create or edit a Skill

Start from the Skill page: Open the Skill community, switch to Mine, and select New Skill.
Ask the Agent inside a project: Upload Markdown and ask the Agent to organize it as a Skill, create a Skill from experience gained in the project, or update a Skill already used by the project.
Use Flova CLI: Prepare and submit Skill files through an Agent that can run local commands. CLI supports a package with skill.md and optional references/*.md, which is useful for maintaining local method documents and several references.

What to write

State the tasks the Skill fits and the inputs required before it starts.
Record rules that change the Agent's actions, including sequence, confirmation points, and how references should be used.
Explain how to judge whether the storyboard, generated media, or final video meets the goal.
Replace broad adjectives with concrete criteria.

For example, an episodic-drama Skill can require checking character material before each episode, waiting for storyboard approval before generation, and reusing the specified appearance reference. “This episode takes place on a rainy night” belongs to one project and usually should not become a fixed rule for every project.

Skill file structure

A Skill folder contains:

skill.md: the main Skill document.
references/: an optional directory containing one or more reference documents.

What belongs in skill.md

Suitable content for skill.md:

The Skill's goal and intended use cases.
When it should or should not be used.
Core working methods and decision-making principles.
Creative boundaries that must be respected.
Key checks and acceptance criteria.
How to choose and use reference documents.
What to confirm with the user when information is missing.

A simple rule:

If the Agent needs to know it before every use of the Skill, it belongs in skill.md.

What belongs in reference documents

Suitable content for reference documents:

Brand guides, character profiles, and worldbuilding material.
Detailed cases, strong examples, and counterexamples.
Long templates, glossaries, and style guidance.
Specialist information for a particular type of task.
Material consulted in specific situations, rather than loaded in full every time.
References that change over time and are easier to maintain separately.

A simple rule:

If it provides verification, examples, or background needed only for certain tasks, it belongs in a reference document.

An example

A brand advertising Skill:

skill.md could include:

Product placement must serve the story.
Establish a conflict or need in the first three seconds.
Do not cut away from emotional shots too early just to maintain pace.
Check brand information, pacing, character consistency, and CTA when finished.

references/ could contain:

The brand's visual guidelines.
Previously approved advertisements.
Product selling points and prohibited wording.
Video specifications for different channels.
Character, scene, and shot references.

Tips

Keep one Skill focused on one stable workflow instead of many unrelated scenarios.
Save a Skill from Featured that is close to the goal, then modify its existing structure.
Begin with the few judgment rules that most affect the result; a Skill does not need to become a complete textbook immediately.
A reference is easier to use correctly when the main document says when to read it.
Keep one-time project requirements separate from a reusable method.

Usage limitations

Pasting external Skill content into an ordinary project document does not enable it as a Skill.
Attachments uploaded while creating a Skill are inputs for organizing the method. To depend on them in future runs, keep them as explicit dependencies and check that the main document refers to them.

Use and Share Skills: understand Default Invocation, Historical Usage, and shared copies.
Flova CLI: create and maintain a complete Skill package through a local Agent.
Documents: distinguish ordinary project material, project rules, and Skills.