Update to Letter.md

{
  "description": "Use when the user wants to create, find, open, read, or revise a Letter.md document. Guides safe document selection, creation, editor opening, and reviewable suggestions with Letter.md MCP tools.",
  "included_files": [],
  "name": "letter-document-authoring",
  "skill_md_contents": "---\nname: letter-document-authoring\ndescription: Use when the user wants to create, find, open, read, or revise a Letter.md document. Guides safe document selection, creation, editor opening, and reviewable suggestions with Letter.md MCP tools.\n---\n\n# Letter.md document authoring\n\nUse Letter.md as the source of truth for document identity and current content. Keep reads and writes separate so the user can understand what will change.\n\n## Choose the document\n\n- Use an explicit \"documentId\" when the user supplied one.\n- Use \"list_documents\" when the title is ambiguous or the user wants to browse. Use \"search_workspace_documents\" when the user describes document content instead of its title.\n- Use \"render_letter_editor\" without a document ID only when the user explicitly asks for their latest document.\n- If multiple documents remain plausible, present the short candidates and ask the user to choose instead of guessing.\n\n## Create a document\n\n1. Draft complete Markdown before saving.\n2. Call \"create_document\" only when the user asked to create or save a new Letter.md document. Supply a useful title and the finished Markdown. Omit \"idempotencyKey\" for normal retries.\n3. Use the returned document ID with \"render_letter_editor\" so the user can continue in the collaborative editor.\n\nCreating a new document never means overwriting an existing document. Do not use \"create_document_from_ai\" outside an active in-editor derivative workflow.\n\n## Read or revise an existing document\n\n1. Call \"get_document\" before quoting, summarizing, or proposing changes so the response uses the latest Markdown and block IDs.\n2. For requested edits, call \"create_suggestion\" with narrow operations anchored to exact current block IDs and text. Prefer \"replace_text\" for a local edit and include prefix or suffix context when the same text can occur more than once.\n3. Explain that a suggestion is reviewable and does not change the document until the user accepts it.\n4. Call \"render_letter_editor\" when the user asks to open the document or when visual review and acceptance are the natural next step.\n\nDo not claim that a suggestion was accepted or that document content changed unless a later tool result confirms it.\n"
}