{"id":"ed6ddf22-918d-44ed-8f3e-ca7b1cfeceb4","entityType":"agent","slug":"clawhub-oomol-oo-monday","name":"monday","canonicalUrl":"https://www.xpersona.co/agent/clawhub-oomol-oo-monday","canonicalPath":"/agent/clawhub-oomol-oo-monday","generatedAt":"2026-10-11T03:55:08.117Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T00:50:28.559Z","emptyReason":null},"description":"monday (monday.com). Use this skill for ANY monday request — reading, creating, updating, and deleting data. Whenever a task involves monday, use this skill instead of calling the API directly.","descriptionLabel":"Source description","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-monday","sourceUrl":"https://clawhub.ai/oomol/oo-monday","homepage":"https://clawhub.ai/oomol/skills/oo-monday","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/oomol/oo-monday","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/oomol/skills/oo-monday","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":62,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"monday technical dossier on Xpersona with agent coverage, OPENCLEW support, and live trust metadata."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T00:50:28.559Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T00:50:28.559Z","emptyReason":null},"stars":null,"forks":null,"downloads":1214,"packageName":null,"latestVersion":"1.0.7","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T00:50:28.492Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T00:50:28.559Z","lastCrawledAt":"2026-10-11T00:50:28.492Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T00:50:28.492Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.7","createdAt":"2026-09-20T03:22:43.783Z","changelog":"- Provides OOMOL-connected monday.com automation through the `oo` CLI without handling raw API tokens. - Supports board, workspace, dashboard, doc, form, group, item, subitem, update, user, team, and department operations. - Includes read actions for listing, filtering, fetching, pagination, activity logs, audit logs, assets, memberships, and updates. - Includes write actions for creating, updating, moving, duplicating, and assigning monday resources. - Marks destructive operations clearly and requires explicit confirmation before delete, archive, overwrite, or removal actions. Source: `oomol-lab/skills@792ad44`","fileCount":3,"zipByteSize":4443},{"version":"1.0.6","createdAt":"2026-09-15T05:34:38.843Z","changelog":"- Provides an OOMOL-backed monday.com skill for reading, creating, updating, and deleting monday data through the `oo` CLI. - Covers boards, items, subitems, groups, columns, workspaces, dashboards, docs, forms, updates, users, teams, departments, assets, audit logs, and activity logs. - Requires checking each action’s live schema with `oo connector schema` before building request payloads. - Marks state-changing actions as `[write]` and irreversible/removal actions as `[destructive]` with explicit confirmation guidance. - Includes first-time setup and recovery steps for missing CLI, auth failures, expired credentials, missing scopes, and billing errors. Source: `oomol-lab/skills@75bac03`","fileCount":3,"zipByteSize":4463},{"version":"1.0.4","createdAt":"2026-08-25T04:51:14.034Z","changelog":"- monday connector skill for operating monday.com through the OOMOL-connected account via the `oo` CLI. - Supports core board, item, workspace, dashboard, doc, form, group, column, update, team, user, and department workflows. - Covers both read and write operations, including create, update, move, duplicate, archive, and list actions. - Includes destructive actions with explicit safety guidance so state-changing requests are handled carefully. - Uses live connector schemas before running actions, keeping payloads aligned with the authoritative monday contract. Source: `oomol-lab/skills@3e4b3ff`","fileCount":3,"zipByteSize":4532},{"version":"1.0.3","createdAt":"2026-08-11T08:05:24.057Z","changelog":"- Operates monday.com through the OOMOL `monday` connector using the `oo` CLI, with credentials handled server-side. - Documents the required workflow for inspecting live action schemas before running connector actions. - Covers board, item, subitem, group, column, workspace, dashboard, doc, form, team, user, department, update, asset, audit log, and activity log operations. - Marks state-changing actions as `[write]` and removal/overwrite actions as `[destructive]` with explicit confirmation guidance. - Includes first-time setup and troubleshooting paths for CLI installation, auth, connection scope, expired credentials, and billing errors. Source: `oomol-lab/skills@46cfb3e`","fileCount":3,"zipByteSize":4511},{"version":"1.0.2","createdAt":"2026-07-12T16:04:03.897Z","changelog":"- Provides an OOMOL-backed monday.com skill for reading, creating, updating, and deleting monday data through the `oo` CLI. - Uses server-side OOMOL credentials, so raw monday tokens are never handled directly. - Supports board, item, subitem, group, column, update, workspace, user, team, dashboard, doc, form, department, asset, audit log, and activity log workflows. - Requires fetching each action’s live schema before running it, keeping payloads aligned with the current connector contract. - Marks write and destructive actions clearly, with explicit confirmation required before changing or removing monday data. Source: `oomol-lab/skills@d4aeb09`","fileCount":3,"zipByteSize":4380},{"version":"1.0.1","createdAt":"2026-06-09T10:12:41.600Z","changelog":"- Operates monday.com through an OOMOL-connected account using the `oo` CLI, without handling raw credentials. - Supports board, item, subitem, group, column, dashboard, doc, form, workspace, user, team, and department workflows. - Provides read actions for listing, searching, and retrieving Monday data, including pagination and filters. - Provides write actions for creating, updating, moving, archiving, and duplicating Monday resources. - Marks destructive actions clearly and requires explicit confirmation before deleting or overwriting Monday data. Source: `oomol-lab/skills@146ef20`","fileCount":3,"zipByteSize":4475},{"version":"1.0.0","createdAt":"2026-06-05T01:51:00.356Z","changelog":"- Initial release of the `oo-monday` skill for operating monday.com through an OOMOL-connected account using the `oo` CLI. - Provides 64 actions for reading and managing Monday boards, items, subitems, groups, columns, workspaces, users, teams, departments, dashboards, docs, forms, updates, assets, activity logs, and audit logs. - Supports core board workflows including creating, updating, archiving, deleting, duplicating, moving, positioning, and searching items. - Includes write operations for column values, board metadata, groups, docs, dashboards, Workforms, updates, and enterprise departments. - Documents a schema-first execution flow so agents inspect the live connector contract before constructing action payloads. - Adds explicit safety guidance for read, write, and destructive actions, including confirmation requirements before changing or deleting Monday data.","fileCount":67,"zipByteSize":40529}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-monday","setupComplexity":"low","setupSteps":["Install using `clawhub skill install s1790xw8jww1c6hgm8aqy9q25187t1rg:oo-monday` in an isolated environment before connecting it to live workloads.","No published capability contract is available yet, so validate auth and request/response behavior manually.","Review the upstream CLAWHUB listing at https://clawhub.ai/oomol/oo-monday before using production credentials."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T03:55:08.115Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-oomol-oo-monday/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T00:50:28.559Z","emptyReason":null},"readme":"Skill: monday\n\nOwner: oomol\n\nSummary: monday (monday.com). Use this skill for ANY monday request — reading, creating, updating, and deleting data. Whenever a task involves monday, use this skill instead of calling the API directly.\n\nTags: latest:1.0.7\n\nVersion history:\n\nv1.0.7 | 2026-09-20T03:22:43.783Z | user\n\n- Provides OOMOL-connected monday.com automation through the `oo` CLI without handling raw API tokens.\n- Supports board, workspace, dashboard, doc, form, group, item, subitem, update, user, team, and department operations.\n- Includes read actions for listing, filtering, fetching, pagination, activity logs, audit logs, assets, memberships, and updates.\n- Includes write actions for creating, updating, moving, duplicating, and assigning monday resources.\n- Marks destructive operations clearly and requires explicit confirmation before delete, archive, overwrite, or removal actions.\n\nSource: `oomol-lab/skills@792ad44`\n\nv1.0.6 | 2026-09-15T05:34:38.843Z | user\n\n- Provides an OOMOL-backed monday.com skill for reading, creating, updating, and deleting monday data through the `oo` CLI.\n- Covers boards, items, subitems, groups, columns, workspaces, dashboards, docs, forms, updates, users, teams, departments, assets, audit logs, and activity logs.\n- Requires checking each action’s live schema with `oo connector schema` before building request payloads.\n- Marks state-changing actions as `[write]` and irreversible/removal actions as `[destructive]` with explicit confirmation guidance.\n- Includes first-time setup and recovery steps for missing CLI, auth failures, expired credentials, missing scopes, and billing errors.\n\nSource: `oomol-lab/skills@75bac03`\n\nv1.0.4 | 2026-08-25T04:51:14.034Z | user\n\n- monday connector skill for operating monday.com through the OOMOL-connected account via the `oo` CLI.\n- Supports core board, item, workspace, dashboard, doc, form, group, column, update, team, user, and department workflows.\n- Covers both read and write operations, including create, update, move, duplicate, archive, and list actions.\n- Includes destructive actions with explicit safety guidance so state-changing requests are handled carefully.\n- Uses live connector schemas before running actions, keeping payloads aligned with the authoritative monday contract.\n\nSource: `oomol-lab/skills@3e4b3ff`\n\nv1.0.3 | 2026-08-11T08:05:24.057Z | user\n\n- Operates monday.com through the OOMOL `monday` connector using the `oo` CLI, with credentials handled server-side.\n- Documents the required workflow for inspecting live action schemas before running connector actions.\n- Covers board, item, subitem, group, column, workspace, dashboard, doc, form, team, user, department, update, asset, audit log, and activity log operations.\n- Marks state-changing actions as `[write]` and removal/overwrite actions as `[destructive]` with explicit confirmation guidance.\n- Includes first-time setup and troubleshooting paths for CLI installation, auth, connection scope, expired credentials, and billing errors.\n\nSource: `oomol-lab/skills@46cfb3e`\n\nv1.0.2 | 2026-07-12T16:04:03.897Z | user\n\n- Provides an OOMOL-backed monday.com skill for reading, creating, updating, and deleting monday data through the `oo` CLI.\n- Uses server-side OOMOL credentials, so raw monday tokens are never handled directly.\n- Supports board, item, subitem, group, column, update, workspace, user, team, dashboard, doc, form, department, asset, audit log, and activity log workflows.\n- Requires fetching each action’s live schema before running it, keeping payloads aligned with the current connector contract.\n- Marks write and destructive actions clearly, with explicit confirmation required before changing or removing monday data.\n\nSource: `oomol-lab/skills@d4aeb09`\n\nv1.0.1 | 2026-06-09T10:12:41.600Z | user\n\n- Operates monday.com through an OOMOL-connected account using the `oo` CLI, without handling raw credentials.\n- Supports board, item, subitem, group, column, dashboard, doc, form, workspace, user, team, and department workflows.\n- Provides read actions for listing, searching, and retrieving Monday data, including pagination and filters.\n- Provides write actions for creating, updating, moving, archiving, and duplicating Monday resources.\n- Marks destructive actions clearly and requires explicit confirmation before deleting or overwriting Monday data.\n\nSource: `oomol-lab/skills@146ef20`\n\nv1.0.0 | 2026-06-05T01:51:00.356Z | user\n\n- Initial release of the `oo-monday` skill for operating monday.com through an OOMOL-connected account using the `oo` CLI.\n- Provides 64 actions for reading and managing Monday boards, items, subitems, groups, columns, workspaces, users, teams, departments, dashboards, docs, forms, updates, assets, activity logs, and audit logs.\n- Supports core board workflows including creating, updating, archiving, deleting, duplicating, moving, positioning, and searching items.\n- Includes write operations for column values, board metadata, groups, docs, dashboards, Workforms, updates, and enterprise departments.\n- Documents a schema-first execution flow so agents inspect the live connector contract before constructing action payloads.\n- Adds explicit safety guidance for read, write, and destructive actions, including confirmation requirements before changing or deleting Monday data.\n\nArchive index:\n\nArchive v1.0.7: 3 files, 4443 bytes\n\nFiles: skill-card.md (2002b), SKILL.md (8907b), _meta.json (128b)\n\nFile v1.0.7:SKILL.md\n\n---\nname: oo-monday\ndescription: \"monday (monday.com). Use this skill for ANY monday request — reading, creating, updating, and deleting data. Whenever a task involves monday, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"monday\"\n author: \"OOMOL\"\n version: \"1.0.7\"\n services: [\"monday\"]\n icon: \"https://static.oomol.com/logo/third-party/Monday.svg\"\n---\n\n# monday\n\nOperate **monday** through your OOMOL-connected account. This skill calls the `monday` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected monday. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"monday\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"monday\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `activate_form` — Activate a monday Workform so it starts accepting submissions. [write]\n- `add_teams_to_board` — Add monday teams to a board as subscribers or owners. [write]\n- `add_users_to_board` — Add monday users to a board as subscribers or owners. [write]\n- `archive_board` — Archive a monday board. [destructive]\n- `archive_item` — Archive a monday item. [destructive]\n- `assign_department_members` — Assign users to a monday department on an enterprise account. [write]\n- `change_item_position` — Change a monday item's position on the same board. [write]\n- `change_multiple_column_values` — Change multiple monday column values in one mutation using the official JSON payload shape. [write]\n- `change_simple_column_value` — Change a monday column value using the official simple string mutation. [write]\n- `clear_users_department` — Clear department assignments from monday users on an enterprise account. [destructive]\n- `create_board` — Create a monday board with the official create_board mutation. [write]\n- `create_column` — Create a monday column on an existing board. [write]\n- `create_dashboard` — Create a monday dashboard with the official dashboard mutation. [write]\n- `create_department` — Create a monday department on an enterprise account. [write]\n- `create_doc` — Create a monday doc in a workspace or document column location. [write]\n- `create_form` — Create a monday Workform and its destination responses board. [write]\n- `create_group` — Create a monday group on an existing board. [write]\n- `create_item` — Create a monday item on a board, optionally setting column values and position. [write]\n- `create_subitem` — Create a monday subitem under an existing parent item. [write]\n- `create_update` — Create a monday update on an item or as a reply to an existing update. [write]\n- `create_workspace` — Create a monday workspace with the official create_workspace mutation. [write]\n- `deactivate_form` — Deactivate a monday Workform so it stops accepting submissions. [destructive]\n- `delete_board` — Delete a monday board. [destructive]\n- `delete_column` — Delete a monday column from an existing board. [destructive]\n- `delete_dashboard` — Delete a monday dashboard. [destructive]\n- `delete_department` — Delete a monday department on an enterprise account. [destructive]\n- `delete_doc` — Delete an existing monday doc. [destructive]\n- `delete_group` — Delete a monday group from an existing board. [destructive]\n- `delete_item` — Delete a monday item. [destructive]\n- `delete_subscribers_from_board` — Remove monday user subscribers from a board. [destructive]\n- `delete_teams_from_board` — Remove monday team subscribers from a board. [destructive]\n- `delete_update` — Delete an existing monday update. [destructive]\n- `delete_workspace` — Delete a monday workspace with the official delete_workspace mutation. [destructive]\n- `duplicate_item` — Duplicate a monday item. [write]\n- `edit_update` — Edit an existing monday update. [write]\n- `find_items_by_column_values` — Find monday items on a board by matching explicit column values.\n- `get_board_memberships` — Retrieve the user and team memberships configured on a monday board.\n- `get_current_user` — Retrieve the monday user associated with the current personal API token.\n- `get_form` — Retrieve a monday Workform by its unique form token.\n- `get_items` — Retrieve specific monday items by ID.\n- `get_items_page` — Retrieve a filtered page of monday board items using the official items_page query.\n- `get_next_items_page` — Retrieve the next page of monday items from an items_page cursor.\n- `list_activity_logs` — List board-scoped monday activity logs.\n- `list_assets` — Retrieve one or more monday assets by asset ID.\n- `list_audit_logs` — List account-level monday audit logs on enterprise accounts.\n- `list_board_columns` — List the columns for a specific monday board.\n- `list_boards` — List monday boards with official pagination and board-level filters.\n- `list_departments` — List monday departments on enterprise accounts.\n- `list_docs` — List monday docs by document, object, or workspace identifiers.\n- `list_groups` — List the groups for a specific monday board.\n- `list_subitems_by_parent` — List monday subitems for one or more parent items.\n- `list_team_members` — List the members of a specific monday team.\n- `list_teams` — List monday teams, optionally filtering by team IDs.\n- `list_update_replies` — List monday replies for updates on one or more boards.\n- `list_updates` — List monday updates with optional date filtering.\n- `list_users` — List monday users with official root-level filters and pagination.\n- `list_workspaces` — List monday workspaces with official filters and pagination.\n- `move_item_to_board` — Move a monday item to another board and target group. [destructive]\n- `move_item_to_group` — Move a monday item to another group on the same board. [write]\n- `set_item_description_content` — Replace a monday item description using markdown content. [destructive]\n- `update_board` — Update a monday board attribute with the official update_board mutation. [destructive]\n- `update_column` — Update a monday column with the official update_column mutation. [write]\n- `update_dashboard` — Update a monday dashboard with the official dashboard mutation. [write]\n- `update_department` — Update a monday department on an enterprise account. [write]\n- `update_doc_name` — Update the name of an existing monday doc. [write]\n- `update_group` — Update an existing monday group attribute. [write]\n- `update_workspace` — Update a monday workspace with the official update_workspace mutation. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change monday state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — monday is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=monday\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- monday homepage: https://monday.com\n\nFile v1.0.7:_meta.json\n\n{\n \"ownerId\": \"kn7d7j8jdksrd4pyjnnxgch2y987zpvb\",\n \"slug\": \"oo-monday\",\n \"version\": \"1.0.7\",\n \"publishedAt\": 1789874563783\n}\n\nFile v1.0.7:skill-card.md\n\n## Description:\n\nOperates monday.com through OOMOL's oo CLI connector for reading, creating, updating, and deleting monday data.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nAgents and users with an OOMOL-connected monday account use this skill to inspect action schemas and run monday connector actions for boards, items, workspaces, docs, forms, dashboards, users, teams, and departments. It supports read workflows and user-confirmed write or destructive operations.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: First-time setup can run remote installer scripts for the oo CLI.\n\nMitigation: Review the installer path before installing and prefer a verified or package-manager installation of the oo CLI.\n\nRisk: A connected monday account can be used for write or destructive actions.\n\nMitigation: Allow write or destructive monday actions only after checking the exact board, item, workspace, and payload the agent will send.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-monday)\n- [OOMOL publisher profile](https://clawhub.ai/user/oomol)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [monday.com](https://monday.com)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON payload examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Commands use the oo CLI and return connector responses containing data and meta.executionId.]\n\n## Skill Version(s):\n\n1.0.7 (source: server evidence and frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.6: 3 files, 4463 bytes\n\nFiles: skill-card.md (2022b), SKILL.md (8885b), _meta.json (128b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: oo-monday\ndescription: \"monday (monday.com). Use this skill for ANY monday request — reading, creating, updating, and deleting data. Whenever a task involves monday, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"monday\"\n author: \"OOMOL\"\n version: \"1.0.6\"\n services: [\"monday\"]\n icon: \"https://static.oomol.com/logo/third-party/Monday.svg\"\n---\n\n# monday\n\nOperate **monday** through your OOMOL-connected account. This skill calls the `monday` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected monday. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"monday\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"monday\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `activate_form` — Activate a monday Workform so it starts accepting submissions. [write]\n- `add_teams_to_board` — Add monday teams to a board as subscribers or owners. [write]\n- `add_users_to_board` — Add monday users to a board as subscribers or owners. [write]\n- `archive_board` — Archive a monday board. [write]\n- `archive_item` — Archive a monday item. [write]\n- `assign_department_members` — Assign users to a monday department on an enterprise account. [write]\n- `change_item_position` — Change a monday item's position on the same board. [write]\n- `change_multiple_column_values` — Change multiple monday column values in one mutation using the official JSON payload shape. [write]\n- `change_simple_column_value` — Change a monday column value using the official simple string mutation. [write]\n- `clear_users_department` — Clear department assignments from monday users on an enterprise account. [destructive]\n- `create_board` — Create a monday board with the official create_board mutation. [write]\n- `create_column` — Create a monday column on an existing board. [write]\n- `create_dashboard` — Create a monday dashboard with the official dashboard mutation. [write]\n- `create_department` — Create a monday department on an enterprise account. [write]\n- `create_doc` — Create a monday doc in a workspace or document column location. [write]\n- `create_form` — Create a monday Workform and its destination responses board. [write]\n- `create_group` — Create a monday group on an existing board. [write]\n- `create_item` — Create a monday item on a board, optionally setting column values and position. [write]\n- `create_subitem` — Create a monday subitem under an existing parent item. [write]\n- `create_update` — Create a monday update on an item or as a reply to an existing update. [write]\n- `create_workspace` — Create a monday workspace with the official create_workspace mutation. [write]\n- `deactivate_form` — Deactivate a monday Workform so it stops accepting submissions. [destructive]\n- `delete_board` — Delete a monday board. [destructive]\n- `delete_column` — Delete a monday column from an existing board. [destructive]\n- `delete_dashboard` — Delete a monday dashboard. [destructive]\n- `delete_department` — Delete a monday department on an enterprise account. [destructive]\n- `delete_doc` — Delete an existing monday doc. [destructive]\n- `delete_group` — Delete a monday group from an existing board. [destructive]\n- `delete_item` — Delete a monday item. [destructive]\n- `delete_subscribers_from_board` — Remove monday user subscribers from a board. [destructive]\n- `delete_teams_from_board` — Remove monday team subscribers from a board. [destructive]\n- `delete_update` — Delete an existing monday update. [destructive]\n- `delete_workspace` — Delete a monday workspace with the official delete_workspace mutation. [destructive]\n- `duplicate_item` — Duplicate a monday item. [write]\n- `edit_update` — Edit an existing monday update. [write]\n- `find_items_by_column_values` — Find monday items on a board by matching explicit column values.\n- `get_board_memberships` — Retrieve the user and team memberships configured on a monday board.\n- `get_current_user` — Retrieve the monday user associated with the current personal API token.\n- `get_form` — Retrieve a monday Workform by its unique form token.\n- `get_items` — Retrieve specific monday items by ID.\n- `get_items_page` — Retrieve a filtered page of monday board items using the official items_page query.\n- `get_next_items_page` — Retrieve the next page of monday items from an items_page cursor.\n- `list_activity_logs` — List board-scoped monday activity logs.\n- `list_assets` — Retrieve one or more monday assets by asset ID.\n- `list_audit_logs` — List account-level monday audit logs on enterprise accounts.\n- `list_board_columns` — List the columns for a specific monday board.\n- `list_boards` — List monday boards with official pagination and board-level filters.\n- `list_departments` — List monday departments on enterprise accounts.\n- `list_docs` — List monday docs by document, object, or workspace identifiers.\n- `list_groups` — List the groups for a specific monday board.\n- `list_subitems_by_parent` — List monday subitems for one or more parent items.\n- `list_team_members` — List the members of a specific monday team.\n- `list_teams` — List monday teams, optionally filtering by team IDs.\n- `list_update_replies` — List monday replies for updates on one or more boards. [write]\n- `list_updates` — List monday updates with optional date filtering.\n- `list_users` — List monday users with official root-level filters and pagination.\n- `list_workspaces` — List monday workspaces with official filters and pagination.\n- `move_item_to_board` — Move a monday item to another board and target group. [write]\n- `move_item_to_group` — Move a monday item to another group on the same board. [write]\n- `set_item_description_content` — Replace a monday item description using markdown content. [write]\n- `update_board` — Update a monday board attribute with the official update_board mutation. [write]\n- `update_column` — Update a monday column with the official update_column mutation. [write]\n- `update_dashboard` — Update a monday dashboard with the official dashboard mutation. [write]\n- `update_department` — Update a monday department on an enterprise account. [write]\n- `update_doc_name` — Update the name of an existing monday doc. [write]\n- `update_group` — Update an existing monday group attribute. [write]\n- `update_workspace` — Update a monday workspace with the official update_workspace mutation. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change monday state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — monday is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=monday\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- monday homepage: https://monday.com\n\nFile v1.0.6:_meta.json\n\n{\n \"ownerId\": \"kn7d7j8jdksrd4pyjnnxgch2y987zpvb\",\n \"slug\": \"oo-monday\",\n \"version\": \"1.0.6\",\n \"publishedAt\": 1789450478843\n}\n\nFile v1.0.6:skill-card.md\n\n## Description:\n\nEnables an agent to read, create, update, and delete monday.com data through the OOMOL oo CLI connector.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nExternal users and developers use this skill to operate monday.com work management resources from an agent after their OOMOL account and monday connection are configured. It supports board, item, workspace, dashboard, document, form, user, team, department, asset, audit log, and activity log workflows.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Fallback setup includes remote installer scripts that may be run directly in a shell.\n\nMitigation: Review the installer path before installation and prefer manual or otherwise verified oo CLI installation.\n\nRisk: Write and destructive monday actions can change, remove, or overwrite workspace data.\n\nMitigation: Confirm the exact payload, action, and board, item, workspace, or user targets before executing any tagged write or destructive action.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-monday)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md)\n- [monday.com](https://monday.com)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Commands generally return JSON containing data and meta.executionId.]\n\n## Skill Version(s):\n\n1.0.6 (source: server release metadata and skill metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.4: 3 files, 4532 bytes\n\nFiles: skill-card.md (2197b), SKILL.md (8885b), _meta.json (128b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: oo-monday\ndescription: \"monday (monday.com). Use this skill for ANY monday request — reading, creating, updating, and deleting data. Whenever a task involves monday, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"monday\"\n author: \"OOMOL\"\n version: \"1.0.4\"\n services: [\"monday\"]\n icon: \"https://static.oomol.com/logo/third-party/Monday.svg\"\n---\n\n# monday\n\nOperate **monday** through your OOMOL-connected account. This skill calls the `monday` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected monday. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"monday\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"monday\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `activate_form` — Activate a monday Workform so it starts accepting submissions. [write]\n- `add_teams_to_board` — Add monday teams to a board as subscribers or owners. [write]\n- `add_users_to_board` — Add monday users to a board as subscribers or owners. [write]\n- `archive_board` — Archive a monday board. [write]\n- `archive_item` — Archive a monday item. [write]\n- `assign_department_members` — Assign users to a monday department on an enterprise account. [write]\n- `change_item_position` — Change a monday item's position on the same board. [write]\n- `change_multiple_column_values` — Change multiple monday column values in one mutation using the official JSON payload shape. [write]\n- `change_simple_column_value` — Change a monday column value using the official simple string mutation. [write]\n- `clear_users_department` — Clear department assignments from monday users on an enterprise account. [destructive]\n- `create_board` — Create a monday board with the official create_board mutation. [write]\n- `create_column` — Create a monday column on an existing board. [write]\n- `create_dashboard` — Create a monday dashboard with the official dashboard mutation. [write]\n- `create_department` — Create a monday department on an enterprise account. [write]\n- `create_doc` — Create a monday doc in a workspace or document column location. [write]\n- `create_form` — Create a monday Workform and its destination responses board. [write]\n- `create_group` — Create a monday group on an existing board. [write]\n- `create_item` — Create a monday item on a board, optionally setting column values and position. [write]\n- `create_subitem` — Create a monday subitem under an existing parent item. [write]\n- `create_update` — Create a monday update on an item or as a reply to an existing update. [write]\n- `create_workspace` — Create a monday workspace with the official create_workspace mutation. [write]\n- `deactivate_form` — Deactivate a monday Workform so it stops accepting submissions. [destructive]\n- `delete_board` — Delete a monday board. [destructive]\n- `delete_column` — Delete a monday column from an existing board. [destructive]\n- `delete_dashboard` — Delete a monday dashboard. [destructive]\n- `delete_department` — Delete a monday department on an enterprise account. [destructive]\n- `delete_doc` — Delete an existing monday doc. [destructive]\n- `delete_group` — Delete a monday group from an existing board. [destructive]\n- `delete_item` — Delete a monday item. [destructive]\n- `delete_subscribers_from_board` — Remove monday user subscribers from a board. [destructive]\n- `delete_teams_from_board` — Remove monday team subscribers from a board. [destructive]\n- `delete_update` — Delete an existing monday update. [destructive]\n- `delete_workspace` — Delete a monday workspace with the official delete_workspace mutation. [destructive]\n- `duplicate_item` — Duplicate a monday item. [write]\n- `edit_update` — Edit an existing monday update. [write]\n- `find_items_by_column_values` — Find monday items on a board by matching explicit column values.\n- `get_board_memberships` — Retrieve the user and team memberships configured on a monday board.\n- `get_current_user` — Retrieve the monday user associated with the current personal API token.\n- `get_form` — Retrieve a monday Workform by its unique form token.\n- `get_items` — Retrieve specific monday items by ID.\n- `get_items_page` — Retrieve a filtered page of monday board items using the official items_page query.\n- `get_next_items_page` — Retrieve the next page of monday items from an items_page cursor.\n- `list_activity_logs` — List board-scoped monday activity logs.\n- `list_assets` — Retrieve one or more monday assets by asset ID.\n- `list_audit_logs` — List account-level monday audit logs on enterprise accounts.\n- `list_board_columns` — List the columns for a specific monday board.\n- `list_boards` — List monday boards with official pagination and board-level filters.\n- `list_departments` — List monday departments on enterprise accounts.\n- `list_docs` — List monday docs by document, object, or workspace identifiers.\n- `list_groups` — List the groups for a specific monday board.\n- `list_subitems_by_parent` — List monday subitems for one or more parent items.\n- `list_team_members` — List the members of a specific monday team.\n- `list_teams` — List monday teams, optionally filtering by team IDs.\n- `list_update_replies` — List monday replies for updates on one or more boards. [write]\n- `list_updates` — List monday updates with optional date filtering.\n- `list_users` — List monday users with official root-level filters and pagination.\n- `list_workspaces` — List monday workspaces with official filters and pagination.\n- `move_item_to_board` — Move a monday item to another board and target group. [write]\n- `move_item_to_group` — Move a monday item to another group on the same board. [write]\n- `set_item_description_content` — Replace a monday item description using markdown content. [write]\n- `update_board` — Update a monday board attribute with the official update_board mutation. [write]\n- `update_column` — Update a monday column with the official update_column mutation. [write]\n- `update_dashboard` — Update a monday dashboard with the official dashboard mutation. [write]\n- `update_department` — Update a monday department on an enterprise account. [write]\n- `update_doc_name` — Update the name of an existing monday doc. [write]\n- `update_group` — Update an existing monday group attribute. [write]\n- `update_workspace` — Update a monday workspace with the official update_workspace mutation. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change monday state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — monday is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=monday\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- monday homepage: https://monday.com\n\nFile v1.0.4:_meta.json\n\n{\n \"ownerId\": \"kn7d7j8jdksrd4pyjnnxgch2y987zpvb\",\n \"slug\": \"oo-monday\",\n \"version\": \"1.0.4\",\n \"publishedAt\": 1787633474034\n}\n\nFile v1.0.4:skill-card.md\n\n## Description:\n\nmonday (monday.com). Use this skill for ANY monday request - reading, creating, updating, and deleting data.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, operators, and developers use this skill to let an agent work with monday.com boards, items, workspaces, dashboards, docs, forms, teams, users, updates, and departments through an OOMOL-connected account. It supports read workflows and state-changing workflows, with explicit confirmation expected before write or destructive actions.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can operate a user's monday.com account and includes actions that write, archive, delete, deactivate, or change memberships and account structures.\n\nMitigation: Review proposed payloads carefully and approve only actions whose target and effect are clear, especially for delete, archive, deactivate, membership, workspace, board, item, and department changes.\n\nRisk: Incorrect payloads or misunderstood targets could modify the wrong monday.com data.\n\nMitigation: Fetch the live connector schema before constructing a payload and confirm the exact payload and expected effect before running write or destructive actions.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-monday)\n- [monday homepage](https://monday.com)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n\n## Skill Output:\n\n**Output Type(s):** [shell commands, configuration, guidance, JSON]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON payloads]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Responses may include connector execution results as JSON with data and metadata.]\n\n## Skill Version(s):\n\n1.0.4 (source: server release metadata and skill frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.3: 3 files, 4511 bytes\n\nFiles: skill-card.md (2225b), SKILL.md (8888b), _meta.json (128b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: oo-monday\ndescription: \"monday (monday.com). Use this skill for ANY monday request — reading, creating, updating, and deleting data. Whenever a task involves monday, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"monday\"\n author: \"OOMOL\"\n version: \"1.0.3\"\n services: [\"monday\"]\n icon: \"https://static.oomol.com/logo/third-party/Monday.svg\"\n---\n\n# monday\n\nOperate **monday** through your OOMOL-connected account. This skill calls the `monday` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected monday. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"monday\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"monday\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `activate_form` — Activate a monday Workform so it starts accepting submissions. [write]\n- `add_teams_to_board` — Add monday teams to a board as subscribers or owners. [write]\n- `add_users_to_board` — Add monday users to a board as subscribers or owners. [write]\n- `archive_board` — Archive a monday board. [write]\n- `archive_item` — Archive a monday item. [write]\n- `assign_department_members` — Assign users to a monday department on an enterprise account. [write]\n- `change_item_position` — Change a monday item's position on the same board. [write]\n- `change_multiple_column_values` — Change multiple monday column values in one mutation using the official JSON payload shape. [write]\n- `change_simple_column_value` — Change a monday column value using the official simple string mutation. [write]\n- `clear_users_department` — Clear department assignments from monday users on an enterprise account. [destructive]\n- `create_board` — Create a monday board with the official create_board mutation. [write]\n- `create_column` — Create a monday column on an existing board. [write]\n- `create_dashboard` — Create a monday dashboard with the official dashboard mutation. [write]\n- `create_department` — Create a monday department on an enterprise account. [write]\n- `create_doc` — Create a monday doc in a workspace or document column location. [write]\n- `create_form` — Create a monday Workform and its destination responses board. [write]\n- `create_group` — Create a monday group on an existing board. [write]\n- `create_item` — Create a monday item on a board, optionally setting column values and position. [write]\n- `create_subitem` — Create a monday subitem under an existing parent item. [write]\n- `create_update` — Create a monday update on an item or as a reply to an existing update. [write]\n- `create_workspace` — Create a monday workspace with the official create_workspace mutation. [write]\n- `deactivate_form` — Deactivate a monday Workform so it stops accepting submissions. [destructive]\n- `delete_board` — Delete a monday board. [destructive]\n- `delete_column` — Delete a monday column from an existing board. [destructive]\n- `delete_dashboard` — Delete a monday dashboard. [destructive]\n- `delete_department` — Delete a monday department on an enterprise account. [destructive]\n- `delete_doc` — Delete an existing monday doc. [destructive]\n- `delete_group` — Delete a monday group from an existing board. [destructive]\n- `delete_item` — Delete a monday item. [destructive]\n- `delete_subscribers_from_board` — Remove monday user subscribers from a board. [destructive]\n- `delete_teams_from_board` — Remove monday team subscribers from a board. [destructive]\n- `delete_update` — Delete an existing monday update. [destructive]\n- `delete_workspace` — Delete a monday workspace with the official delete_workspace mutation. [destructive]\n- `duplicate_item` — Duplicate a monday item. [write]\n- `edit_update` — Edit an existing monday update. [write]\n- `find_items_by_column_values` — Find monday items on a board by matching explicit column values.\n- `get_board_memberships` — Retrieve the user and team memberships configured on a monday board.\n- `get_current_user` — Retrieve the monday user associated with the current personal API token.\n- `get_form` — Retrieve a monday Workform by its unique form token.\n- `get_items` — Retrieve specific monday items by ID.\n- `get_items_page` — Retrieve a filtered page of monday board items using the official items_page query.\n- `get_next_items_page` — Retrieve the next page of monday items from an items_page cursor.\n- `list_activity_logs` — List board-scoped monday activity logs.\n- `list_assets` — Retrieve one or more monday assets by asset ID.\n- `list_audit_logs` — List account-level monday audit logs on enterprise accounts.\n- `list_board_columns` — List the columns for a specific monday board.\n- `list_boards` — List monday boards with official pagination and board-level filters.\n- `list_departments` — List monday departments on enterprise accounts.\n- `list_docs` — List monday docs by document, object, or workspace identifiers.\n- `list_groups` — List the groups for a specific monday board.\n- `list_subitems_by_parent` — List monday subitems for one or more parent items.\n- `list_team_members` — List the members of a specific monday team.\n- `list_teams` — List monday teams with official filters and pagination.\n- `list_update_replies` — List monday replies for updates on one or more boards. [write]\n- `list_updates` — List monday updates with optional date filtering.\n- `list_users` — List monday users with official root-level filters and pagination.\n- `list_workspaces` — List monday workspaces with official filters and pagination.\n- `move_item_to_board` — Move a monday item to another board and target group. [write]\n- `move_item_to_group` — Move a monday item to another group on the same board. [write]\n- `set_item_description_content` — Replace a monday item description using markdown content. [write]\n- `update_board` — Update a monday board attribute with the official update_board mutation. [write]\n- `update_column` — Update a monday column with the official update_column mutation. [write]\n- `update_dashboard` — Update a monday dashboard with the official dashboard mutation. [write]\n- `update_department` — Update a monday department on an enterprise account. [write]\n- `update_doc_name` — Update the name of an existing monday doc. [write]\n- `update_group` — Update an existing monday group attribute. [write]\n- `update_workspace` — Update a monday workspace with the official update_workspace mutation. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change monday state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — monday is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=monday\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- monday homepage: https://monday.com\n\nFile v1.0.3:_meta.json\n\n{\n \"ownerId\": \"kn7d7j8jdksrd4pyjnnxgch2y987zpvb\",\n \"slug\": \"oo-monday\",\n \"version\": \"1.0.3\",\n \"publishedAt\": 1786435524057\n}\n\nFile v1.0.3:skill-card.md\n\n## Description:\n\nmonday (monday.com) lets an agent read, create, update, and delete monday.com data through the OOMOL monday connector.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nEmployees, external users, and developers use this skill when they want an agent to operate monday.com boards, items, workspaces, docs, dashboards, forms, users, teams, departments, updates, assets, audit logs, and activity logs through an OOMOL-connected account.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: The skill can perform powerful write and delete actions against monday.com data.\n\nMitigation: Review every proposed write or delete payload carefully and require explicit confirmation before changing boards, workspaces, items, docs, departments, or related records.\n\nRisk: Connector action schemas or required scopes may differ from assumptions in a prompt.\n\nMitigation: Inspect the live action schema before building a payload and resolve connection or scope errors before retrying.\n\nRisk: The skill operates through the oo CLI and OOMOL connection path.\n\nMitigation: Install only when the user intends to operate a monday.com account through OOMOL and trusts that connection path.\n\n## Reference(s):\n\n- [monday homepage](https://monday.com)\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with shell commands and JSON command output]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Uses live connector schemas before action execution and returns connector responses with data and execution metadata.]\n\n## Skill Version(s):\n\n1.0.3 (source: server release metadata and skill metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.2: 3 files, 4380 bytes\n\nFiles: skill-card.md (2068b), SKILL.md (8570b), _meta.json (128b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: oo-monday\ndescription: \"monday (monday.com). Use this skill for ANY monday request — reading, creating, updating, and deleting data. Whenever a task involves monday, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"monday\"\n author: \"OOMOL\"\n version: \"1.0.2\"\n services: [\"monday\"]\n icon: \"https://static.oomol.com/logo/third-party/Monday.svg\"\n---\n\n# monday\n\nOperate **monday** through your OOMOL-connected account. This skill calls the `monday` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected monday. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"monday\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"monday\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `activate_form` — Activate a monday Workform so it starts accepting submissions. [write]\n- `add_teams_to_board` — Add monday teams to a board as subscribers or owners. [write]\n- `add_users_to_board` — Add monday users to a board as subscribers or owners. [write]\n- `archive_board` — Archive a monday board. [write]\n- `archive_item` — Archive a monday item. [write]\n- `assign_department_members` — Assign users to a monday department on an enterprise account. [write]\n- `change_item_position` — Change a monday item's position on the same board. [write]\n- `change_multiple_column_values` — Change multiple monday column values in one mutation using the official JSON payload shape. [write]\n- `change_simple_column_value` — Change a monday column value using the official simple string mutation. [write]\n- `clear_users_department` — Clear department assignments from monday users on an enterprise account. [destructive]\n- `create_board` — Create a monday board with the official create_board mutation. [write]\n- `create_column` — Create a monday column on an existing board. [write]\n- `create_dashboard` — Create a monday dashboard with the official dashboard mutation. [write]\n- `create_department` — Create a monday department on an enterprise account. [write]\n- `create_doc` — Create a monday doc in a workspace or document column location. [write]\n- `create_form` — Create a monday Workform and its destination responses board. [write]\n- `create_group` — Create a monday group on an existing board. [write]\n- `create_item` — Create a monday item on a board, optionally setting column values and position. [write]\n- `create_subitem` — Create a monday subitem under an existing parent item. [write]\n- `create_update` — Create a monday update on an item or as a reply to an existing update. [write]\n- `deactivate_form` — Deactivate a monday Workform so it stops accepting submissions. [destructive]\n- `delete_board` — Delete a monday board. [destructive]\n- `delete_column` — Delete a monday column from an existing board. [destructive]\n- `delete_dashboard` — Delete a monday dashboard. [destructive]\n- `delete_department` — Delete a monday department on an enterprise account. [destructive]\n- `delete_doc` — Delete an existing monday doc. [destructive]\n- `delete_group` — Delete a monday group from an existing board. [destructive]\n- `delete_item` — Delete a monday item. [destructive]\n- `delete_subscribers_from_board` — Remove monday user subscribers from a board. [destructive]\n- `delete_teams_from_board` — Remove monday team subscribers from a board. [destructive]\n- `delete_update` — Delete an existing monday update. [destructive]\n- `duplicate_item` — Duplicate a monday item. [write]\n- `edit_update` — Edit an existing monday update. [write]\n- `find_items_by_column_values` — Find monday items on a board by matching explicit column values.\n- `get_board_memberships` — Retrieve the user and team memberships configured on a monday board.\n- `get_current_user` — Retrieve the monday user associated with the current personal API token.\n- `get_form` — Retrieve a monday Workform by its unique form token.\n- `get_items` — Retrieve specific monday items by ID.\n- `get_items_page` — Retrieve a filtered page of monday board items using the official items_page query.\n- `get_next_items_page` — Retrieve the next page of monday items from an items_page cursor.\n- `list_activity_logs` — List board-scoped monday activity logs.\n- `list_assets` — Retrieve one or more monday assets by asset ID.\n- `list_audit_logs` — List account-level monday audit logs on enterprise accounts.\n- `list_board_columns` — List the columns for a specific monday board.\n- `list_boards` — List monday boards with official pagination and board-level filters.\n- `list_departments` — List monday departments on enterprise accounts.\n- `list_docs` — List monday docs by document, object, or workspace identifiers.\n- `list_groups` — List the groups for a specific monday board.\n- `list_subitems_by_parent` — List monday subitems for one or more parent items.\n- `list_team_members` — List the members of a specific monday team.\n- `list_teams` — List monday teams with official filters and pagination.\n- `list_update_replies` — List monday replies for updates on one or more boards. [write]\n- `list_updates` — List monday updates with optional date filtering.\n- `list_users` — List monday users with official root-level filters and pagination.\n- `list_workspaces` — List monday workspaces with official filters and pagination.\n- `move_item_to_board` — Move a monday item to another board and target group. [write]\n- `move_item_to_group` — Move a monday item to another group on the same board. [write]\n- `set_item_description_content` — Replace a monday item description using markdown content. [write]\n- `update_board` — Update a monday board attribute with the official update_board mutation. [write]\n- `update_column` — Update a monday column with the official update_column mutation. [write]\n- `update_dashboard` — Update a monday dashboard with the official dashboard mutation. [write]\n- `update_department` — Update a monday department on an enterprise account. [write]\n- `update_doc_name` — Update the name of an existing monday doc. [write]\n- `update_group` — Update an existing monday group attribute. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change monday state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — monday is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=monday\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- monday homepage: https://monday.com\n\nFile v1.0.2:_meta.json\n\n{\n \"ownerId\": \"kn7d7j8jdksrd4pyjnnxgch2y987zpvb\",\n \"slug\": \"oo-monday\",\n \"version\": \"1.0.2\",\n \"publishedAt\": 1783872243897\n}\n\nFile v1.0.2:skill-card.md\n\n## Description:
\nmonday (monday.com) lets an agent read, create, update, and delete monday data through the OOMOL oo CLI connector.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[oomol](https://clawhub.ai/user/oomol)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nExternal users and developers use this skill to operate monday.com workspaces through an OOMOL-connected account, including board, item, document, dashboard, team, audit log, and activity log workflows.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can change or delete monday.com data.
\nMitigation: Confirm the exact payload, target, and effect before approving write or destructive actions.
\nRisk: The skill can access sensitive monday.com workspace or account data, including audit logs on enterprise accounts.
\nMitigation: Install and use it only for monday accounts and workspaces where the agent is authorized to operate.
\n\n\n## Reference(s):
\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-monday)
\n- [monday homepage](https://monday.com)
\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)
\n- [oo CLI install guide](https://cli.oomol.com/install-guide.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [Shell commands, Configuration, Guidance]
\n**Output Format:** [Markdown guidance with inline shell commands and JSON payloads]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Requires fetching the connector action schema before constructing payloads; write and destructive actions require explicit user confirmation.]
\n\n## Skill Version(s):
\n1.0.2 (source: server release and skill metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.1: 3 files, 4475 bytes\n\nFiles: skill-card.md (2313b), SKILL.md (8579b), _meta.json (128b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: oo-monday\ndescription: \"Monday (monday.com). Use this skill for ANY Monday request — reading, creating, updating, and deleting data. Whenever a task involves Monday, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Monday\"\n author: \"OOMOL\"\n version: \"1.0.1\"\n services: [\"monday\"]\n icon: \"https://static.oomol.com/logo/third-party/Monday.svg\"\n---\n\n# Monday\n\nOperate **Monday** through your OOMOL-connected account. This skill calls the `monday` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Monday. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"monday\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"monday\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `activate_form` — Activate a Monday Workform so it starts accepting submissions. [write]\n- `add_teams_to_board` — Add Monday teams to a board as subscribers or owners. [write]\n- `add_users_to_board` — Add Monday users to a board as subscribers or owners. [write]\n- `archive_board` — Archive a Monday board. [write]\n- `archive_item` — Archive a Monday item. [write]\n- `assign_department_members` — Assign users to a Monday department on an enterprise account. [write]\n- `change_item_position` — Change a Monday item's position on the same board. [write]\n- `change_multiple_column_values` — Change multiple Monday column values in one mutation using the official JSON payload shape. [write]\n- `change_simple_column_value` — Change a Monday column value using the official simple string mutation. [write]\n- `clear_users_department` — Clear department assignments from Monday users on an enterprise account. [destructive]\n- `create_board` — Create a Monday board with the official create_board mutation. [write]\n- `create_column` — Create a Monday column on an existing board. [write]\n- `create_dashboard` — Create a Monday dashboard with the official dashboard mutation. [write]\n- `create_department` — Create a Monday department on an enterprise account. [write]\n- `create_doc` — Create a Monday doc in a workspace or document column location. [write]\n- `create_form` — Create a Monday Workform and its destination responses board. [write]\n- `create_group` — Create a Monday group on an existing board. [write]\n- `create_item` — Create a Monday item on a board, optionally setting column values and position. [write]\n- `create_subitem` — Create a Monday subitem under an existing parent item. [write]\n- `create_update` — Create a Monday update on an item or as a reply to an existing update. [write]\n- `deactivate_form` — Deactivate a Monday Workform so it stops accepting submissions. [destructive]\n- `delete_board` — Delete a Monday board. [destructive]\n- `delete_column` — Delete a Monday column from an existing board. [destructive]\n- `delete_dashboard` — Delete a Monday dashboard. [destructive]\n- `delete_department` — Delete a Monday department on an enterprise account. [destructive]\n- `delete_doc` — Delete an existing Monday doc. [destructive]\n- `delete_group` — Delete a Monday group from an existing board. [destructive]\n- `delete_item` — Delete a Monday item. [destructive]\n- `delete_subscribers_from_board` — Remove Monday user subscribers from a board. [destructive]\n- `delete_teams_from_board` — Remove Monday team subscribers from a board. [destructive]\n- `delete_update` — Delete an existing Monday update. [destructive]\n- `duplicate_item` — Duplicate a Monday item. [write]\n- `edit_update` — Edit an existing Monday update. [write]\n- `find_items_by_column_values` — Find Monday items on a board by matching explicit column values.\n- `get_board_memberships` — Retrieve the user and team memberships configured on a Monday board.\n- `get_current_user` — Retrieve the Monday user associated with the current personal API token.\n- `get_form` — Retrieve a Monday Workform by its unique form token.\n- `get_items` — Retrieve specific Monday items by ID.\n- `get_items_page` — Retrieve a filtered page of Monday board items using the official items_page query.\n- `get_next_items_page` — Retrieve the next page of Monday items from an items_page cursor.\n- `list_activity_logs` — List board-scoped Monday activity logs.\n- `list_assets` — Retrieve one or more Monday assets by asset ID.\n- `list_audit_logs` — List account-level Monday audit logs on enterprise accounts.\n- `list_board_columns` — List the columns for a specific Monday board.\n- `list_boards` — List Monday boards with official pagination and board-level filters.\n- `list_departments` — List Monday departments on enterprise accounts.\n- `list_docs` — List Monday docs by document, object, or workspace identifiers.\n- `list_groups` — List the groups for a specific Monday board.\n- `list_subitems_by_parent` — List Monday subitems for one or more parent items.\n- `list_team_members` — List the members of a specific Monday team.\n- `list_teams` — List Monday teams with official filters and pagination.\n- `list_update_replies` — List Monday replies for updates on one or more boards. [write]\n- `list_updates` — List Monday updates with optional date filtering.\n- `list_users` — List Monday users with official root-level filters and pagination.\n- `list_workspaces` — List Monday workspaces with official filters and pagination.\n- `move_item_to_board` — Move a Monday item to another board and target group. [write]\n- `move_item_to_group` — Move a Monday item to another group on the same board. [write]\n- `set_item_description_content` — Replace a Monday item description using markdown content. [write]\n- `update_board` — Update a Monday board attribute with the official update_board mutation. [write]\n- `update_column` — Update a Monday column with the official update_column mutation. [write]\n- `update_dashboard` — Update a Monday dashboard with the official dashboard mutation. [write]\n- `update_department` — Update a Monday department on an enterprise account. [write]\n- `update_doc_name` — Update the name of an existing Monday doc. [write]\n- `update_group` — Update an existing Monday group attribute. [write]\n\n## Safety\n\n- Untagged actions are reads (get / list / search) — safe to run directly.\n- **Actions tagged `[write]` change Monday state — confirm the exact payload and effect with the user before running.**\n- **Actions tagged `[destructive]` remove or overwrite data — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Monday is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2, API key) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=monday\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Monday homepage: https://monday.com\n\nFile v1.0.1:_meta.json\n\n{\n \"ownerId\": \"kn7d7j8jdksrd4pyjnnxgch2y987zpvb\",\n \"slug\": \"oo-monday\",\n \"version\": \"1.0.1\",\n \"publishedAt\": 1780999961600\n}\n\nFile v1.0.1:skill-card.md\n\n## Description:
\nOperate monday.com through an OOMOL-connected account for reading, creating, updating, moving, archiving, and deleting Monday resources.
\n\nThis skill is ready for commercial/non-commercial use.
\n\n## Publisher:
\n[oomol](https://clawhub.ai/user/oomol)
\n\n### License/Terms of Use:
\nMIT-0
\n\n\n## Use Case:
\nEmployees, operators, and developers use this skill to let an agent work with monday.com boards, items, updates, workspaces, users, teams, forms, dashboards, docs, and related resources through an OOMOL-connected account.
\n\n### Deployment Geography for Use:
\nGlobal
\n\n## Known Risks and Mitigations:
\nRisk: The skill can create, update, archive, move, and delete monday.com data.
\nMitigation: Review the exact action, target resource, and payload before approving any write or destructive operation.
\nRisk: A broad trigger may activate the skill when a user mentions Monday as a weekday rather than monday.com.
\nMitigation: Confirm the user intends to operate monday.com before running connector actions when the request is ambiguous.
\nRisk: The skill requires a connected monday.com account and can act with that account's permissions.
\nMitigation: Install it only for users who want an agent to operate their monday.com account through OOMOL.
\n\n\n## Reference(s):
\n- [ClawHub Skill Page](https://clawhub.ai/oomol/oo-monday)
\n- [Monday Homepage](https://monday.com)
\n- [OOMOL oo CLI](https://github.com/oomol-lab/oo-cli)
\n- [OOMOL CLI Install Guide](https://cli.oomol.com/install-guide.md)
\n\n\n## Skill Output:
\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]
\n**Output Format:** [Markdown with inline shell commands and JSON payload examples]
\n**Output Parameters:** [1D]
\n**Other Properties Related to Output:** [Actions may return JSON data and execution metadata from the OOMOL CLI.]
\n\n## Skill Version(s):
\n1.0.1 (source: frontmatter and server release metadata)
\n\n## Ethical Considerations:
\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.
\n\nArchive v1.0.0: 67 files, 40529 bytes\n\nFiles: actions/activate_form.md (659b), actions/add_teams_to_board.md (800b), actions/add_users_to_board.md (800b), actions/archive_board.md (621b), actions/archive_item.md (615b), actions/assign_department_members.md (848b), actions/change_item_position.md (683b), actions/change_multiple_column_values.md (769b), actions/change_simple_column_value.md (734b), actions/clear_users_department.md (860b), actions/create_board.md (779b), actions/create_column.md (766b), actions/create_dashboard.md (831b), actions/create_department.md (799b), actions/create_doc.md (768b), actions/create_form.md (804b), actions/create_group.md (760b), actions/create_item.md (791b), actions/create_subitem.md (781b), actions/create_update.md (793b), actions/deactivate_form.md (810b), actions/delete_board.md (755b), actions/delete_column.md (784b), actions/delete_dashboard.md (779b), actions/delete_department.md (815b), actions/delete_doc.md (751b), actions/delete_group.md (778b), actions/delete_item.md (749b), actions/delete_subscribers_from_board.md (862b), actions/delete_teams_from_board.md (832b), actions/delete_update.md (772b), actions/duplicate_item.md (751b), actions/edit_update.md (744b), actions/find_items_by_column_values.md (731b), actions/get_board_memberships.md (705b), actions/get_current_user.md (680b), actions/get_form.md (624b), actions/get_items_page.md (685b), actions/get_items.md (614b), actions/get_next_items_page.md (692b), actions/list_activity_logs.md (661b), actions/list_assets.md (634b), actions/list_audit_logs.md (679b), actions/list_board_columns.md (667b), actions/list_boards.md (655b), actions/list_departments.md (664b), actions/list_docs.md (638b), actions/list_groups.md (631b), actions/list_subitems_by_parent.md (697b), actions/list_team_members.md (659b), actions/list_teams.md (636b), actions/list_update_replies.md (806b), actions/list_updates.md (642b), actions/list_users.md (647b), actions/list_workspaces.md (671b), actions/move_item_to_board.md (800b), actions/move_item_to_group.md (801b), actions/set_item_description_content.md (854b), actions/update_board.md (789b), actions/update_column.md (786b), actions/update_dashboard.md (831b), actions/update_department.md (799b), actions/update_doc_name.md (772b), actions/update_group.md (759b), skill-card.md (2675b), SKILL.md (10147b), _meta.json (128b)\n\nFile v1.0.0:SKILL.md\n\n---\nname: oo-monday\ndescription: \"Monday (monday.com). Use this skill for ANY Monday request — reading, creating, updating, and deleting data. Whenever a task involves Monday, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"Monday\"\n author: \"OOMOL\"\n version: \"1.0.0\"\n service: \"monday\"\n categories: \"Productivity\"\n homepage: \"https://monday.com\"\n icon: \"https://static.oomol.com/logo/third-party/Monday.svg\"\n---\n\n# Monday\n\nOperate **Monday** through your OOMOL-connected account. This skill calls the `monday` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\nCategory: Productivity. Exposes 64 action(s).\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected Monday. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"monday\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"monday\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action below links to a reference file with its purpose and exact commands. Read the linked file, then fetch the live schema with `oo connector schema` before constructing `--data`.\n\n## Available actions\n\n- [`activate_form`](actions/activate_form.md) — Activate a Monday Workform so it starts accepting submissions.\n- [`add_teams_to_board`](actions/add_teams_to_board.md) — Add Monday teams to a board as subscribers or owners.\n- [`add_users_to_board`](actions/add_users_to_board.md) — Add Monday users to a board as subscribers or owners.\n- [`archive_board`](actions/archive_board.md) — Archive a Monday board.\n- [`archive_item`](actions/archive_item.md) — Archive a Monday item.\n- [`assign_department_members`](actions/assign_department_members.md) — Assign users to a Monday department on an enterprise account.\n- [`change_item_position`](actions/change_item_position.md) — Change a Monday item's position on the same board.\n- [`change_multiple_column_values`](actions/change_multiple_column_values.md) — Change multiple Monday column values in one mutation using the official JSON payload shape.\n- [`change_simple_column_value`](actions/change_simple_column_value.md) — Change a Monday column value using the official simple string mutation.\n- [`clear_users_department`](actions/clear_users_department.md) — Clear department assignments from Monday users on an enterprise account.\n- [`create_board`](actions/create_board.md) — Create a Monday board with the official create_board mutation.\n- [`create_column`](actions/create_column.md) — Create a Monday column on an existing board.\n- [`create_dashboard`](actions/create_dashboard.md) — Create a Monday dashboard with the official dashboard mutation.\n- [`create_department`](actions/create_department.md) — Create a Monday department on an enterprise account.\n- [`create_doc`](actions/create_doc.md) — Create a Monday doc in a workspace or document column location.\n- [`create_form`](actions/create_form.md) — Create a Monday Workform and its destination responses board.\n- [`create_group`](actions/create_group.md) — Create a Monday group on an existing board.\n- [`create_item`](actions/create_item.md) — Create a Monday item on a board, optionally setting column values and position.\n- [`create_subitem`](actions/create_subitem.md) — Create a Monday subitem under an existing parent item.\n- [`create_update`](actions/create_update.md) — Create a Monday update on an item or as a reply to an existing update.\n- [`deactivate_form`](actions/deactivate_form.md) — Deactivate a Monday Workform so it stops accepting submissions.\n- [`delete_board`](actions/delete_board.md) — Delete a Monday board.\n- [`delete_column`](actions/delete_column.md) — Delete a Monday column from an existing board.\n- [`delete_dashboard`](actions/delete_dashboard.md) — Delete a Monday dashboard.\n- [`delete_department`](actions/delete_department.md) — Delete a Monday department on an enterprise account.\n- [`delete_doc`](actions/delete_doc.md) — Delete an existing Monday doc.\n- [`delete_group`](actions/delete_group.md) — Delete a Monday group from an existing board.\n- [`delete_item`](actions/delete_item.md) — Delete a Monday item.\n- [`delete_subscribers_from_board`](actions/delete_subscribers_from_board.md) — Remove Monday user subscribers from a board.\n- [`delete_teams_from_board`](actions/delete_teams_from_board.md) — Remove Monday team subscribers from a board.\n- [`delete_update`](actions/delete_update.md) — Delete an existing Monday update.\n- [`duplicate_item`](actions/duplicate_item.md) — Duplicate a Monday item.\n- [`edit_update`](actions/edit_update.md) — Edit an existing Monday update.\n- [`find_items_by_column_values`](actions/find_items_by_column_values.md) — Find Monday items on a board by matching explicit column values.\n- [`get_board_memberships`](actions/get_board_memberships.md) — Retrieve the user and team memberships configured on a Monday board.\n- [`get_current_user`](actions/get_current_user.md) — Retrieve the Monday user associated with the current personal API token.\n- [`get_form`](actions/get_form.md) — Retrieve a Monday Workform by its unique form token.\n- [`get_items`](actions/get_items.md) — Retrieve specific Monday items by ID.\n- [`get_items_page`](actions/get_items_page.md) — Retrieve a filtered page of Monday board items using the official items_page query.\n- [`get_next_items_page`](actions/get_next_items_page.md) — Retrieve the next page of Monday items from an items_page cursor.\n- [`list_activity_logs`](actions/list_activity_logs.md) — List board-scoped Monday activity logs.\n- [`list_assets`](actions/list_assets.md) — Retrieve one or more Monday assets by asset ID.\n- [`list_audit_logs`](actions/list_audit_logs.md) — List account-level Monday audit logs on enterprise accounts.\n- [`list_board_columns`](actions/list_board_columns.md) — List the columns for a specific Monday board.\n- [`list_boards`](actions/list_boards.md) — List Monday boards with official pagination and board-level filters.\n- [`list_departments`](actions/list_departments.md) — List Monday departments on enterprise accounts.\n- [`list_docs`](actions/list_docs.md) — List Monday docs by document, object, or workspace identifiers.\n- [`list_groups`](actions/list_groups.md) — List the groups for a specific Monday board.\n- [`list_subitems_by_parent`](actions/list_subitems_by_parent.md) — List Monday subitems for one or more parent items.\n- [`list_team_members`](actions/list_team_members.md) — List the members of a specific Monday team.\n- [`list_teams`](actions/list_teams.md) — List Monday teams with official filters and pagination.\n- [`list_update_replies`](actions/list_update_replies.md) — List Monday replies for updates on one or more boards.\n- [`list_updates`](actions/list_updates.md) — List Monday updates with optional date filtering.\n- [`list_users`](actions/list_users.md) — List Monday users with official root-level filters and pagination.\n- [`list_workspaces`](actions/list_workspaces.md) — List Monday workspaces with official filters and pagination.\n- [`move_item_to_board`](actions/move_item_to_board.md) — Move a Monday item to another board and target group.\n- [`move_item_to_group`](actions/move_item_to_group.md) — Move a Monday item to another group on the same board.\n- [`set_item_description_content`](actions/set_item_description_content.md) — Replace a Monday item description using markdown content.\n- [`update_board`](actions/update_board.md) — Update a Monday board attribute with the official update_board mutation.\n- [`update_column`](actions/update_column.md) — Update a Monday column with the official update_column mutation.\n- [`update_dashboard`](actions/update_dashboard.md) — Update a Monday dashboard with the official dashboard mutation.\n- [`update_department`](actions/update_department.md) — Update a Monday department on an enterprise account.\n- [`update_doc_name`](actions/update_doc_name.md) — Update the name of an existing Monday doc.\n- [`update_group`](actions/update_group.md) — Update an existing Monday group attribute.\n\n## Safety\n\n- Read actions (get / list / search) are safe to run directly.\n- **Create, update, send, or post actions change Monday state — confirm the exact payload and effect with the user before running.**\n- **Delete or remove actions are destructive — always confirm the target and get explicit approval first.**\n\n## First-time setup\n\nThese are **one-time** steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.\n\n- **`oo: command not found`** — install the oo CLI (other platforms: ):\n\n ```bash\n curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux\n ```\n\n ```powershell\n irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell\n ```\n\n- **Not signed in / authentication error** — sign in to your OOMOL account once:\n\n ```bash\n oo auth login\n ```\n\n- **`scope_missing` / `credential_expired` / `app_not_ready` / `app_not_found`** — Monday is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2, API key) at:\n\n ```text\n https://console.oomol.com/app-connections?provider=monday\n ```\n\n- **HTTP 402 / `OOMOL_INSUFFICIENT_CREDIT`** — billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.\n\n## Resources\n\n- Monday homepage: https://monday.com\n\nFile v1.0.0:_meta.json\n\n{\n \"ownerId\": \"kn7d7j8jdksrd4pyjnnxgch2y987zpvb\",\n \"slug\": \"oo-monday\",\n \"version\": \"1.0.0\",\n \"publishedAt\": 1780624260356\n}\n\nFile v1.0.0:actions/activate_form.md\n\n# Monday · `activate_form`\n\nActivate a Monday Workform so it starts accepting submissions.\n\n- **Service**: `monday`\n- **Action**: `activate_form`\n- **Action id**: `monday.activate_form`\n- **Required scopes**: forms:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"activate_form\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"activate_form\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/add_teams_to_board.md\n\n# Monday · `add_teams_to_board`\n\nAdd Monday teams to a board as subscribers or owners.\n\n- **Service**: `monday`\n- **Action**: `add_teams_to_board`\n- **Action id**: `monday.add_teams_to_board`\n- **Required scopes**: boards:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"add_teams_to_board\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"add_teams_to_board\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Monday state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/add_users_to_board.md\n\n# Monday · `add_users_to_board`\n\nAdd Monday users to a board as subscribers or owners.\n\n- **Service**: `monday`\n- **Action**: `add_users_to_board`\n- **Action id**: `monday.add_users_to_board`\n- **Required scopes**: boards:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"add_users_to_board\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"add_users_to_board\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Monday state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/archive_board.md\n\n# Monday · `archive_board`\n\nArchive a Monday board.\n\n- **Service**: `monday`\n- **Action**: `archive_board`\n- **Action id**: `monday.archive_board`\n- **Required scopes**: boards:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"archive_board\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"archive_board\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/archive_item.md\n\n# Monday · `archive_item`\n\nArchive a Monday item.\n\n- **Service**: `monday`\n- **Action**: `archive_item`\n- **Action id**: `monday.archive_item`\n- **Required scopes**: boards:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"archive_item\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"archive_item\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/assign_department_members.md\n\n# Monday · `assign_department_members`\n\nAssign users to a Monday department on an enterprise account.\n\n- **Service**: `monday`\n- **Action**: `assign_department_members`\n- **Action id**: `monday.assign_department_members`\n- **Required scopes**: departments:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"assign_department_members\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"assign_department_members\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Write action.** This changes Monday state. Confirm the exact payload and intended effect with the user before running.\n\nFile v1.0.0:actions/change_item_position.md\n\n# Monday · `change_item_position`\n\nChange a Monday item's position on the same board.\n\n- **Service**: `monday`\n- **Action**: `change_item_position`\n- **Action id**: `monday.change_item_position`\n- **Required scopes**: boards:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"change_item_position\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"change_item_position\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/change_multiple_column_values.md\n\n# Monday · `change_multiple_column_values`\n\nChange multiple Monday column values in one mutation using the official JSON payload shape.\n\n- **Service**: `monday`\n- **Action**: `change_multiple_column_values`\n- **Action id**: `monday.change_multiple_column_values`\n- **Required scopes**: boards:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"change_multiple_column_values\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"change_multiple_column_values\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/change_simple_column_value.md\n\n# Monday · `change_simple_column_value`\n\nChange a Monday column value using the official simple string mutation.\n\n- **Service**: `monday`\n- **Action**: `change_simple_column_value`\n- **Action id**: `monday.change_simple_column_value`\n- **Required scopes**: boards:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"change_simple_column_value\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"change_simple_column_value\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\nFile v1.0.0:actions/clear_users_department.md\n\n# Monday · `clear_users_department`\n\nClear department assignments from Monday users on an enterprise account.\n\n- **Service**: `monday`\n- **Action**: `clear_users_department`\n- **Action id**: `monday.clear_users_department`\n- **Required scopes**: departments:write\n\n## Inspect the schema\n\nAlways fetch the authoritative input/output schema before building a payload — fields and defaults can change upstream:\n\n```bash\noo connector schema \"monday\" --action \"clear_users_department\"\n```\n\n## Run\n\n```bash\noo connector run \"monday\" --action \"clear_users_department\" --data '{}' --json\n```\n\nReplace `{}` with a JSON object that matches the input schema. The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`.\n\n> **Destructive action.** This removes or overwrites Monday data. Always confirm the target and get explicit user approval before running.","readmeExcerpt":"Skill: monday Owner: oomol Summary: monday (monday.com). Use this skill for ANY monday request — reading, creating, updating, and deleting data. Whenever a task involves monday, use this skill instead of calling the API directly. Tags: latest:1.0.7 Version history: v1.0.7 | 2026-09-20T03:22:43.783Z | user - Provides OOMOL-connected monday.com automation through the oo CLI without handling raw API tokens. - Supports b","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"oo connector schema \"monday\" --action \"\""},{"language":"bash","snippet":"oo connector run \"monday\" --action \"\" --data '' --json"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux"},{"language":"bash","snippet":"curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux"},{"language":"powershell","snippet":"irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShell"},{"language":"bash","snippet":"oo auth login"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: oo-monday\ndescription: \"monday (monday.com). Use this skill for ANY monday request — reading, creating, updating, and deleting data. Whenever a task involves monday, use this skill instead of calling the API directly.\"\nallowed-tools: [Bash(oo *)]\nmetadata:\n title: \"monday\"\n author: \"OOMOL\"\n version: \"1.0.7\"\n services: [\"monday\"]\n icon: \"https://static.oomol.com/logo/third-party/Monday.svg\"\n---\n\n# monday\n\nOperate **monday** through your OOMOL-connected account. This skill calls the `monday` connector with the [oo CLI](https://github.com/oomol-lab/oo-cli); OOMOL injects credentials server-side, so you never handle raw tokens.\n\n## Running an action\n\nAssume the user has already installed the oo CLI, signed in, and connected monday. **Do not run `oo auth login` or open the connection URL proactively — just run the action.** Fall back to [First-time setup](#first-time-setup) only when a command actually fails with an auth or connection error.\n\n**1. Inspect the contract** to get the authoritative input/output schema before building a payload:\n\n```bash\noo connector schema \"monday\" --action \"\"\n```\n\n**2. Run the action** with a JSON payload that matches the input schema:\n\n```bash\noo connector run \"monday\" --action \"\" --data '' --json\n```\n\n- `--data` takes a JSON object string or `@path/to/file.json`; omit it to send `{}`.\n- The response is `{ \"data\": ..., \"meta\": { \"executionId\": \"...\" } }`; the execution id lives under `meta.executionId`.\n\nEach action is listed below with a one-line description; actions that change state carry a `[write]` or `[destructive]` tag. Before constructing `--data`, fetch the action's live schema with `oo connector schema` to get its authoritative input fields.\n\n## Available actions\n\n- `activate_form` — Activate a monday Workform so it starts accepting submissions. [write]\n- `add_teams_to_board` — Add monday teams to a board as subscribers or owners. [write]\n- `add_users_to_board` — Add monday users to a board as subscribers or owners. [write]\n- `archive_board` — Archive a monday board. [destructive]\n- `archive_item` — Archive a monday item. [destructive]\n- `assign_department_members` — Assign users to a monday department on an enterprise account. [write]\n- `change_item_position` — Change a monday item's position on the same board. [write]\n- `change_multiple_column_values` — Change multiple monday column values in one mutation using the official JSON payload shape. [write]\n- `change_simple_column_value` — Change a monday column value using the official simple string mutation. [write]\n- `clear_users_department` — Clear department assignments from monday users on an enterprise account. [destructive]\n- `create_board` — Create a monday board with the official create_board mutation. [write]\n- `create_column` — Create a monday column on an existing board. [write]\n- `create_dashboard` — Create a monday dashboard with the official dashboard mutation. [write]\n- `create_department` — Create a "},{"path":"_meta.json","content":"{\n \"ownerId\": \"kn7d7j8jdksrd4pyjnnxgch2y987zpvb\",\n \"slug\": \"oo-monday\",\n \"version\": \"1.0.7\",\n \"publishedAt\": 1789874563783\n}"},{"path":"skill-card.md","content":"## Description:\n\nOperates monday.com through OOMOL's oo CLI connector for reading, creating, updating, and deleting monday data.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[oomol](https://clawhub.ai/user/oomol)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nAgents and users with an OOMOL-connected monday account use this skill to inspect action schemas and run monday connector actions for boards, items, workspaces, docs, forms, dashboards, users, teams, and departments. It supports read workflows and user-confirmed write or destructive operations.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: First-time setup can run remote installer scripts for the oo CLI.\n\nMitigation: Review the installer path before installing and prefer a verified or package-manager installation of the oo CLI.\n\nRisk: A connected monday account can be used for write or destructive actions.\n\nMitigation: Allow write or destructive monday actions only after checking the exact board, item, workspace, and payload the agent will send.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/oomol/skills/oo-monday)\n- [OOMOL publisher profile](https://clawhub.ai/user/oomol)\n- [oo CLI](https://github.com/oomol-lab/oo-cli)\n- [monday.com](https://monday.com)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with inline shell commands and JSON payload examples]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Commands use the oo CLI and return connector responses containing data and meta.executionId.]\n\n## Skill Version(s):\n\n1.0.7 (source: server evidence and frontmatter)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":null,"editorialQuality":{"score":100,"threshold":65,"status":"thin","wordCount":1652,"uniquenessScore":37,"reasons":["uniqueness-below-45"]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T00:50:28.559Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T00:50:28.559Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:55:08.117Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}