--- name: monday-weekly-board-status-report description: "Every Friday: items by status on each monday.com board you follow, what moved to Done this week, and what has sat in one status for 14 days. Use when the user asks for this, or when it runs on a schedule." --- # Monday.com weekly board status report Every Friday: items by status on each monday.com board you follow, what moved to Done this week, and what has sat in one status for 14 days. monday.com dashboards show status as colored bars, which is fine until someone asks what actually finished this week, or which items have been "Working on it" since the start of the month. Project managers end up filtering boards by hand before every status meeting. The agent reads each board you follow, counts items by status, finds what reached Done in the last seven days, and lists the items whose status has not changed in 14 days. The weekly update writes itself, with the stuck items and their owners named. ## Two ways to get the data Use the API or MCP route when you have an MCP server, a CLI or an API token for the app. Otherwise, if you can drive a browser the user is signed in to (Claude in Chrome, a Playwright or Chrome DevTools MCP server), use the browser route. Say which one you used. ## Route A: API or MCP server ### What you need - The monday.com MCP server (`https://mcp.monday.com/mcp`, OAuth) or a personal API token in `MONDAY_API_TOKEN` for `https://api.monday.com/v2`, with access to the boards. - The board IDs, and the IDs of the status and owner columns if they are not `status` and `person`. If something is missing, say what and stop; do not invent numbers. ### Steps 1. **Read every item** (monday.com): Query `boards(ids: []) { name items_page(limit: 500) { cursor items { id name group { title } column_values(ids: ["status", "person"]) { id text value } } } }`, then `next_items_page(cursor: "", limit: 500)` until the cursor comes back empty. 2. **Read the status changes**: The status column's `text` is the label, and its `value` JSON carries `changed_at`, the time the status last changed. Count items by label per board. 3. **Find what finished and what is stuck**: Items labeled Done with `changed_at` in the last 7 days moved to Done this week. Items not done whose `changed_at` is more than 14 days ago are stuck; sort them by days, with their owner from the person column. 4. **Write the report**: One row per board with counts by status and done this week, then the stuck items with board, status, days and owner, then one line on the board that needs attention. ## Route B: the browser ### What you need - Signed in to monday.com as a member of the account with at least viewer access to the boards; board owners can save the filters as a view so the next run is faster. If something is missing, say what and stop; do not invent numbers. ### Steps Start at https://auth.monday.com/. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears. 1. **Open the first board**: The sign-in page sends you to your account at `.monday.com`. Open each board you follow from the left sidebar, in its main **Table** view, and expand every group so all items are visible. 2. **Count items by status**: Click the status column header and choose **Group by** (or read the column summary bar at the bottom of each group, which shows the share of each label). Note the count per label for the board. 3. **Find what finished this week**: Add the **Last updated** column with the **+** at the end of the header row if it is not there. Use **Filter > Advanced filters** with `Status` is `Done` and `Last updated` is in the past 7 days, and count the items. 4. **Find the stuck items**: Change the filter to `Status` is not `Done` and `Last updated` is more than 14 days ago. Sort by Last updated, oldest first, and note each item with its board, status, days and the person in the owner column. 5. **Repeat and write it up**: Do the same on the other boards. Report one row per board with counts by status and done this week, then the stuck items with owners, and one line on the board that needs attention. Note: The Last updated column reflects any change to the item, not only its status, so an item that was renamed or commented on recently can hide from the stuck list even if its status is old. The API route reads the status change time itself; in the browser, open an item's Activity Log to confirm when its status last changed. ## The report - **Per board**: items by status and items moved to Done this week. - **Stuck items**: no status change in 14 days, with board, status, days and owner. - One line on the board that needs attention first. ## Post it to Briefkin When `BRIEFKIN_TOKEN` is set, or `~/.config/briefkin/env` exists (the installer from https://briefkin.dev/docs writes it), also send the result to the user's Briefkin board as one card. Keep the `item_key` the same on every run so the card updates in place, use a new `event_id` per run, and put today's real numbers in place of the example ones. If the request fails, say so once and carry on. ```bash [ -n "${BRIEFKIN_TOKEN:-}" ] || . ~/.config/briefkin/env curl -sS -X POST "${BRIEFKIN_URL:-https://briefkin.dev}/v1/events" \ -H "authorization: Bearer $BRIEFKIN_TOKEN" \ -H "content-type: application/json" \ -d @- <<'JSON' { "v": 1, "event_id": "monday-weekly-board-status-report/", "item_key": "monday-weekly-board-status-report", "project": "Acme", "source": "Monday.com weekly board status report skill", "kind": "update", "title": "22 items done on 3 boards this week", "summary": "**22 items** moved to Done across Website, Campaigns and Partnerships. **7 items** have kept the same status for 14 days or more, 4 of them marked Stuck.", "widget": [ { "type": "Table", "props": { "columns": [ "Board", "Not started", "Working on it", "Stuck", "Done this week" ], "align": [ "left", "right", "right", "right", "right" ], "rows": [ [ "Website", 14, 12, 3, 9 ], [ "Campaigns", 6, 8, 1, 8 ], [ "Partnerships", 9, 5, 2, 5 ] ] } }, { "type": "Table", "props": { "columns": [ "Item", "Board", "Status", "Days", "Owner" ], "align": [ "left", "left", "left", "right", "left" ], "rows": [ [ "Blog redesign", "Website", "Working on it", 24, "Lena" ], [ "Homepage hero test", "Website", "Stuck", 21, "Sam" ], [ "Cookie banner update", "Website", "Stuck", 18, "Theo" ], [ "Q4 webinar series", "Campaigns", "Working on it", 17, "Priya" ], [ "Partner portal access", "Partnerships", "Stuck", 16, "Marco" ], [ "Contoso co-marketing plan", "Partnerships", "Stuck", 15, "Dana" ], [ "Case study: Fabrikam", "Partnerships", "Working on it", 14, "Dana" ] ] } }, { "type": "Callout", "props": { "text": "Website holds 3 of the 7 stuck items, and the blog redesign has been \"Working on it\" for 24 days.", "tone": "warn" } } ] } JSON ``` Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report. ## Run it on a schedule Suggested: Fridays at 15:00 (`0 15 * * 5`). From cron, with the agent signed in on that machine: ```bash 0 15 * * 5 claude -p "Run the monday-weekly-board-status-report skill" # Codex: codex exec, Gemini CLI: gemini -p, Copilot CLI: copilot -p, OpenCode: opencode run ``` Or use the agent's own scheduler (Claude Code routines, Codex automations, Claude or ChatGPT scheduled tasks): https://briefkin.dev/skills/monday-weekly-board-status-report#schedule Source: https://briefkin.dev/skills/monday-weekly-board-status-report