← SpeechdubCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Speechdub
Snapshot Sep 30, 2026 · 22:55 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"name": "speechdub-text-to-speech",
"description": "Generate spoken audio with Speechdub preset voices when the user wants text read aloud, a voice preview, or audio output from their content.",
"included_files": [],
"skill_md_contents": "---\nname: speechdub-text-to-speech\ndescription: Generate spoken audio with Speechdub preset voices when the user wants text read aloud, a voice preview, or audio output from their content.\n---\n\n# Speechdub text-to-speech\n\nUse when the user wants **audio** or **read aloud** via Speechdub voices, not only silent text in chat.\n\n## Tools\n\n- `speechdub_list_voices` — optional `gender` filter (`male` | `female`).\n- `speechdub_get_voice` — metadata for one `voice_id` (presets like `F1`, `M3`).\n- `speechdub_synthesize_speech` — required `input` (max 5000 chars) and `voice_id`; optional `language`, `audio_format` (`wav` | `mp3`), `include_audio_data`.\n\n## Workflow\n\n1. Always call `speechdub_list_voices` (or `speechdub_get_voice` if they named a preset) **before** synthesis unless a valid `voice_id` is already confirmed.\n2. Pick a voice that matches the user’s language or preference; say which voice you chose.\n3. Split long text into chunks under 5000 characters if needed; synthesize per chunk.\n4. Report billing context briefly: synthesis uses the user’s Speechdub credit wallet (same as the web app). Do not quote API keys.\n5. If `include_audio_data` is false or omitted, describe the result (duration, format, request id) per tool output; follow the client’s rules for playing or attaching audio.\n\n## Boundaries\n\n- Do not create or delete library documents unless the user also asked for library changes.\n- Prefer synthesis on user-supplied or document text they explicitly want heard; do not synthesize huge documents without narrowing scope.\n"
}SHA-256: f599f598c153518b4004ce2f721bb06c79eba8a57f12b98972d1605afae2b901