agentleFS
Sign inStart free
descriptincdescriptinc/descript-mcp/skills/export-timeline/SKILL.md

export-timeline

Skill37 starsChanged 43 days agoApache-2.0View on GitHub

Export a Descript project's timeline for another editor like Premiere Pro, DaVinci Resolve, Final Cut Pro, or Pro Tools.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user wants to continue editing in another NLE or DAW (Premiere Pro, DaVinci Resolve, Final Cut Pro, Pro Tools, Logic, Audition, …

    line 10
  2. Distinctive:

    When they ask for a timeline, XML, EDL, AAF, or interchange file

    line 11
  3. Very specific:

    If the project has more than one composition, confirm which one and pass its composition_id explicitly.

    line 16
  4. Very specific:

    Call export_timeline with the project ID, composition ID, and a format (edl, sesx, fcp, premiere, davinci_resolve, or aaf).

    line 17

≈ “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

Export Timeline

When to use

  • When the user wants to continue editing in another NLE or DAW (Premiere Pro, DaVinci Resolve, Final Cut Pro, Pro Tools, Logic, Audition, Reaper)
  • When they ask for a timeline, XML, EDL, AAF, or interchange file

Instructions

  1. Locate the project with search_drive (or list_projects if filtering/paginating the project list), then use get_project to retrieve its composition IDs.
  2. If the project has more than one composition, confirm which one and pass its composition_id explicitly.
  3. Call export_timeline with the project ID, composition ID, and a format (edl, sesx, fcp, premiere, davinci_resolve, or aaf). Media files are never bundled — only the timeline file itself.
  4. export_timeline is asynchronous and returns a job_id. Wait for it by polling wait_for_job with wait_seconds: 20 until the job is terminal, surfacing progress.label/percent. A timeout (-32001) or a still_running wait status means it is still going — poll the same job_id again, never re-export.
  5. Report the download_url from the completed job's result back to the user. It is time-limited (valid until download_url_expires_at), so tell the user to download promptly.

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.

Check your setup, free