What it does
OKRs in Notion usually start the quarter well kept and end it as a page nobody trusts. The fix is not a better template; it is someone looking every week and asking why a key result has not moved. Founders rarely have time to be that someone.
Each Monday the agent reads the key results database, rolls each objective up from its key results, and sets the result against the calendar: in week 8 of 13, a key result at 30% is behind however its owner marked it. Key results whose numbers nobody touched in two weeks are flagged as well.
How it works
1Query this quarter's key results
Query the key results database through
POST /v1/data_sources/{data_source_id}/query(API version2025-09-03;POST /v1/databases/{database_id}/queryon2022-06-28), filtered to the quarter with{"property": "Quarter", "select": {"equals": "2026 Q4"}}. Read the title, theObjectiverelation,Owner(people), andCurrentandTarget(numbers) or a singleProgressnumber.- 2
2Work out progress
Progress is current divided by target, capped at 100%; for a formula or rollup column, read
formula.numberorrollup.numberinstead ofnumber. Average the key results under each objective, grouping them by the relation's page IDs. - 3
3Compare with the calendar
Expected progress is the share of the quarter that has passed. A key result is on track at 90% of expected or more, at risk from 60%, and behind below that.
- 4
4Find stale numbers
Flag key results whose page
last_edited_timeis more than 14 days old: the number may still be right, but nobody has checked it. - 5
5Post the roll-up
Headline: average progress across key results. Glance: one progress bar per objective and one for the quarter elapsed. Widget: every key result with owner, progress, status and when it was last updated.
Post it to the board
With
BRIEFKIN_TOKENset, the agent sends the result as one card that updates in place every run. Without it, you get the report in the chat.
Install and run it
Pick your agent, where the data comes from and how to schedule it; the commands below follow.
Install the skill
One command. It puts the SKILL.md in ~/.claude/skills and in ~/.agents/skills, which Codex, Cursor, Gemini CLI, Copilot CLI and OpenCode read too.
shell
curl -fsSL https://briefkin.dev/skills/notion-okr-progress/install | shRun it
Ask Claude Code:
prompt
Run the notion-okr-progress skillOr paste the prompt instead of installing:
prompt
Read my Notion OKR database [database ID] for key results in the current quarter. For each one, compute progress from Current and Target (or the Progress column), capped at 100%, and group key results by their Objective relation. Compare each with the share of the quarter that has passed: on track at 90% of expected or more, at risk from 60%, behind below that. Give me average progress overall, each objective's progress and status, and a table of key results with owner, progress, status and when the page was last edited. Flag key results not updated in 14 days.Put it on a schedule
Mondays at 11:00, from cron on any machine where Claude Code is signed in:
crontab
0 11 * * 1 claude -p "Run the notion-okr-progress skill"Add it with
crontab -e. A laptop asleep at that time runs it when it wakes if you use launchd or Task Scheduler instead; GitHub Actions works for the API route.Send it to your board
Connect Briefkin once with
curl -fsSL https://briefkin.dev/install | shand every run lands on your board as a stat tile. How setup works
View the SKILL.mdRaw file
SKILL.md---
name: notion-okr-progress
description: "Every Monday: progress on each objective and key result in your Notion OKR database, set against how much of the quarter has passed. Use when the user asks for this, or when it runs on a schedule."
---
# Notion OKR progress
Every Monday: progress on each objective and key result in your Notion OKR database, set against how much of the quarter has passed.
OKRs in Notion usually start the quarter well kept and end it as a page nobody trusts. The fix is not a better template; it is someone looking every week and asking why a key result has not moved. Founders rarely have time to be that someone.
Each Monday the agent reads the key results database, rolls each objective up from its key results, and sets the result against the calendar: in week 8 of 13, a key result at 30% is behind however its owner marked it. Key results whose numbers nobody touched in two weeks are flagged as well.
## 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 Notion integration shared with the OKR database (and the objectives database, if objectives are a relation), its token in `NOTION_TOKEN`; or a Notion connector.
- The names of the quarter, objective, owner and progress (or current and target) properties.
If something is missing, say what and stop; do not invent numbers.
### Steps
1. **Query this quarter's key results** (Notion): Query the key results database through `POST /v1/data_sources/{data_source_id}/query` (API version `2025-09-03`; `POST /v1/databases/{database_id}/query` on `2022-06-28`), filtered to the quarter with `{"property": "Quarter", "select": {"equals": "2026 Q4"}}`. Read the title, the `Objective` relation, `Owner` (people), and `Current` and `Target` (numbers) or a single `Progress` number.
2. **Work out progress**: Progress is current divided by target, capped at 100%; for a formula or rollup column, read `formula.number` or `rollup.number` instead of `number`. Average the key results under each objective, grouping them by the relation's page IDs.
3. **Compare with the calendar**: Expected progress is the share of the quarter that has passed. A key result is on track at 90% of expected or more, at risk from 60%, and behind below that.
4. **Find stale numbers**: Flag key results whose page `last_edited_time` is more than 14 days old: the number may still be right, but nobody has checked it.
5. **Post the roll-up**: Headline: average progress across key results. Glance: one progress bar per objective and one for the quarter elapsed. Widget: every key result with owner, progress, status and when it was last updated.
## Route B: the browser
### What you need
- Signed in to Notion as a workspace member with access to the OKR database (and the objectives database when objectives are a relation).
If something is missing, say what and stop; do not invent numbers.
### Steps
Start at https://www.notion.so/. The user is signed in already; never type passwords or codes, and ask if a sign-in page appears.
1. **Open the key results database**: Open the key results database as a full page in a **Table** view and filter **Quarter** **Is** `2026 Q4`. Make sure the columns Objective, Owner, Current, Target (or Progress) and **Last edited time** are visible; add the last one through the view's **Properties** menu if it is hidden.
2. **Read every key result**: Note name, objective, owner, current and target (or the progress value). Progress is current over target, capped at 100%; a formula or rollup column already shows the percent.
3. **Roll up by objective**: Group the view by **Objective** and average the progress of the key results under each one.
4. **Compare with the calendar**: Expected progress is the share of the quarter that has passed. On track at 90% of expected or more, at risk from 60%, behind below that, for each key result and each objective.
5. **Flag stale numbers**: Any key result whose Last edited time is more than **14 days** ago goes on the stale list, whatever its progress.
6. **Write the roll-up**: Average progress across key results against the quarter elapsed, each objective with its status, then every key result with owner, progress, status and last update.
Note: Last edited time changes when anyone touches the page, including a comment, so a fresh timestamp does not prove the number was checked. Rollup columns shown as percent are already capped; a plain Current over Target column is not.
## The report
- **Average progress** across key results, against the share of the quarter that has passed.
- **Each objective**, rolled up from its key results and marked on track, at risk or behind.
- **Each key result** with owner, progress and status.
- **Stale**: key results not updated in 14 days.
## 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": "notion-okr-progress/<date of this run, e.g. 2026-10-16>",
"item_key": "notion-okr-progress",
"project": "Acme",
"source": "Notion OKR progress skill",
"kind": "metric",
"title": "OKRs at 47% in week 8 of 13, EU launch behind",
"metric": {
"label": "Average key result progress",
"value": 47,
"unit": "%",
"better": "higher",
"period_start": "<start of the period, ISO 8601>",
"period_end": "<end of the period, ISO 8601>"
},
"glance": [
{
"type": "Progress",
"props": {
"label": "Grow self-serve revenue",
"value": 64,
"text": "On track, 3 key results",
"tone": "ok"
}
},
{
"type": "Progress",
"props": {
"label": "Make onboarding faster",
"value": 48,
"text": "At risk, 3 key results",
"tone": "warn"
}
},
{
"type": "Progress",
"props": {
"label": "Launch the EU region",
"value": 28,
"text": "Behind, 3 key results",
"tone": "bad"
}
},
{
"type": "Progress",
"props": {
"label": "Quarter elapsed",
"value": 62,
"text": "Week 8 of 13",
"tone": "neutral"
}
}
],
"widget": [
{
"type": "Table",
"props": {
"columns": [
"Key result",
"Owner",
"Progress",
"Status",
"Updated"
],
"align": [
"left",
"left",
"right",
"left",
"right"
],
"rows": [
[
"Self-serve MRR to $180k",
"Dana",
"72%",
"On track",
"2 days ago"
],
[
"Trial to paid at 18%",
"Sam",
"65%",
"On track",
"6 days ago"
],
[
"Annual plan share to 35%",
"Dana",
"54%",
"At risk",
"9 days ago"
],
[
"Time to first project under 10 min",
"Lena",
"58%",
"On track",
"3 days ago"
],
[
"Checklist completion to 60%",
"Lena",
"49%",
"At risk",
"5 days ago"
],
[
"Tickets from new accounts down 30%",
"Aisha",
"38%",
"At risk",
"17 days ago"
],
[
"EU region live for new signups",
"Jonas",
"30%",
"Behind",
"4 days ago"
],
[
"20 customers migrated to EU",
"Marco",
"15%",
"Behind",
"21 days ago"
],
[
"SOC 2 scope extended to EU",
"Theo",
"40%",
"At risk",
"8 days ago"
]
]
}
},
{
"type": "Callout",
"props": {
"text": "Two key results have not been updated in over 14 days: new-account tickets (17 days) and EU migrations (21 days).",
"tone": "warn"
}
}
],
"size": "md"
}
JSON
```
Widgets come from the Briefkin catalog (https://briefkin.dev/v1/catalog). Without a token, just give the user the report.
Set `period_start` and `period_end` to the window the number covers: the tile names it from them ("Last 7 days", "Today", "This month"). For a count right now (open items, a balance), send `"period_label": ""` so no period shows; for another name, send it as `period_label` (at most 24 characters).
## Run it on a schedule
Suggested: Mondays at 11:00 (`0 11 * * 1`). From cron, with the agent signed in on that machine:
```bash
0 11 * * 1 claude -p "Run the notion-okr-progress 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/notion-okr-progress#schedule
Source: https://briefkin.dev/skills/notion-okr-progress
What your agent needs
A Notion integration shared with the OKR database (and the objectives database, if objectives are a relation), its token in
NOTION_TOKEN; or a Notion connector.The names of the quarter, objective, owner and progress (or current and target) properties.
Connecting Notion
- Notion MCP, Notion's hosted server at
https://mcp.notion.com/mcp. Add Notion from Claude's connector directory, or runclaude mcp add --transport http notion https://mcp.notion.com/mcp, and approve access with OAuth; it sees the pages your Notion account can see. - API with an internal integration. Create an internal integration in Notion's integration settings, store its secret (it starts with
ntn_) inNOTION_TOKEN, sendNotion-Version: 2025-09-03, and share each page or database with the integration from its ••• menu under Connections.
Give the integration only the Read content capability and share just the databases the report uses; Notion MCP acts as you and can edit, so it fits interactive work better than unattended runs.
Questions
What about a key result that should go down, like churn?
Give it a Start value as well as Target, and the skill measures progress as start minus current, divided by start minus target. A drop from 4% to 3% churn against a 2% target reads as 50%.
Does it handle key results that are checkboxes or milestones?
Yes. A checkbox counts as 0% or 100%. A milestone with sub-tasks in a relation counts the share of those tasks that are done, read through a rollup set to percent checked.
Do I need Briefkin to use the Notion OKR progress skill?
No. The skill runs with your own agent and gives you the report in the chat. With a Briefkin token set, each run also posts it to your board as a stat tile, so you can glance at it instead of asking again.
Which agents can run it?
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot CLI, OpenCode, Windsurf and Amp all read SKILL.md files. The install command puts it in ~/.claude/skills and ~/.agents/skills, where they look. ChatGPT, the Claude app and Grok take the prompt instead. Pick your agent under "Install and run it" and the commands change to match.
Can it work without an API or MCP server, from my browser?
Yes. Switch the data source to "Your browser" and the steps change to the Notion pages themselves: the agent opens www.notion.so in a browser you are signed in to and reads the numbers off the page. Claude Code, Codex, Cursor, Claude app and ChatGPT can drive a browser out of the box; Gemini CLI, Copilot CLI and OpenCode need a Playwright or Chrome DevTools MCP server first. It is slower than the API and needs you signed in, so it suits a report you run by hand or from a scheduler on your own computer.