Descript Connector for Muse
Drive Descript editing and publishing through its API (open beta).
- What
- Drive Descript editing and publishing through its API (open beta).
- Cost
- Free
- Needs
- A Descript API key (your Descript account's API settings), kept in your Muse's secure vault (never paste secrets here). Note: publishing sends content live and burns Descript credits — always confirm the project first; Descript has a free plan.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
A Muse agent skill that works with Descript's API (open beta): list projects, inspect Underlord/agent jobs, submit a publish job, and poll the job until it finishes. Publishing sends content live and burns Descript credits — the skill always confirms the project first. Honest note: Descript usage is credit-based; every publish job costs credits, and the publish request body may need adjusting per project. Descript has a free plan. Draft: written from Descript's public API docs, not yet live-tested end-to-end — this listing's unverified status reflects that. No secrets in the repo.
Curated by Skill Harbor — free, open-source build (MIT) by @bluman1.
Version:
Install
Prerequisites: A Descript API key (your Descript account's API settings), kept in your Muse's secure vault (never paste secrets here). Note: publishing sends content live and burns Descript credits — always confirm the project first; Descript has a free plan. No GitHub account needed unless listed here. Install "Descript Connector for Muse" for me. A Muse agent skill that drives Descript editing and publishing via its API (open beta): list projects, inspect agent jobs, submit publish jobs, poll job status. Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/descript 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "descript". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my Descript API key in the vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.