Update to Vaiz

{
  "description": "Upload files to Vaiz tasks, milestones, and documents from local disk or a public URL, insert them into document bodies or comments, remove them again, and read attached files back including inline images and text.",
  "included_files": [],
  "name": "vaiz-files",
  "skill_md_contents": "---\nname: vaiz-files\ndescription: Upload files to Vaiz tasks, milestones, and documents from local disk or a public URL, insert them into document bodies or comments, remove them again, and read attached files back including inline images and text.\n---\n\n# Vaiz files\n\nFiles in Vaiz are always attached to an entity: a task, a milestone, or a document. Uploading is a two-step process (get an upload URL, then send bytes); attaching is a separate call.\n\n## Prerequisite\n\nThe Vaiz MCP server (`https://api.vaiz.com/mcp`) must be available through the installed Vaiz plugin and authorized with OAuth (open the Vaiz connection and complete OAuth sign-in). Local uploads also require the ability to run an HTTP request (for example `curl` in the terminal).\n\nVaiz tools can appear under different names depending on how Vaiz is connected: `mcp__Vaiz__query_tasks` for a directly configured MCP server, or `mcp__codex_apps__vaiz_query_tasks` (sometimes with a longer app prefix such as `vaiz_testing_`) when Vaiz is installed as an app. Match tool names case-insensitively and by the tool suffix (`query_tasks`, `show_tasks`, …), not by an exact `Vaiz` prefix. Tools may also be loaded lazily: a Vaiz tool that is not in the current tool list is not missing — load it through tool search (for example `Vaiz query_tasks`) before concluding it is unavailable. Work with Vaiz only through these tools: do not open app.vaiz.com in a browser or drive the Vaiz desktop app with Computer Use, even if the user's `@Vaiz` mention also resolves to that app.\n\n## Uploading a local file\n\n1. `prepare_file_upload` with `entityType` (`\"task\"`, `\"milestone\"`, `\"document\"`), `entityId` (task HRID or id; 24-char id for others), `fileName` with extension, and optionally `size` in bytes so oversized files are rejected early. The response contains a short-lived upload URL (15 minutes) and a `curlExample`.\n2. Send the bytes to that URL — `PUT` with the raw body, or `POST multipart/form-data`. The HTTP response contains the new `fileId`.\n3. Attach the `fileId` (next section).\n\n## Importing from a URL\n\n`upload_file_from_url` with `entityType`, `entityId`, and a public `https://` `url`; optional `fileName` overrides the stored name. Private networks and localhost are rejected. Returns a `fileId`. Use this for CI artifacts, screenshots already hosted online, or when you cannot run HTTP uploads yourself.\n\n## Attaching\n\n- `attach_files_to_document` — append up to 20 `fileIds` to the body of the same entity they were uploaded for. Images become Image blocks, videos Video blocks, everything else a Files block. Order is preserved.\n- `create_comment` with `fileIds` — attach to a new comment on that entity instead; `content` may be omitted when files are provided.\n\nFiles must be attached to the entity they were uploaded for; you cannot upload to one task and attach to another.\n\n## Removing\n\n- From a document body: `replace_document_fragment` — find the file block as `get_document` shows it and replace it with an empty string (see `vaiz-documents`).\n- From one of your comments: `edit_comment` with `removeFileIds` (the `files[]._id` values from `get_task_comments` / `get_document_comments`).\n\n## Reading a file\n\n`read_file` with `file` set to the 24-char file id or the file URL seen in `documentContent` or comments. Returns metadata and a short-lived `downloadUrl` (15 minutes, plain GET, no auth headers). With `includeContent: true`:\n\n- images are returned inline, downscaled to 1600px\n- text-like files (txt, md, csv, json, code) are returned as UTF-8 text, first 100k characters\n- PDFs and other binaries: use `downloadUrl`\n- videos are not served\n\nThis is a heavy operation. Call it only when the user asks about a specific file, and set `includeContent: false` when metadata is enough.\n\n## Good habits\n\n- Name files descriptively (`login-flow-diagram.png`, not `image1.png`).\n- Prefer `upload_file_from_url` when the file already has a public URL.\n- Reuse the same `fileId` for both the body and a comment only if it really belongs in both places.\n\nFurther reading: https://vaiz.com/help/tutorials/how-to-connect-vaiz-to-mcp · https://vaiz.com\n"
}