From a0e0115c384cde3060f6f7250a02d0c5b6b43599 Mon Sep 17 00:00:00 2001 From: Avner Harrari Date: Wed, 18 Nov 2026 17:13:44 +0200 Subject: [PATCH] chore: sync skills from mondaycom/skills@811894d, release 1.0.2 Co-Authored-By: Claude Opus 5.5 --- .gemini-plugin/plugin.json | 2 +- CHANGELOG.md | 6 ++++++ skills.json | 2 +- skills/monday-board-setup/SKILL.md | 6 +++--- .../monday-board-setup/references/column-types-guide.md | 2 +- skills/monday-docs-collaborator/SKILL.md | 2 +- .../monday-docs-collaborator/references/create-modes.md | 2 +- skills/monday-forms-builder/SKILL.md | 9 ++++----- skills/monday-task-management/SKILL.md | 2 +- .../references/column-value-formats.md | 8 ++------ 10 files changed, 21 insertions(+), 20 deletions(-) diff --git a/.gemini-plugin/plugin.json b/.gemini-plugin/plugin.json index 4fea036..9db1d4d 100644 --- a/.gemini-plugin/plugin.json +++ b/.gemini-plugin/plugin.json @@ -1,7 +1,7 @@ { "name": "monday-work-management", "displayName": "monday.com", - "version": "1.0.1", + "version": "1.0.2", "description": "Plan and track work in monday.com from Gemini: set up boards, create, update and assign items, get project status reports, write docs, and build forms that turn requests into items.", "author": { "name": "monday.com", diff --git a/CHANGELOG.md b/CHANGELOG.md index 8a8f5c0..199c06a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,12 @@ All notable changes to this plugin are documented here. Versions follow [Semantic Versioning](https://semver.org). +## 1.0.2 + +- Skills synced from `mondaycom/skills` with live-verified tool behavior: region-safe form links, + partial form header updates, confirmed column formats (color_picker is not writable), and no upload or + invite offers when the tools are not listed. + ## 1.0.1 - Skills synced from `mondaycom/skills` with every tool call matched to the current monday.com MCP tool schemas diff --git a/skills.json b/skills.json index e03699b..1270580 100644 --- a/skills.json +++ b/skills.json @@ -1,6 +1,6 @@ { "repo": "https://github.com/mondaycom/skills.git", - "ref": "6be49b9ae40a5d4a72b11564698519d34dc1786d", + "ref": "811894dca5388c7eb7fce460003c215d3e88f0fe", "prefix": "monday-", "skills": [ "onboard-to-monday", diff --git a/skills/monday-board-setup/SKILL.md b/skills/monday-board-setup/SKILL.md index bf7d63a..be2bf15 100644 --- a/skills/monday-board-setup/SKILL.md +++ b/skills/monday-board-setup/SKILL.md @@ -11,7 +11,7 @@ description: | license: MIT metadata: author: monday.com - version: "0.2.3" + version: "0.2.4" --- # Board Setup @@ -195,7 +195,7 @@ Summarize what was created: Then suggest 2-3 logical next steps: - "Want me to add some initial items to get started?" -- "Should I invite team members to this board?" +- "Should I add teammates who are already on your account to this board?" - "Want me to create a dashboard to track this project?" - "Should I set up a form for intake requests?" @@ -249,7 +249,7 @@ For common workflows (project tracker, bug tracker, CRM pipeline, content calend - If a column type is rejected (e.g., formula on a non-Pro plan), explain the plan gating and propose an alternative column type. - **Detect name collisions before creating.** monday allows two boards with the same name in the same workspace, which is a usability trap. Before calling `create_board`, call `search` with `searchType: "BOARD"` and `searchTerm: ""`, scoped with `workspaceIds: []`. If a board with that name already exists, ask the user: use the existing one, create with a suffix (e.g., "Board Name (2)"), or pick a different name. Skipping this check and creating a duplicate is a fail. - If `columnSettings` JSON is malformed, `create_column` returns an error. The label format requires an array of `{label, color, index}` objects, not a name->color map. See "Custom labels for status columns" above. -- **Date filters in saved views** (`create_view_table` / `update_view_table`) take different values from item filters. Use `between` with two plain `YYYY-MM-DD` dates, `greater_than` / `lower_than` with `"TODAY"`, or `within_the_next` / `within_the_last` with `["DAYS", 7]`. `any_of` with `["EXACT", ""]` is rejected in views, even though `get_column_type_info` guidelines list it - those guidelines are for `get_board_items_page` filters. +- **Date filters in saved views** (`create_view_table`, and `update_view_table` when it is listed) take different values from item filters. Use `between` with two plain `YYYY-MM-DD` dates, `greater_than` / `lower_than` with `"TODAY"`, or `within_the_next` / `within_the_last` with `["DAYS", 7]`. `any_of` with `["EXACT", ""]` is rejected in views, even though `get_column_type_info` guidelines list it - those guidelines are for `get_board_items_page` filters. ## Tools Used diff --git a/skills/monday-board-setup/references/column-types-guide.md b/skills/monday-board-setup/references/column-types-guide.md index c544a24..a8a6793 100644 --- a/skills/monday-board-setup/references/column-types-guide.md +++ b/skills/monday-board-setup/references/column-types-guide.md @@ -170,7 +170,7 @@ Time of day value. ### color_picker -Hex color value. +Hex color value. Not writable through the API; values are set in monday, so the agent cannot fill this column. **Use for:** Brand colors, category colors, design specifications. diff --git a/skills/monday-docs-collaborator/SKILL.md b/skills/monday-docs-collaborator/SKILL.md index 3e90469..d6e6a33 100644 --- a/skills/monday-docs-collaborator/SKILL.md +++ b/skills/monday-docs-collaborator/SKILL.md @@ -11,7 +11,7 @@ description: | license: MIT metadata: author: monday.com - version: "0.2.3" + version: "0.2.4" --- # Docs Collaborator diff --git a/skills/monday-docs-collaborator/references/create-modes.md b/skills/monday-docs-collaborator/references/create-modes.md index 6cd8762..9e8966a 100644 --- a/skills/monday-docs-collaborator/references/create-modes.md +++ b/skills/monday-docs-collaborator/references/create-modes.md @@ -44,5 +44,5 @@ Starting points when the user names a use case. Extend freely; they are examples - Markdown headings (`#`, `##`, `###`) map to LARGE_TITLE / MEDIUM_TITLE / SMALL_TITLE blocks. - Markdown tables work and the cells will be populated with the values you put in. **This is the only way to get pre-filled table content.** Cell-level API population after creation is not supported. -- Markdown images and links work. Markdown cannot reference monday assets: for an image block, use `update_doc` `create_block` with `block_type: "image"` and either `public_url` or `asset_id`. An `asset_id` must already exist - the `assetId` in an item's file column, or the `asset_id` that `finalize_asset_upload` returns after `get_asset_upload_url` (only when the client can PUT the file itself). Do not use the `public_url` from `get_assets` as an image source: it expires after an hour. +- Markdown images and links work. Markdown cannot reference monday assets: for an image block, use `update_doc` `create_block` with `block_type: "image"` and either `public_url` or `asset_id`. An `asset_id` must already exist - the `assetId` in an item's file column, or the `asset_id` that `finalize_asset_upload` returns after `get_asset_upload_url` (only when the client can PUT the file itself). If `get_asset_upload_url` is not in the tool list, use a `public_url` or an existing `asset_id` and do not offer to upload a new file. Do not use the `public_url` from `get_assets` as an image source: it expires after an hour. - Markdown does not have notice_box, layout, embed, divider-with-spacing, mention, or live column-value syntax. Add those via `update_doc` after the doc is created. diff --git a/skills/monday-forms-builder/SKILL.md b/skills/monday-forms-builder/SKILL.md index dd426af..4719e96 100644 --- a/skills/monday-forms-builder/SKILL.md +++ b/skills/monday-forms-builder/SKILL.md @@ -14,7 +14,7 @@ description: | license: MIT metadata: author: monday.com - version: "0.1.3" + version: "0.1.4" --- # Forms Builder @@ -52,7 +52,7 @@ Call `create_form` with: Capture the returned `form_token` (and `board_id`) - every other forms tool takes it as `formToken`. -**`create_form` does not accept a form title parameter.** The form header defaults to "New Form" regardless of `destination_name` (which only names the backing board). Always follow `create_form` with an `update_form` call using `action: "updateFormHeader"` to set `form.title` (and optional `form.description`) before showing the URL to the user. Skipping this leaves every form labeled "New Form" in the WorkForms UI - confusing for end users and for the form owner browsing their forms list. +**`create_form` does not accept a form title parameter.** The form header defaults to "New Form" regardless of `destination_name` (which only names the backing board). Always follow `create_form` with an `update_form` call using `action: "updateFormHeader"` to set `form.title` (and `form.description` if the user gave one) before showing the URL to the user. Skipping this leaves every form labeled "New Form" in the WorkForms UI - confusing for end users and for the form owner browsing their forms list. ### Step 3: Build the question set @@ -96,7 +96,7 @@ After all questions are created, summarize them in a Markdown table (question te Forms are created **active by default**. The form URL works the moment `create_form` returns. If the user wants a draft state (questions still being shaped), call `update_form` with `action: "deactivate"` immediately, finish the questions, then `activate` when ready. Otherwise, share the URL as-is. -`create_form` and `get_form` do not return the public form URL (`get_form` returns `features.shortenedLink.url` once the URL is shortened). Build it from the token. The `?r=` value is the account's data region; `use1` is the example `get_form` documents: +`create_form` does not return the public form URL. To get a link that works in every data region, call `update_form` with `action: "shortenFormUrl"`, then `get_form` and share `features.shortenedLink.url` (a `wkf.ms` link). Only if that fails, build the URL from the token; the `?r=` value is the account's data region, and `use1` is just the example `get_form` documents: ``` https://forms.monday.com/forms/{formToken}?r=use1 @@ -109,7 +109,6 @@ Include both the form URL and the backing board URL (`get_board_info` with the ` End with 2-3 next-step suggestions: - **"Want the form on a single scrolling page (Classic) instead of one question per screen (OneByOne)?"** - Classic is the better default for most operational and internal forms. Surface this choice every time. The MCP tools cannot change it (see below); the suggestion points the user to Form Settings -> Layout in the monday UI. -- "Want me to shorten the form URL?" - "Should I set a password on the form?" - "Should I set a submission limit or close date?" - "Want to remove the WorkForms branding? (Pro+ only.)" @@ -134,7 +133,7 @@ Pick the right tool: - **Add / update / delete a single question:** `form_questions_editor`. - **Reorder questions:** `update_form` with `action: "updateQuestionOrder"` and `form: {questions: [{"id": ""}, {"id": ""}, ...]}` (objects with required `id` and optional `page_block_id`, with every existing question included). -- **Header (title and description):** `update_form` with `action: "updateFormHeader"` (`form.title` and optional `form.description`). +- **Header (title and description):** `update_form` with `action: "updateFormHeader"` (`form.title`, `form.description`, or both; at least one is required, and a field you omit keeps its current value). - **Branding, layout, colors, logo:** `update_form` with `action: "updateAppearance"`. - **Submission rules (anonymous, response limit, close date, login required, captcha):** `update_form` with `action: "updateFeatures"`. - **Activate / deactivate / shorten URL / set password:** corresponding actions. diff --git a/skills/monday-task-management/SKILL.md b/skills/monday-task-management/SKILL.md index f207752..77dfe15 100644 --- a/skills/monday-task-management/SKILL.md +++ b/skills/monday-task-management/SKILL.md @@ -11,7 +11,7 @@ description: | license: MIT metadata: author: monday.com - version: "0.2.2" + version: "0.2.3" --- # Task Management diff --git a/skills/monday-task-management/references/column-value-formats.md b/skills/monday-task-management/references/column-value-formats.md index d1b8c6f..a98c314 100644 --- a/skills/monday-task-management/references/column-value-formats.md +++ b/skills/monday-task-management/references/column-value-formats.md @@ -189,7 +189,7 @@ Geographic location. ## Additional Column Types -> **Note:** The write tools' built-in format guide does not cover the types below (`rating`, `country`, `world_clock`, `week`, `hour`, `color_picker`), and `get_column_type_info` returns settings schemas, not value formats. If a write is rejected, show the user the API error before trying another shape. +> **Note:** The write tools' built-in format guide does not cover the types below, and `get_column_type_info` returns settings schemas, not value formats. The shapes below were confirmed with `change_item_column_values` and read back. If a write is rejected, show the user the API error before trying another shape. ### Rating @@ -233,11 +233,7 @@ Time value. ### Color Picker -Nested hex color object. - -```json -{"color_picker_column_id": {"color": {"hex": "#FF5733"}}} -``` +Not writable through the API: any write fails with `InvalidColumnTypeException` ("This column type is not supported yet in the API"). Tell the user to set it in monday. ## Combining Multiple Columns