[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CM7Z9CD8FP5FM3AE4KMSWW":3,"skill-same:01M7CM7Z9CD8FP5FM3AE4KMSWW":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CM7Z9CD8FP5FM3AE4KMSWW","monday-automation",null,"Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fmonday-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: monday-automation\ndescription: \"Automate Monday.com work management including boards, items, columns, groups, subitems, and updates via Rube MCP (Composio). Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Monday.com Automation via Rube MCP\n\nAutomate Monday.com work management workflows including board creation, item management, column value updates, group organization, subitems, and update\u002Fcomment threads through Composio's Monday toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Monday.com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `monday`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `monday`\n3. If connection is not ACTIVE, follow the returned auth link to complete Monday.com OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Boards\n\n**When to use**: User wants to create a new board, list existing boards, or set up workspace structure.\n\n**Tool sequence**:\n1. `MONDAY_GET_WORKSPACES` - List available workspaces and resolve workspace ID [Prerequisite]\n2. `MONDAY_LIST_BOARDS` - List existing boards to check for duplicates [Optional]\n3. `MONDAY_CREATE_BOARD` - Create a new board with name, kind, and workspace [Required]\n4. `MONDAY_CREATE_COLUMN` - Add columns to the new board [Optional]\n5. `MONDAY_CREATE_GROUP` - Add groups to organize items [Optional]\n6. `MONDAY_BOARDS` - Retrieve detailed board metadata [Optional]\n\n**Key parameters**:\n- `board_name`: Name for the new board (required)\n- `board_kind`: \"public\", \"private\", or \"share\" (required)\n- `workspace_id`: Numeric workspace ID; omit for default workspace\n- `folder_id`: Folder ID; must be within `workspace_id` if both provided\n- `template_id`: ID of accessible template to clone\n\n**Pitfalls**:\n- `board_kind` is required and must be one of: \"public\", \"private\", \"share\"\n- If both `workspace_id` and `folder_id` are provided, the folder must exist within that workspace\n- `template_id` must reference a template the authenticated user can access\n- Board IDs are large integers; always use the exact value from API responses\n\n### 2. Create and Manage Items\n\n**When to use**: User wants to add tasks\u002Fitems to a board, list existing items, or move items between groups.\n\n**Tool sequence**:\n1. `MONDAY_LIST_BOARDS` - Resolve board name to board ID [Prerequisite]\n2. `MONDAY_LIST_GROUPS` - List groups on the board to get group_id [Prerequisite]\n3. `MONDAY_LIST_COLUMNS` - Get column IDs and types for setting values [Prerequisite]\n4. `MONDAY_CREATE_ITEM` - Create a new item with name and column values [Required]\n5. `MONDAY_LIST_BOARD_ITEMS` - List all items on the board [Optional]\n6. `MONDAY_MOVE_ITEM_TO_GROUP` - Move an item to a different group [Optional]\n7. `MONDAY_ITEMS_PAGE` - Paginated item retrieval with filtering [Optional]\n\n**Key parameters**:\n- `board_id`: Board ID (required, integer)\n- `item_name`: Item name, max 256 characters (required)\n- `group_id`: Group ID string to place the item in (optional)\n- `column_values`: JSON object or string mapping column IDs to values\n\n**Pitfalls**:\n- `column_values` must use column IDs (not titles); get them from `MONDAY_LIST_COLUMNS`\n- Column value formats vary by type: status uses `{\"index\": 0}` or `{\"label\": \"Done\"}`, date uses `{\"date\": \"YYYY-MM-DD\"}`, people uses `{\"personsAndTeams\": [{\"id\": 123, \"kind\": \"person\"}]}`\n- `item_name` has a 256-character maximum\n- Subitem boards are NOT supported by `MONDAY_CREATE_ITEM`; use GraphQL via `MONDAY_CREATE_OBJECT`\n\n### 3. Update Item Column Values\n\n**When to use**: User wants to change status, date, text, or other column values on existing items.\n\n**Tool sequence**:\n1. `MONDAY_LIST_COLUMNS` or `MONDAY_COLUMNS` - Get column IDs and types [Prerequisite]\n2. `MONDAY_LIST_BOARD_ITEMS` or `MONDAY_ITEMS_PAGE` - Find the target item ID [Prerequisite]\n3. `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` - Update text, status, or dropdown with a string value [Required]\n4. `MONDAY_UPDATE_ITEM` - Update complex column types (timeline, people, date) with JSON [Required]\n\n**Key parameters for MONDAY_CHANGE_SIMPLE_COLUMN_VALUE**:\n- `board_id`: Board ID (integer, required)\n- `item_id`: Item ID (integer, required)\n- `column_id`: Column ID string (required)\n- `value`: Simple string value (e.g., \"Done\", \"Working on it\")\n- `create_labels_if_missing`: true to auto-create status\u002Fdropdown labels (default true)\n\n**Key parameters for MONDAY_UPDATE_ITEM**:\n- `board_id`: Board ID (integer, required)\n- `item_id`: Item ID (integer, required)\n- `column_id`: Column ID string (required)\n- `value`: JSON object matching the column type schema\n- `create_labels_if_missing`: false by default; set true for status\u002Fdropdown\n\n**Pitfalls**:\n- Use `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` for simple text\u002Fstatus\u002Fdropdown updates (string value)\n- Use `MONDAY_UPDATE_ITEM` for complex types like timeline, people, date (JSON value)\n- Column IDs are lowercase strings with underscores (e.g., \"status_1\", \"date_2\", \"text\"); get them from `MONDAY_LIST_COLUMNS`\n- Status values can be set by label name (\"Done\") or index number (\"1\")\n- `create_labels_if_missing` defaults differ: true for CHANGE_SIMPLE, false for UPDATE_ITEM\n\n### 4. Work with Groups and Board Structure\n\n**When to use**: User wants to organize items into groups, add columns, or inspect board structure.\n\n**Tool sequence**:\n1. `MONDAY_LIST_BOARDS` - Resolve board ID [Prerequisite]\n2. `MONDAY_LIST_GROUPS` - List all groups on a board [Required]\n3. `MONDAY_CREATE_GROUP` - Create a new group [Optional]\n4. `MONDAY_LIST_COLUMNS` or `MONDAY_COLUMNS` - Inspect column structure [Required]\n5. `MONDAY_CREATE_COLUMN` - Add a new column to the board [Optional]\n6. `MONDAY_MOVE_ITEM_TO_GROUP` - Reorganize items across groups [Optional]\n\n**Key parameters**:\n- `board_id`: Board ID (required for all group\u002Fcolumn operations)\n- `group_name`: Name for new group (CREATE_GROUP)\n- `column_type`: Must be a valid GraphQL enum token in snake_case (e.g., \"status\", \"text\", \"long_text\", \"numbers\", \"date\", \"dropdown\", \"people\")\n- `title`: Column display title\n- `defaults`: JSON string for status\u002Fdropdown labels, e.g., `'{\"labels\": [\"To Do\", \"In Progress\", \"Done\"]}'`\n\n**Pitfalls**:\n- `column_type` must be exact snake_case values; \"person\" is NOT valid, use \"people\"\n- Group IDs are strings (e.g., \"topics\", \"new_group_12345\"), not integers\n- `MONDAY_COLUMNS` accepts an array of `board_ids` and returns column metadata including settings\n- `MONDAY_LIST_COLUMNS` is simpler and takes a single `board_id`\n\n### 5. Manage Subitems and Updates\n\n**When to use**: User wants to view subitems of a task or add comments\u002Fupdates to items.\n\n**Tool sequence**:\n1. `MONDAY_LIST_BOARD_ITEMS` - Find parent item IDs [Prerequisite]\n2. `MONDAY_LIST_SUBITEMS_BY_PARENT` - Retrieve subitems with column values [Required]\n3. `MONDAY_CREATE_UPDATE` - Add a comment\u002Fupdate to an item [Optional]\n4. `MONDAY_CREATE_OBJECT` - Create subitems via GraphQL mutation [Optional]\n\n**Key parameters for MONDAY_LIST_SUBITEMS_BY_PARENT**:\n- `parent_item_ids`: Array of parent item IDs (integer array, required)\n- `include_column_values`: true to include column data (default true)\n- `include_parent_fields`: true to include parent item info (default true)\n\n**Key parameters for MONDAY_CREATE_OBJECT** (GraphQL):\n- `query`: Full GraphQL mutation string\n- `variables`: Optional variables object\n\n**Pitfalls**:\n- Subitems can only be queried through their parent items\n- To create subitems, use `MONDAY_CREATE_OBJECT` with a `create_subitem` GraphQL mutation\n- `MONDAY_CREATE_UPDATE` is for adding comments\u002Fupdates to items (Monday's \"updates\" feature), not for modifying item values\n- `MONDAY_CREATE_OBJECT` is a raw GraphQL endpoint; ensure correct mutation syntax\n\n## Common Patterns\n\n### ID Resolution\nAlways resolve display names to IDs before operations:\n- **Board name -> board_id**: `MONDAY_LIST_BOARDS` and match by name\n- **Group name -> group_id**: `MONDAY_LIST_GROUPS` with `board_id`\n- **Column title -> column_id**: `MONDAY_LIST_COLUMNS` with `board_id`\n- **Workspace name -> workspace_id**: `MONDAY_GET_WORKSPACES` and match by name\n- **Item name -> item_id**: `MONDAY_LIST_BOARD_ITEMS` or `MONDAY_ITEMS_PAGE`\n\n### Pagination\nMonday.com uses cursor-based pagination for items:\n- `MONDAY_ITEMS_PAGE` returns a `cursor` in the response for the next page\n- Pass the `cursor` to the next call; `board_id` and `query_params` are ignored when cursor is provided\n- Cursors are cached for 60 minutes\n- Maximum `limit` is 500 per page\n- `MONDAY_LIST_BOARDS` and `MONDAY_GET_WORKSPACES` use page-based pagination with `page` and `limit`\n\n### Column Value Formatting\nDifferent column types require different value formats:\n- **Status**: `{\"index\": 0}` or `{\"label\": \"Done\"}` or simple string \"Done\"\n- **Date**: `{\"date\": \"YYYY-MM-DD\"}`\n- **People**: `{\"personsAndTeams\": [{\"id\": 123, \"kind\": \"person\"}]}`\n- **Text\u002FNumbers**: Plain string or number\n- **Timeline**: `{\"from\": \"YYYY-MM-DD\", \"to\": \"YYYY-MM-DD\"}`\n\n## Known Pitfalls\n\n### ID Formats\n- Board IDs and item IDs are large integers (e.g., 1234567890)\n- Group IDs are strings (e.g., \"topics\", \"new_group_12345\")\n- Column IDs are short strings (e.g., \"status_1\", \"date4\", \"text\")\n- Workspace IDs are integers\n\n### Rate Limits\n- Monday.com GraphQL API has complexity-based rate limits\n- Large boards with many columns increase query complexity\n- Use `limit` parameter to reduce items per request if hitting limits\n\n### Parameter Quirks\n- `column_type` for CREATE_COLUMN must be exact snake_case enum values; \"people\" not \"person\"\n- `column_values` in CREATE_ITEM accepts both JSON string and object formats\n- `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` auto-creates missing labels by default; `MONDAY_UPDATE_ITEM` does not\n- `MONDAY_CREATE_OBJECT` is a raw GraphQL interface; use it for operations without dedicated tools (e.g., create_subitem, delete_item, archive_board)\n\n### Response Structure\n- Board items are returned as arrays with `id`, `name`, and `state` fields\n- Column values include both raw `value` (JSON) and rendered `text` (display string)\n- Subitems are nested under parent items and cannot be queried independently\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List workspaces | `MONDAY_GET_WORKSPACES` | `kind`, `state`, `limit` |\n| Create workspace | `MONDAY_CREATE_WORKSPACE` | `name`, `kind` |\n| List boards | `MONDAY_LIST_BOARDS` | `limit`, `page`, `state` |\n| Create board | `MONDAY_CREATE_BOARD` | `board_name`, `board_kind`, `workspace_id` |\n| Get board metadata | `MONDAY_BOARDS` | `board_ids`, `board_kind` |\n| List groups | `MONDAY_LIST_GROUPS` | `board_id` |\n| Create group | `MONDAY_CREATE_GROUP` | `board_id`, `group_name` |\n| List columns | `MONDAY_LIST_COLUMNS` | `board_id` |\n| Get column metadata | `MONDAY_COLUMNS` | `board_ids`, `column_types` |\n| Create column | `MONDAY_CREATE_COLUMN` | `board_id`, `column_type`, `title` |\n| Create item | `MONDAY_CREATE_ITEM` | `board_id`, `item_name`, `column_values` |\n| List board items | `MONDAY_LIST_BOARD_ITEMS` | `board_id` |\n| Paginated items | `MONDAY_ITEMS_PAGE` | `board_id`, `limit`, `query_params` |\n| Update column (simple) | `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` | `board_id`, `item_id`, `column_id`, `value` |\n| Update column (complex) | `MONDAY_UPDATE_ITEM` | `board_id`, `item_id`, `column_id`, `value` |\n| Move item to group | `MONDAY_MOVE_ITEM_TO_GROUP` | `item_id`, `group_id` |\n| List subitems | `MONDAY_LIST_SUBITEMS_BY_PARENT` | `parent_item_ids` |\n| Add comment\u002Fupdate | `MONDAY_CREATE_UPDATE` | `item_id`, `body` |\n| Raw GraphQL mutation | `MONDAY_CREATE_OBJECT` | `query`, `variables` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Monday.com Automation via Rube MCP\n\nAutomate Monday.com work management workflows including board creation, item management, column value updates, group organization, subitems, and update\u002Fcomment threads through Composio's Monday toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Monday.com connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `monday`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `monday`\n3. If connection is not ACTIVE, follow the returned auth link to complete Monday.com OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Boards\n\n**When to use**: User wants to create a new board, list existing boards, or set up workspace structure.\n\n**Tool sequence**:\n1. `MONDAY_GET_WORKSPACES` - List available workspaces and resolve workspace ID [Prerequisite]\n2. `MONDAY_LIST_BOARDS` - List existing boards to check for duplicates [Optional]\n3. `MONDAY_CREATE_BOARD` - Create a new board with name, kind, and workspace [Required]\n4. `MONDAY_CREATE_COLUMN` - Add columns to the new board [Optional]\n5. `MONDAY_CREATE_GROUP` - Add groups to organize items [Optional]\n6. `MONDAY_BOARDS` - Retrieve detailed board metadata [Optional]\n\n**Key parameters**:\n- `board_name`: Name for the new board (required)\n- `board_kind`: \"public\", \"private\", or \"share\" (required)\n- `workspace_id`: Numeric workspace ID; omit for default workspace\n- `folder_id`: Folder ID; must be within `workspace_id` if both provided\n- `template_id`: ID of accessible template to clone\n\n**Pitfalls**:\n- `board_kind` is required and must be one of: \"public\", \"private\", \"share\"\n- If both `workspace_id` and `folder_id` are provided, the folder must exist within that workspace\n- `template_id` must reference a template the authenticated user can access\n- Board IDs are large integers; always use the exact value from API responses\n\n### 2. Create and Manage Items\n\n**When to use**: User wants to add tasks\u002Fitems to a board, list existing items, or move items between groups.\n\n**Tool sequence**:\n1. `MONDAY_LIST_BOARDS` - Resolve board name to board ID [Prerequisite]\n2. `MONDAY_LIST_GROUPS` - List groups on the board to get group_id [Prerequisite]\n3. `MONDAY_LIST_COLUMNS` - Get column IDs and types for setting values [Prerequisite]\n4. `MONDAY_CREATE_ITEM` - Create a new item with name and column values [Required]\n5. `MONDAY_LIST_BOARD_ITEMS` - List all items on the board [Optional]\n6. `MONDAY_MOVE_ITEM_TO_GROUP` - Move an item to a different group [Optional]\n7. `MONDAY_ITEMS_PAGE` - Paginated item retrieval with filtering [Optional]\n\n**Key parameters**:\n- `board_id`: Board ID (required, integer)\n- `item_name`: Item name, max 256 characters (required)\n- `group_id`: Group ID string to place the item in (optional)\n- `column_values`: JSON object or string mapping column IDs to values\n\n**Pitfalls**:\n- `column_values` must use column IDs (not titles); get them from `MONDAY_LIST_COLUMNS`\n- Column value formats vary by type: status uses `{\"index\": 0}` or `{\"label\": \"Done\"}`, date uses `{\"date\": \"YYYY-MM-DD\"}`, people uses `{\"personsAndTeams\": [{\"id\": 123, \"kind\": \"person\"}]}`\n- `item_name` has a 256-character maximum\n- Subitem boards are NOT supported by `MONDAY_CREATE_ITEM`; use GraphQL via `MONDAY_CREATE_OBJECT`\n\n### 3. Update Item Column Values\n\n**When to use**: User wants to change status, date, text, or other column values on existing items.\n\n**Tool sequence**:\n1. `MONDAY_LIST_COLUMNS` or `MONDAY_COLUMNS` - Get column IDs and types [Prerequisite]\n2. `MONDAY_LIST_BOARD_ITEMS` or `MONDAY_ITEMS_PAGE` - Find the target item ID [Prerequisite]\n3. `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` - Update text, status, or dropdown with a string value [Required]\n4. `MONDAY_UPDATE_ITEM` - Update complex column types (timeline, people, date) with JSON [Required]\n\n**Key parameters for MONDAY_CHANGE_SIMPLE_COLUMN_VALUE**:\n- `board_id`: Board ID (integer, required)\n- `item_id`: Item ID (integer, required)\n- `column_id`: Column ID string (required)\n- `value`: Simple string value (e.g., \"Done\", \"Working on it\")\n- `create_labels_if_missing`: true to auto-create status\u002Fdropdown labels (default true)\n\n**Key parameters for MONDAY_UPDATE_ITEM**:\n- `board_id`: Board ID (integer, required)\n- `item_id`: Item ID (integer, required)\n- `column_id`: Column ID string (required)\n- `value`: JSON object matching the column type schema\n- `create_labels_if_missing`: false by default; set true for status\u002Fdropdown\n\n**Pitfalls**:\n- Use `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` for simple text\u002Fstatus\u002Fdropdown updates (string value)\n- Use `MONDAY_UPDATE_ITEM` for complex types like timeline, people, date (JSON value)\n- Column IDs are lowercase strings with underscores (e.g., \"status_1\", \"date_2\", \"text\"); get them from `MONDAY_LIST_COLUMNS`\n- Status values can be set by label name (\"Done\") or index number (\"1\")\n- `create_labels_if_missing` defaults differ: true for CHANGE_SIMPLE, false for UPDATE_ITEM\n\n### 4. Work with Groups and Board Structure\n\n**When to use**: User wants to organize items into groups, add columns, or inspect board structure.\n\n**Tool sequence**:\n1. `MONDAY_LIST_BOARDS` - Resolve board ID [Prerequisite]\n2. `MONDAY_LIST_GROUPS` - List all groups on a board [Required]\n3. `MONDAY_CREATE_GROUP` - Create a new group [Optional]\n4. `MONDAY_LIST_COLUMNS` or `MONDAY_COLUMNS` - Inspect column structure [Required]\n5. `MONDAY_CREATE_COLUMN` - Add a new column to the board [Optional]\n6. `MONDAY_MOVE_ITEM_TO_GROUP` - Reorganize items across groups [Optional]\n\n**Key parameters**:\n- `board_id`: Board ID (required for all group\u002Fcolumn operations)\n- `group_name`: Name for new group (CREATE_GROUP)\n- `column_type`: Must be a valid GraphQL enum token in snake_case (e.g., \"status\", \"text\", \"long_text\", \"numbers\", \"date\", \"dropdown\", \"people\")\n- `title`: Column display title\n- `defaults`: JSON string for status\u002Fdropdown labels, e.g., `'{\"labels\": [\"To Do\", \"In Progress\", \"Done\"]}'`\n\n**Pitfalls**:\n- `column_type` must be exact snake_case values; \"person\" is NOT valid, use \"people\"\n- Group IDs are strings (e.g., \"topics\", \"new_group_12345\"), not integers\n- `MONDAY_COLUMNS` accepts an array of `board_ids` and returns column metadata including settings\n- `MONDAY_LIST_COLUMNS` is simpler and takes a single `board_id`\n\n### 5. Manage Subitems and Updates\n\n**When to use**: User wants to view subitems of a task or add comments\u002Fupdates to items.\n\n**Tool sequence**:\n1. `MONDAY_LIST_BOARD_ITEMS` - Find parent item IDs [Prerequisite]\n2. `MONDAY_LIST_SUBITEMS_BY_PARENT` - Retrieve subitems with column values [Required]\n3. `MONDAY_CREATE_UPDATE` - Add a comment\u002Fupdate to an item [Optional]\n4. `MONDAY_CREATE_OBJECT` - Create subitems via GraphQL mutation [Optional]\n\n**Key parameters for MONDAY_LIST_SUBITEMS_BY_PARENT**:\n- `parent_item_ids`: Array of parent item IDs (integer array, required)\n- `include_column_values`: true to include column data (default true)\n- `include_parent_fields`: true to include parent item info (default true)\n\n**Key parameters for MONDAY_CREATE_OBJECT** (GraphQL):\n- `query`: Full GraphQL mutation string\n- `variables`: Optional variables object\n\n**Pitfalls**:\n- Subitems can only be queried through their parent items\n- To create subitems, use `MONDAY_CREATE_OBJECT` with a `create_subitem` GraphQL mutation\n- `MONDAY_CREATE_UPDATE` is for adding comments\u002Fupdates to items (Monday's \"updates\" feature), not for modifying item values\n- `MONDAY_CREATE_OBJECT` is a raw GraphQL endpoint; ensure correct mutation syntax\n\n## Common Patterns\n\n### ID Resolution\nAlways resolve display names to IDs before operations:\n- **Board name -> board_id**: `MONDAY_LIST_BOARDS` and match by name\n- **Group name -> group_id**: `MONDAY_LIST_GROUPS` with `board_id`\n- **Column title -> column_id**: `MONDAY_LIST_COLUMNS` with `board_id`\n- **Workspace name -> workspace_id**: `MONDAY_GET_WORKSPACES` and match by name\n- **Item name -> item_id**: `MONDAY_LIST_BOARD_ITEMS` or `MONDAY_ITEMS_PAGE`\n\n### Pagination\nMonday.com uses cursor-based pagination for items:\n- `MONDAY_ITEMS_PAGE` returns a `cursor` in the response for the next page\n- Pass the `cursor` to the next call; `board_id` and `query_params` are ignored when cursor is provided\n- Cursors are cached for 60 minutes\n- Maximum `limit` is 500 per page\n- `MONDAY_LIST_BOARDS` and `MONDAY_GET_WORKSPACES` use page-based pagination with `page` and `limit`\n\n### Column Value Formatting\nDifferent column types require different value formats:\n- **Status**: `{\"index\": 0}` or `{\"label\": \"Done\"}` or simple string \"Done\"\n- **Date**: `{\"date\": \"YYYY-MM-DD\"}`\n- **People**: `{\"personsAndTeams\": [{\"id\": 123, \"kind\": \"person\"}]}`\n- **Text\u002FNumbers**: Plain string or number\n- **Timeline**: `{\"from\": \"YYYY-MM-DD\", \"to\": \"YYYY-MM-DD\"}`\n\n## Known Pitfalls\n\n### ID Formats\n- Board IDs and item IDs are large integers (e.g., 1234567890)\n- Group IDs are strings (e.g., \"topics\", \"new_group_12345\")\n- Column IDs are short strings (e.g., \"status_1\", \"date4\", \"text\")\n- Workspace IDs are integers\n\n### Rate Limits\n- Monday.com GraphQL API has complexity-based rate limits\n- Large boards with many columns increase query complexity\n- Use `limit` parameter to reduce items per request if hitting limits\n\n### Parameter Quirks\n- `column_type` for CREATE_COLUMN must be exact snake_case enum values; \"people\" not \"person\"\n- `column_values` in CREATE_ITEM accepts both JSON string and object formats\n- `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` auto-creates missing labels by default; `MONDAY_UPDATE_ITEM` does not\n- `MONDAY_CREATE_OBJECT` is a raw GraphQL interface; use it for operations without dedicated tools (e.g., create_subitem, delete_item, archive_board)\n\n### Response Structure\n- Board items are returned as arrays with `id`, `name`, and `state` fields\n- Column values include both raw `value` (JSON) and rendered `text` (display string)\n- Subitems are nested under parent items and cannot be queried independently\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List workspaces | `MONDAY_GET_WORKSPACES` | `kind`, `state`, `limit` |\n| Create workspace | `MONDAY_CREATE_WORKSPACE` | `name`, `kind` |\n| List boards | `MONDAY_LIST_BOARDS` | `limit`, `page`, `state` |\n| Create board | `MONDAY_CREATE_BOARD` | `board_name`, `board_kind`, `workspace_id` |\n| Get board metadata | `MONDAY_BOARDS` | `board_ids`, `board_kind` |\n| List groups | `MONDAY_LIST_GROUPS` | `board_id` |\n| Create group | `MONDAY_CREATE_GROUP` | `board_id`, `group_name` |\n| List columns | `MONDAY_LIST_COLUMNS` | `board_id` |\n| Get column metadata | `MONDAY_COLUMNS` | `board_ids`, `column_types` |\n| Create column | `MONDAY_CREATE_COLUMN` | `board_id`, `column_type`, `title` |\n| Create item | `MONDAY_CREATE_ITEM` | `board_id`, `item_name`, `column_values` |\n| List board items | `MONDAY_LIST_BOARD_ITEMS` | `board_id` |\n| Paginated items | `MONDAY_ITEMS_PAGE` | `board_id`, `limit`, `query_params` |\n| Update column (simple) | `MONDAY_CHANGE_SIMPLE_COLUMN_VALUE` | `board_id`, `item_id`, `column_id`, `value` |\n| Update column (complex) | `MONDAY_UPDATE_ITEM` | `board_id`, `item_id`, `column_id`, `value` |\n| Move item to group | `MONDAY_MOVE_ITEM_TO_GROUP` | `item_id`, `group_id` |\n| List subitems | `MONDAY_LIST_SUBITEMS_BY_PARENT` | `parent_item_ids` |\n| Add comment\u002Fupdate | `MONDAY_CREATE_UPDATE` | `item_id`, `body` |\n| Raw GraphQL mutation | `MONDAY_CREATE_OBJECT` | `query`, `variables` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fmonday-automation",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill monday-automation",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill monday-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill monday-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fskills\u002Fmonday-automation\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]