Catch up on the Confluence pages that changed this week

SKILL.md---
name: confluence-pages-changed-this-week
description: "Every Friday: pages created or edited this week in the Confluence spaces you follow, grouped by space, with one line on what changed in each. Use when the user asks for this, or when it runs on a schedule."
---

# Confluence pages changed this week

Every Friday: pages created or edited this week in the Confluence spaces you follow, grouped by space, with one line on what changed in each.

Watching a Confluence space means an email per edit, and most people filter those away. The result is a runbook that changed on Tuesday and an on-call engineer who finds out during the next incident.

Every Friday the agent searches the spaces you follow for pages created or edited in the last seven days, compares each page with its version from before the week, and writes one line on what changed. Product managers and engineering leads get a reading list instead of an inbox.

## 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

- View access to the spaces, through the Atlassian Rovo MCP server or an Atlassian API token with your email (`CONFLUENCE_EMAIL`, `CONFLUENCE_API_TOKEN`) for `https://<site>.atlassian.net/wiki`. The skill only reads.
- The space keys to follow.

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

### Steps

1. **Search the week's changes** (Confluence): Call `GET /wiki/rest/api/search` with `cql=space in (ENG, PROD, SUP) and type = page and lastmodified >= startOfDay("-7d") order by lastmodified desc` and `limit=50`, or `searchConfluence` on the Atlassian Rovo MCP server. Pages that also match `created >= startOfDay("-7d")` are new.
2. **Read the versions** (Confluence): For each edited page call `GET /wiki/api/v2/pages/{id}/versions` and keep this week's versions with `authorId`, `createdAt`, `message` and `minorEdit`. Note the last version from before the week.
3. **Say what changed** (Confluence): Compare that older version with the current one, using `diffConfluenceContentVersions` on the Rovo MCP server or by fetching both bodies (`GET /wiki/api/v2/pages/{id}?version=<n>&body-format=storage`). Write one line: sections added or removed, steps or owners changed, dates moved.
4. **Write the digest**: Group by space, new pages first, then edits by number of versions. Pages with only minor edits get a count, not a line.

## Route B: the browser

### What you need

- Signed in to Atlassian with an account that can view the spaces; pages restricted away from that account do not appear in search.

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

### Steps

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

1. **Open search on your site**: Open `https://home.atlassian.com`, pick your Confluence site, and click the search box at the top, then **Advanced search**. Confluence pages live at `https://<site>.atlassian.net/wiki`.
2. **Filter to the week**: Set **Type** to **Page**, **Space** to each space you follow (ENG, PROD, SUP), and the last modified date filter to the past 7 days. Sort by **Last modified**. A page whose created date is also inside the week is new.
3. **Compare each edited page**: Open each edited page, choose **Page history** from the **...** menu, tick the current version and the last version from before this week, and click **Compare selected versions**. Note the version count, who edited, and which versions are marked minor.
4. **Write the digest**: Group by space, new pages first, then edits by number of versions, one line on what changed per page with the editor and link. Count pages with only minor edits instead of describing them.

Note: The search results page loads more results as you scroll and does not export, so for spaces with more than a hundred changed pages a week the API route is the practical one. Each space overview also has a recently updated feed you can read instead of search.

## The report

- **Pages changed** this week, new and edited, per space.
- **Each page**: what changed in one line, who edited it, and a link.
- **Minor edits** as a count per space.
- One line on the change most people should know about.

## 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": "confluence-pages-changed-this-week/<date of this run, e.g. 2026-10-16>",
  "item_key": "confluence-pages-changed-this-week",
  "project": "Acme",
  "source": "Confluence pages changed this week skill",
  "kind": "update",
  "title": "17 Confluence pages changed in 3 spaces",
  "summary": "**4 new** and **13 edited** pages in Engineering, Product and Support. The payments incident runbook changed most: escalations now go to the platform on-call.",
  "widget": [
    {
      "type": "Bars",
      "props": {
        "unit": "pages",
        "items": [
          {
            "label": "Engineering",
            "value": 8
          },
          {
            "label": "Product",
            "value": 5
          },
          {
            "label": "Support",
            "value": 4
          }
        ]
      }
    },
    {
      "type": "Table",
      "props": {
        "columns": [
          "Page",
          "Space",
          "What changed",
          "By"
        ],
        "align": [
          "left",
          "left",
          "left",
          "left"
        ],
        "rows": [
          [
            "Payments incident runbook",
            "ENG",
            "Escalation path now goes to the platform on-call",
            "Sam"
          ],
          [
            "API versioning policy",
            "ENG",
            "New page",
            "Theo"
          ],
          [
            "Q4 launch plan",
            "PROD",
            "Launch moved to Nov 18; beta list added",
            "Dana"
          ],
          [
            "Pricing FAQ",
            "SUP",
            "Answers for the annual plan added",
            "Lena"
          ],
          [
            "Refund macro guide",
            "SUP",
            "New page",
            "Lena"
          ],
          [
            "Feature flag naming",
            "ENG",
            "Owners added per flag prefix",
            "Priya"
          ]
        ]
      }
    }
  ]
}
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 confluence-pages-changed-this-week 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/confluence-pages-changed-this-week#schedule

Source: https://briefkin.dev/skills/confluence-pages-changed-this-week