Get a weekly summary of your Trello board from your AI agent

SKILL.md---
name: trello-weekly-board-summary
description: "Every Friday: cards moved to Done this week, new cards, and cards stuck in the same list for over 7 days, for each Trello board you follow. Use when the user asks for this, or when it runs on a schedule."
---

# Trello weekly board summary

Every Friday: cards moved to Done this week, new cards, and cards stuck in the same list for over 7 days, for each Trello board you follow.

Trello boards show where cards are, not how long they have been there. A card can sit in Review for two weeks and look exactly like one that arrived this morning, and the weekly sync spends its first ten minutes rebuilding what moved.

Every Friday the agent reads the board's activity for the week: what reached Done, what was added, and which cards have not changed lists in more than seven days. Founders and team leads get the week in one card, with the stuck cards 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

- A Trello API key and token with read access to the board, in `TRELLO_API_KEY` and `TRELLO_TOKEN` (keys come from a Power-Up you create in Trello's admin portal).
- The board, and which lists mean done and which are backlog.

If something is missing, say what and stop; do not invent numbers.

### Steps

1. **Read the week's activity** (Trello): Call `GET /1/boards/{boardId}/actions?filter=createCard,updateCard&since=<7 days ago, ISO>&limit=1000`. A list move is an `updateCard` whose `data` has `listBefore` and `listAfter`; a move into your Done list counts as done.
2. **Read the cards and lists** (Trello): Call `GET /1/boards/{boardId}/cards?fields=name,idList,idMembers,due,dateLastActivity,shortUrl`, `GET /1/boards/{boardId}/lists?fields=name` and `GET /1/boards/{boardId}/members` to turn IDs into names.
3. **Find stuck cards** (Trello): For each open card outside Done and backlog lists, find when it entered its current list: the latest move or `createCard` this week, or for older cards `GET /1/cards/{id}/actions?filter=updateCard:idList,createCard&limit=1`. Stuck means more than 7 days in the same list.
4. **Write the summary**: Done, new and stuck counts with the change on last week (saved in a JSON file), then the stuck cards by days in list with members and links, then the cards that reached Done.

## Route B: the browser

### What you need

- Signed in to Trello as a member of the board, or as a Workspace member for a Workspace-visible board; a private board you are not on will not open.

If something is missing, say what and stop; do not invent numbers.

### Steps

Start at https://trello.com. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.

1. **Open the board and its activity**: Open `https://trello.com`, which lists your boards, and open the board. Click **Menu** (the **...** at the top right), then **Activity**. Read the feed back to 7 days ago, clicking **Load more** as needed.
2. **Count moves and new cards**: Each entry "moved this card from X to Y" with Y your Done list counts as done; each "added this card to X" is a new card. Note the member and the date for every one.
3. **Find stuck cards**: For each open card outside Done and Backlog, open it and read its **Activity** section: the newest "moved this card" or "added this card" entry tells you when it entered its current list. More than 7 days means stuck. Note the list and members.
4. **Write the summary**: Done, new and stuck counts with the change on last week (keep last week's numbers in a note), then the stuck cards by days in list with members and links, then the cards that reached Done.

Note: The board Activity feed has no date filter and loads a page at a time, and card activity is one card at a time, so a board with more than about fifty open cards is slow in a browser. Archived cards do not appear on the board; open Menu, Archived items, if your team finishes cards by archiving them.

## The report

- **Done**, **new** and **stuck** counts for the week, with the change on last week.
- **Stuck cards**: card, list, days in that list, members.
- **Done this week**: the cards that reached Done, by member.
- One line on the list where cards wait longest.

## 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": "trello-weekly-board-summary/<date of this run, e.g. 2026-10-16>",
  "item_key": "trello-weekly-board-summary",
  "project": "Acme",
  "source": "Trello weekly board summary skill",
  "kind": "update",
  "title": "19 cards done, 6 stuck over a week",
  "summary": "On the Marketing board, **19 cards** reached Done and **11** were added this week. **6 cards** have sat in the same list for more than 7 days, 4 of them in Review.",
  "widget": [
    {
      "type": "Grid",
      "props": {
        "columns": 3
      },
      "children": [
        {
          "type": "Stat",
          "props": {
            "label": "Done",
            "value": 19,
            "delta": 27
          }
        },
        {
          "type": "Stat",
          "props": {
            "label": "New",
            "value": 11
          }
        },
        {
          "type": "Stat",
          "props": {
            "label": "Stuck over 7 days",
            "value": 6,
            "tone": "warn"
          }
        }
      ]
    },
    {
      "type": "Table",
      "props": {
        "columns": [
          "Card",
          "List",
          "Days in list",
          "Members"
        ],
        "align": [
          "left",
          "left",
          "right",
          "left"
        ],
        "rows": [
          [
            "Holiday campaign brief",
            "Review",
            12,
            "Dana"
          ],
          [
            "Webinar landing page",
            "Doing",
            11,
            "Marco"
          ],
          [
            "Partner newsletter",
            "Review",
            10,
            "Lena"
          ],
          [
            "Case study: Contoso",
            "Review",
            9,
            "Priya"
          ],
          [
            "Pricing page test",
            "Review",
            8,
            "Sam"
          ],
          [
            "Ad creative refresh",
            "Doing",
            8,
            "Theo"
          ]
        ]
      }
    },
    {
      "type": "Callout",
      "props": {
        "text": "Review is where cards wait: 4 of the 6 stuck cards are there, the oldest for 12 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 trello-weekly-board-summary 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/trello-weekly-board-summary#schedule

Source: https://briefkin.dev/skills/trello-weekly-board-summary