← 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": "edit-speechdub-document",
"description": "Rename or update text and language of an existing Speechdub document the user owns, or permanently delete a document when they explicitly request removal.",
"included_files": [],
"skill_md_contents": "---\nname: edit-speechdub-document\ndescription: Rename or update text and language of an existing Speechdub document the user owns, or permanently delete a document when they explicitly request removal.\n---\n\n# Edit or remove Speechdub documents\n\nUse when the user wants to **change** a saved document (title, body, language) or **delete** one they identify by name or id.\n\n## Tools\n\n- `speechdub_list_documents` / `speechdub_get_document` — resolve `document_id` when the user only gives a title or vague reference.\n- `speechdub_update_document` — `document_id` plus any of `title`, `text`, `language`.\n- `speechdub_delete_document` — `document_id` only; **permanent**.\n\n## Workflow\n\n1. Resolve the target document id (list + get if needed). Do not guess UUIDs.\n2. For renames or content edits, use `speechdub_update_document` with only the fields that should change.\n3. For deletion, confirm the user intent when ambiguous (title + id). Then call `speechdub_delete_document` once.\n4. After delete, state clearly that the document was removed and cannot be restored via the API.\n\n## Boundaries\n\n- `speechdub_delete_document` is destructive; do not use it for “archive” or “clear chat” requests unless they mean delete from Speechdub.\n- Do not create new documents here (use import-to-speechdub).\n"
}SHA-256: 54ca24e4e47d7399e88ca10a57be0b53f1821dc261fe7762358efce1e52335a2