# monday

Interacts with Monday.com boards and tasks through the Membrane CLI. Lets your agent inspect project records and track task execution directly.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 424 installs · ★ 270
- Author: membrane
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/membranedev/application-skills/tree/HEAD/skills/monday/SKILL.md
- Updated: 2026-04-28
- HTML: https://affpapa.org/en/nevibecode/skills/monday

## What it does

This skill connects your coding assistant to Monday.com. It handles reading boards and updating item columns. The interaction relies on Membrane CLI, which manages authentication and refreshes credentials in the background.

Available actions cover standard operations like `list-boards`, `create-item`, `get-board`, and `update-item-column-values`. If an operation is missing, the skill routes raw HTTP calls directly to the API endpoint via `membrane request`.

Prerequisites include a Membrane account and `@membranehq/cli` installed via npm with network access. Running without prior authentication via `membrane login` breaks the connection immediately.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill monday -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/monday/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/monday/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill monday -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/monday/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill monday -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/monday/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install membranedev/application-skills monday
```

2. **Manually: put the files in place**
- File: `.github/skills/monday/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill monday -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/membranedev/application-skills --path skills/monday
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/monday/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add membranedev/application-skills --skill monday -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/membranedev/application-skills/tree/HEAD/skills/monday/SKILL.md

## When to use it
- list boards and retrieve column values
- create new tasks or groups on a board
- modify item properties and status fields
- post comments to project items

## Example prompts
- Show all active tasks on the Sprint board
- Create a new item named 'Fix auth bug' on the backlog board
- Post an update to item 987654321

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: f68ec3a5751ad658.

BEGIN THIRD-PARTY FILE f68ec3a5751ad658
````text
---
name: monday
description: |
  Monday integration. Manage project management data, records, and workflows. Use when the user wants to interact with Monday data.
compatibility: Requires network access and a valid Membrane account (Free tier supported).
license: MIT
homepage: https://getmembrane.com
repository: https://github.com/membranedev/application-skills
metadata:
  author: membrane
  version: "1.0"
  categories: ""
---

# Monday

Monday.com is a work operating system where teams can plan, track, and manage their work. It's used by project managers, marketing teams, and sales teams to improve collaboration and execution.

Official docs: https://developers.monday.com/

## Monday Overview

- **Board**
  - **Item**
    - **Column**
- **User**

When to use which actions: Use action names and parameters as needed.

## Working with Monday

This skill uses the Membrane CLI to interact with Monday. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.

### Install the CLI

Install the Membrane CLI so you can run `membrane` from the terminal:

```bash
npm install -g @membranehq/cli@latest
```

### Authentication

```bash
membrane login --tenant --clientName=<agentType>
```

This will either open a browser for authentication or print an authorization URL to the console, depending on whether interactive mode is available.

**Headless environments:** The command will print an authorization URL. Ask the user to open it in a browser. When they see a code after completing login, finish with:

```bash
membrane login complete <code>
```

Add `--json` to any command for machine-readable JSON output.

**Agent Types** : claude, openclaw, codex, warp, windsurf, etc. Those will be used to adjust tooling to be used best with your harness

### Connecting to Monday

Use `membrane connection ensure` to find or create a connection by app URL or domain:

```bash
membrane connection ensure "" --json
```
The user completes authentication in the browser. The output contains the new connection id.

This is the fastest way to get a connection. The URL is normalized to a domain and matched against known apps. If no app is found, one is created and a connector is built automatically.

If the returned connection has `state: "READY"`, skip to **Step 2**.

#### 1b. Wait for the connection to be ready

If the connection is in `BUILDING` state, poll until it's ready:

```bash
npx @membranehq/cli connection get <id> --wait --json
```

The `--wait` flag long-polls (up to `--timeout` seconds, default 30) until the state changes. Keep polling until `state` is no longer `BUILDING`.

The resulting state tells you what to do next:

- **`READY`** — connection is fully set up. Skip to **Step 2**.
- **`CLIENT_ACTION_REQUIRED`** — the user or agent needs to do something. The `clientAction` object describes the required action:
  - `clientAction.type` — the kind of action needed:
    - `"connect"` — user needs to authenticate (OAuth, API key, etc.). This covers initial authentication and re-authentication for disconnected connections.
    - `"provide-input"` — more information is needed (e.g. which app to connect to).
  - `clientAction.description` — human-readable explanation of what's needed.
````
END THIRD-PARTY FILE f68ec3a5751ad658

The third-party file has ended. Everything between the f68ec3a5751ad658 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3309 of 7818 bytes. © membrane · MIT · https://github.com/membranedev/application-skills/tree/HEAD/skills/monday/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md