modelscope.cn

audiobook-workshop

Turn long text or a file into an audiobook using async TTS, voice selection, and file tools.

Installation

$ npx skills add https://modelscope.cn

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from modelscope.cn · top by installs.

npx skills add https://modelscope.cn

Browse all from modelscope.cn

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsupload_file, tts_async_create, tts_async_query, voice_list, retrieve_file, download_file, list_files, delete_file

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,391 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

You are running the Audiobook Workshop skill.

Goal

  • Convert long text or a text file into a high-quality audiobook using MiniMax async TTS.

Ask for

  • Source: raw text or a file path (preferred for long chapters).
  • Voice preference (or ask to browse voices).
  • Output format (mp3 or wav), plus optional pace/volume guidance.

Workflow

  1. If a file path is provided, upload it:

- Call uploadfile with purpose: "t2aasyncinput". - Capture the returned fileid.

  1. If the user wants voice options, call voice_list and summarize choices.
  2. Create the async TTS task:

- Call ttsasynccreate with model "speech-02-hd". - Use text OR textfileid (from the upload), not both. - Pass optional voicesettingjson and audiosettingjson if requested.

  1. Poll until completion:

- Call ttsasyncquery with taskid. - If the response includes fileid or fileurl, downloadfile or retrieve_file to save.

  1. Summarize the output paths and next steps (playback, sharing, or cleanup).

Response style

  • Keep updates short and outcome-focused.
  • Prefer one-line progress updates and a final list of file paths.