agentleFS
Sign inStart free
descriptincdescriptinc/descript-mcp/skills/publish-project/SKILL.md

publish-project

Skill37 starsChanged 43 days agoApache-2.0View on GitHub

Publish a Descript project composition to create a shareable link and exported video or audio file.

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 is ready to share or export a finished project

    line 10
  2. Distinctive:

    When they ask for a shareable link or a downloadable video/audio file

    line 11
  3. Very specific:

    Call publish_project with the project ID and composition ID.

    line 18
  4. Very specific:

    Wait for publishing to finish by polling wait_for_job with the returned job_id and wait_seconds: 20 until the job is terminal.

    line 19

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

Publish Project

When to use

  • When the user is ready to share or export a finished project
  • When they ask for a shareable link or a downloadable video/audio 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 and any existing publishes.
  2. Confirm with the user which composition to publish if there is more than one.
  3. Confirm the user actually wants to publish before calling publish_project. Publishing is user-visible and republishing the same composition overwrites the previous output at the same share URL — get explicit authorization before publishing or overwriting an existing publish. The host may also surface its own approval prompt.
  4. Call publish_project with the project ID and composition ID. To retrieve an existing share link without republishing, read it from get_project instead of calling publish_project.
  5. Wait for publishing to finish by polling wait_for_job with the returned job_id and wait_seconds: 20 until the job is terminal. A timeout (-32001) or a still_running wait status means it is still going — poll the same job_id again, never re-publish.
  6. Report the share_url and download_url from the completed job back to the user exactly as returned — do not edit or shorten them.

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