agentleFS
descriptincdescriptinc/descript-mcp/skills/edit-project/SKILL.md

edit-project

Skill37 starsChanged 43 days agoApache-2.0View on GitHub

Edit an existing Descript project with Underlord, Descript's AI co-editor, using natural language instructions.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When modifying an existing Descript project

    line 10
  2. Distinctive:

    When applying Underlord edits like trimming, captioning, or rearranging

    line 11
  3. Distinctive:

    When the user wants to make changes to a video or audio project they've already created

    line 12
  4. Very specific:

    Use search_drive to find the project when the user describes it by name or spoken content.

    line 16
  5. Very specific:

    Use get_project with the project ID to inspect its current state — compositions, media files, and structure.

    line 17
  6. Very specific:

    Wait for the edit by polling wait_for_job with wait_seconds: 20 until the job is terminal, surfacing progress.label/percent after each poll.

    line 20

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

Edit Project

When to use

  • When modifying an existing Descript project
  • When applying Underlord edits like trimming, captioning, or rearranging
  • When the user wants to make changes to a video or audio project they've already created

Instructions

  1. Use search_drive to find the project when the user describes it by name or spoken content. Use list_projects (filter by name if provided) when you need a paginated project list rather than a search.
  2. Use get_project with the project ID to inspect its current state — compositions, media files, and structure.
  3. Confirm with the user which composition to edit if the project has multiple compositions.
  4. Use prompt_project_agent to edit with Underlord, Descript's AI co-editor, passing the project ID, composition ID, and a clear natural language prompt describing the desired edits. Follow the user's instructions as given. If the result includes a conversation_id, save it and reuse it on follow-up edits anywhere in the same project to continue the same thread, including edits that target a different composition; pass the target composition_id alongside it to say which clip to edit. Don't start a second agent job for the same clip while one is still in flight.
  5. Wait for the edit by polling wait_for_job with wait_seconds: 20 until the job is terminal, surfacing progress.label/percent after each poll. A timeout (-32001) means the edit is still running — poll the same job_id again, don't re-issue the prompt.
  6. Confirm the edit landed from the completed job result (and the composition state) — not get_project.updated_at. Use get_project to report the result back to the user.

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.