agentleFS
badgidsbadgids/Story-Film-Skills/skills/kdenlive-export/SKILL.md

kdenlive-export

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Create a current Generation 5 Kdenlive .kdenlive project from canonical editorial state using Kdenlive document version 1.1, main_bin, sequence and track tractors, MLT playlists, source producers, optional effects/transitions, and portable media references.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the canonical advanced editor manifest when multitrack layering or MLT effects/transitions are required.

    line 14
  2. Distinctive:

    Keep media resources project-relative.

    line 22
  3. Distinctive:

    If a specific installed Kdenlive version must be certified, open the generated project in that version before claiming import success.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Kdenlive Export

Workflow

  1. Read ../../references/EDITOR_PROJECT_EXPORT.md.
  2. Use the canonical advanced editor manifest when multitrack layering or MLT effects/transitions are required.
  3. Export with:
python scripts/editor_project_export.py PROJECT --target kdenlive --require-sources
  1. Confirm the output contains a Generation 5 main_bin, document version 1.1, sequence tractor with kdenlive:uuid, Kdenlive track tractors/playlists, and final project tractor wrapper.
  2. Keep media resources project-relative.
  3. If a specific installed Kdenlive version must be certified, open the generated project in that version before claiming import success.

Done

A structurally valid .kdenlive project exists at the requested location and represents the declared editorial tracks/cuts/effects without fabricated editor-private state.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.