From monday-com
Creates and configures monday.com boards with proper structure including groups, columns, and initial items. monday.com boards are flexible enough to manage any workflow - project trackers, CRM pipelines, bug trackers, content calendars, and more. Use when user asks to "create a board", "set up a project", "new board for", "build a tracker", "organize my project", "create a board for tracking", or "set up a workflow".
How this skill is triggered — by the user, by Claude, or both
Slash command
/monday-com:board-setupThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create and configure monday.com boards with proper structure - the right column types, meaningful groups, and initial items. In monday.com, a board is the central workspace where a team tracks any workflow: project delivery, sales pipeline, bug triage, content production, event planning, and more. This skill provides the domain knowledge needed to build well-organized boards that match how team...
Create and configure monday.com boards with proper structure - the right column types, meaningful groups, and initial items. In monday.com, a board is the central workspace where a team tracks any workflow: project delivery, sales pipeline, bug triage, content production, event planning, and more. This skill provides the domain knowledge needed to build well-organized boards that match how teams actually work.
Before creating anything, clarify with the user:
If the user gives a brief request like "create a project board", use reasonable defaults based on the use case and confirm the structure before creating.
Based on requirements, plan:
Call create_board with:
boardName: descriptive nameboardKind: "public" (visible to all team members) or "private" (visible only to subscribers)Call create_group for each workflow stage or category.
Position the new groups above the default group. A new monday board ships with a default empty group named "Group Title" (id topics). To put your workflow groups in the right order at the top of the board, pass positionRelativeMethod: "before_at" and relativeTo: "topics" on each create_group call. Create groups in workflow order (the first group you create becomes the first group on the board, and top_group - which is where new items will land by default).
Clean up the default group at the end. Once your workflow groups exist, the default topics group is a leftover empty group that confuses users. Delete it by calling all_monday_api with the delete_group mutation: mutation { delete_group(board_id: <id>, group_id: "topics") { id } }. Skipping this leaves the board with a dangling empty group below the workflow.
Common group patterns:
By workflow stage (most common):
By priority:
By time period:
By team/department:
By category:
Call create_column for each data field. For each column, specify:
boardId: the board ID from Step 3title: the display namecolumnType: the monday.com column type (see Column Type Selection below)columnSettings: JSON-stringified label config when the column needs custom labels (see "Custom labels for status columns" below)Add columns in this order (left to right on the board):
status columns created without columnSettings always get the default monday labels: "Working on it" (orange), "Done" (green), "Stuck" (red). That is fine for the primary workflow Status column, but it is wrong for any other status column the template needs - Priority, Severity, Stage, and Risk all end up with confusing default labels unless you pass custom ones at creation time.
Pass columnSettings as a JSON string with the shape:
{"labels": [{"label": "<name>", "color": "<color_token>", "index": <0..n>}, ...]}
Each entry needs label, color, and index (other fields are optional). The color token is a string from monday's StatusColumnColors enum. Useful tokens by category:
sky, bright_blue, aquamarine, saladishworking_orange, orange, egg_yolk, purpledark_orange, sunset, lipstickstuck_red, dark_red, bright_green (only for "approved")done_green, grass_greenReference label sets to use in the templates below:
[{"label":"Low","color":"sky","index":0},{"label":"Medium","color":"working_orange","index":1},{"label":"High","color":"dark_orange","index":2},{"label":"Critical","color":"stuck_red","index":3}][{"label":"Low","color":"saladish","index":0},{"label":"Medium","color":"egg_yolk","index":1},{"label":"High","color":"dark_orange","index":2}]If the user requests a status column whose meaning is not workflow ("Priority", "Severity", "Risk", "Stage", "Health", "Confidence", etc.), default to a Low/Medium/High/Critical scale unless they tell you the labels they want. State the defaults you used so they can override.
For the primary workflow Status column, leave columnSettings off - the defaults match what most users expect.
If the user provides initial items, call create_item for each one. Follow the column value formatting rules from the task-management skill.
Report what was built in plain language - don't narrate the API calls. Include the direct URL returned by the MCP tool.
Summarize what was created:
Board Created: [Board Name]
Groups:
Columns:
| Column | Type | Purpose |
|---|---|---|
| Status | Status | Workflow state |
| Owner | People | Item assignee |
| Due Date | Date | Deadline |
| Priority | Status | Importance level |
| Notes | Text | Additional context |
Then suggest 2-3 logical next steps:
Choosing the right column type is critical. Using a text column where you need a status column means losing filtering, grouping, and automation capabilities.
For the complete column type reference, see references/column-types-guide.md.
Quick selection guide for the most common needs:
| What you need | Column type | Why not text? |
|---|---|---|
| Workflow state (To Do, In Progress, Done) | status | Enables color-coding, filtering by status, automations |
| Who's responsible | people | Links to monday.com users, enables workload views |
| Deadline | date | Enables calendar view, timeline view, overdue detection |
| Date range (start-to-end) | timeline | Shows duration bars in timeline view |
| Importance level | status (labeled "Priority") | Color-coded, filterable, sortable |
| Effort estimate | numbers | Enables sum, average, and formula calculations |
| Category tags | dropdown | Multi-select from predefined options |
| Yes/no flag | checkbox | Visual toggle, filterable |
| Free-form notes | text | Simple text input |
| Long description | long_text | Rich text with formatting |
| File attachments | file | Upload and preview files inline |
| Web link | link | Clickable URL with display text |
| Email address | email | Clickable mailto link |
| Phone number | phone | Clickable tel link |
| Budget/cost | numbers | Supports currency formatting and formulas |
| Rating | rating | 1-5 star visual rating |
| Progress | progress | Visual progress bar based on subitems or linked column |
Most column types work on every monday plan. Two are gated and the skill should handle this gracefully:
numbers column the user updates manuallytext column with a calculated value the user pastes from elsewhereIf the user is unsure of their plan, just create the board with standard columns first and offer to add formula columns later if their plan supports it.
create_board fails due to permissions, suggest using an existing workspace the user has admin access to, or ask which workspace they want to use.create_board, call search with the requested board name scoped to the target workspace. If a board with that name already exists, ask the user: use the existing one, create with a suffix (e.g., "Board Name (2)"), or pick a different name. Skipping this check and creating a duplicate is a fail.columnSettings JSON is malformed, create_column returns an error. The label format requires an array of {label, color, index} objects, not a name->color map. See "Custom labels for status columns" above.search - preflight check for board name collisions before create_boardget_column_type_info - understand available column types and their schemas (including the columnSettings shape for status columns)create_board - create the boardcreate_group - add groups to the boardcreate_column - add columns with correct types and custom columnSettings for Priority / Severity / Stage / Risk / etc.create_item - seed initial items (optional)all_monday_api - delete the default topics group after the workflow groups are in placereferences/column-types-guide.md - Complete guide to all monday.com column types, when to use each, and configuration optionsnpx claudepluginhub ai-integr8tor/anthropics-knowledge-work-plugins --plugin monday-comProvides C# and .NET testing patterns using xUnit, FluentAssertions, NSubstitute, Testcontainers, and WebApplicationFactory for unit and integration tests.