Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aiskillstore/fish-audio
Generate AI text-to-speech audio with Fish Audio and browse public reference voices via AceDataCloud API.
Passed 22 of 22 test cases with the skill, and 9 of 22 without it.
and 15 more in the full report
13 fixed9 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When sending a POST request to generate audio via AceDataCloud's Fish Audio API, should the URL path be `/fish/audios`, `/v1/tts`, or `/fish/tts`?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies /fish/tts as the correct API path | Missed | Passed |
The instructions your model reads when the skill loads.
Generate narration / voiceover through AceDataCloud's Fish Audio API.
Setup: See authentication for token setup.
curl -X POST https://api.acedata.cloud/fish/tts \
-H "Authorization: ******ACEDATACLOUD_API_TOKEN" \
-H "Content-Type: application/json" \
-H "model: s2-pro" \
-d '{"text":"你好,欢迎使用 AceData Cloud。","reference_id":"d7900c21663f485ab63ebdb7e5905036","format":"mp3"}'
Synchronous responses return a direct audio URL:
{"audio_url":"https://platform.r2.fish.audio/task/8a72ff9840234006a9f74cb2fa04f978.mp3"}
| Endpoint | Purpose |
|---|---|
POST /fish/tts | Text-to-speech generation |
GET /fish/model | Browse/search public Fish reference voices |
POST /fish/tasks | Poll async TTS jobs when async: true |
curl "https://api.acedata.cloud/fish/model?page_size=10&page_number=1&title=Marcus" \
-H "Authorization: ******ACEDATACLOUD_API_TOKEN"
The response includes items[] with public voice metadata such as _id, title,
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.