Agent skill

Notion Sync

Standardize Notion task updates across all modes. An agent skill from WellApp-ai/Well.

Install Notion Sync

skills CLI

$ npx skills add WellApp-ai/Well --skill notion-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install WellApp-ai/Well notion-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cursor-rules/skills/notion-sync .claude/skills/notion-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "notion-sync" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/notion-sync into .claude/skills/notion-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-sync", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/notion-sync

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add WellApp-ai/Well --skill notion-sync -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install WellApp-ai/Well notion-sync --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cursor-rules/skills/notion-sync .agents/skills/notion-sync && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "notion-sync" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/notion-sync into .agents/skills/notion-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-sync", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add WellApp-ai/Well --skill notion-sync -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install WellApp-ai/Well notion-sync --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cursor-rules/skills/notion-sync .cursor/skills/notion-sync && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "notion-sync" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/notion-sync into .cursor/skills/notion-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-sync", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/WellApp-ai/Well.git --path cursor-rules/skills/notion-sync

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add WellApp-ai/Well --skill notion-sync -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install WellApp-ai/Well notion-sync --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cursor-rules/skills/notion-sync .gemini/skills/notion-sync && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "notion-sync" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/notion-sync into .gemini/skills/notion-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-sync", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install WellApp-ai/Well notion-sync

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add WellApp-ai/Well --skill notion-sync -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .github/skills && cp -r skills-src/cursor-rules/skills/notion-sync .github/skills/notion-sync && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "notion-sync" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/notion-sync into .github/skills/notion-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-sync", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add WellApp-ai/Well --skill notion-sync -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install WellApp-ai/Well notion-sync --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/WellApp-ai/Well.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cursor-rules/skills/notion-sync .opencode/skills/notion-sync && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "notion-sync" agent skill from https://github.com/WellApp-ai/Well/tree/main/cursor-rules/skills/notion-sync into .opencode/skills/notion-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "notion-sync", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: notion-sync
GitHub stars: 345
Token cost: ~1.6k tokens
SKILL.md length: 366 words
Files: 1
Skills in repo: 36
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Standardize Notion task updates across all modes. An agent skill from WellApp-ai/Well.

Works in 4 steps: Retrieve Task Page → Update Standard Fields → Append Content (Optional) → …
Agent Workflows work in your project
SKILL.md covers When to Use, Phases, Phase 5: Session Journal Sync… and Output, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Notion Sync is an agent skill from WellApp-ai/Well. Standardize Notion task updates across all modes

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. It works with Notion and GitHub. The repository describes itself as: No more Sundays on Finance. We build the infrastructure that retrieves, processes, and routes your financial and business data to your FinOps stack, so founders can ship, not… The licence is MIT.

When your agent uses it

Agent Workflows work in your project

Example prompts

“/notion-sync”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Retrieve Task Page
Update Standard Fields
Append Content (Optional)
Confirm Sync

What it can do on your machine

Read from SKILL.md and the folder at commit c740217. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Notion Sync loads about 1.6k tokens when it runs. Until then it costs about 15 tokens; SKILL.md has 366 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~15
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from WellApp-ai/Well at commit c740217, republished under its MIT licence (© WellApp-ai). 366 words, ~1,553 tokens.

Download SKILL.mdSave it as .claude/skills/notion-sync/SKILL.md (or your agent's skills folder).

name: notion-sync
description: Standardize Notion task updates across all modes

Notion Sync Skill

Standardize how Notion tasks are updated across all modes.

When to Use

Push PR mode: update PR link and append plan
Init mode: update branch name
Any mode updating task status
Appending content to task pages

Phases

Phase 1: Retrieve Task Page

Fetch current task state:

API-retrieve-a-page:
  page_id: [task-page-id]

Verify the page exists and note current field values.

Phase 2: Update Standard Fields

Update properties based on context:

Available fields:

Field	Type	When to Update
Github PR link	url	On PR creation
Branch name	rich_text	On branch creation
Lifecycle/Status	select	On state changes

API call:

API-patch-page:
  page_id: [task-page-id]
  properties:
    "Github PR link": { url: "[PR-URL]" }
    "Branch name": { rich_text: [{ text: { content: "[branch-name]" }}]}

Phase 3: Append Content (Optional)

If content needs to be added to the page body:

Get existing blocks:

API-get-block-children:
  block_id: [page-id]

Append new content:

API-patch-block-children:
  block_id: [page-id]
  children: [
    {
      "type": "heading_2",
      "heading_2": { "rich_text": [{ "text": { "content": "Implementation Plan" }}]}
    },
    {
      "type": "paragraph",
      "paragraph": { "rich_text": [{ "text": { "content": "[plan-content]" }}]}
    }
  ]

Content types to append:

Implementation plans (from Plan mode)
PR summaries (from Push PR mode)
Status updates

Phase 4: Confirm Sync

Verify the update was successful:

API-retrieve-a-page:
  page_id: [task-page-id]

Check that updated fields reflect new values.

Phase 5: Session Journal Sync (NEW)

Sync session metrics and decisions to Session Journal database.

When to Run

After PR is created (via push-pr.mdc)
On manual "sync session" command
On session abandon

5.1: Gather Session Data

Collect from session-status skill:

Duration, loops, rework, waiting, RED count, escalations

Collect from decision-capture skill:

Decisions made this session (KO, significant OK)
Learnings captured (Kaizen/Hansei)

5.2: Check for Existing Session

Notion MCP: API-post-search
  query: "[branch-name]"
  filter:
    property: "object"
    value: "page"
  sort:
    property: "last_edited_time"
    direction: "descending"

Show full SKILL.md (151 more words)Show less

5.3: Create or Update Session Page

If new session:

Notion MCP: API-post-page
  parent: { database_id: "[SESSION_JOURNAL_DB_ID]" }
  properties:
    Title: { title: [{ text: { content: "[Feature] - [Date]" }}]}
    Task: { relation: [{ id: "[kanban_task_id]" }]}
    Date: { date: { start: "[session_date]" }}
    Duration: { number: [total_minutes] }
    Phase Reached: { select: { name: "[phase]" }}
    Outcome: { select: { name: "[outcome]" }}
    Loops: { number: [total_loops] }
    Rework: { number: [rework_count] }
    Waiting: { number: [waiting_minutes] }
    RED Count: { number: [red_count] }
    Escalations: { number: [escalation_count] }
    Branch: { rich_text: [{ text: { content: "[branch-name]" }}]}

If existing session:

Notion MCP: API-patch-page
  page_id: [existing_page_id]
  properties:
    Duration: { number: [updated_minutes] }
    Phase Reached: { select: { name: "[latest_phase]" }}
    Outcome: { select: { name: "[outcome]" }}
    Loops: { number: [updated_loops] }
    ... (other updated metrics)

5.4: Append Decisions and Learnings

Notion MCP: API-patch-block-children
  block_id: [session_page_id]
  children:
    - type: heading_2
      heading_2: { rich_text: [{ text: { content: "Decisions" }}]}
    - type: bulleted_list_item
      bulleted_list_item: { rich_text: [{ text: { content: "[KO] [decision 1] - [rationale]" }}]}
    - type: bulleted_list_item
      bulleted_list_item: { rich_text: [{ text: { content: "[OK] [decision 2] - [rationale]" }}]}
    - type: heading_2
      heading_2: { rich_text: [{ text: { content: "Learnings" }}]}
    - type: bulleted_list_item
      bulleted_list_item: { rich_text: [{ text: { content: "[Kaizen] [learning 1]" }}]}
    - type: bulleted_list_item
      bulleted_list_item: { rich_text: [{ text: { content: "[Hansei] [learning 2]" }}]}

5.5: Link to Kanban Task

Notion MCP: API-patch-page
  page_id: [kanban_task_id]
  properties:
    Session Journal: { relation: [{ id: "[session_page_id]" }]}

5.6: Create ADR for High-Impact Decisions

If any decision has Impact = HIGH:

Create ADR file in /docs/decisions/
Link ADR URL in Session Journal page

Session Journal Output

markdown

## Session Journal Synced

**Session:** [Feature] - [Date]
**Page:** [Notion URL]
**Kanban:** Linked to [Task name]

### Metrics Recorded
- Duration: [N]min
- Loops: [N]
- Rework: [N]
- RED Count: [N]
- Escalations: [N]

### Decisions: [N] captured
### Learnings: [N] captured
[If ADR: ADR-[NNN] created]

**Status:** Sync successful

Output

Present sync summary:

## Notion Sync Complete

**Task:** [task-title]
**Page ID:** [page-id]

### Updates Applied
- ✅ Github PR link: [url]
- ✅ Branch name: [branch]
- ✅ Content appended: [description]

**Status:** Sync successful

Standard Field Reference

Staffing Database ID: 256c4d5e-7bea-80ca-ba8d-c0ba0bb881c6

Common Properties:

Github PR link (url) - Link to GitHub PR
Branch name (rich_text) - Git branch name
Lifecycle or Status (select) - Task state
Assignee (people) - Task owner
Sprint (relation) - Sprint association

Integration

This skill is invoked by:

push-pr.mdc - Phase 2.2 (Sync Notion) + Phase 4 (Session Journal)
init.mdc - Update branch name
Any mode needing Notion updates
Manual "sync session" command

Notion MCP Tools:

API-retrieve-a-page - Get task details
API-get-block-children - Get page content
API-patch-page - Update page properties
API-patch-block-children - Add content to page
API-post-page - Create new session entries
API-post-search - Find existing sessions by branch

Files

Just SKILL.md in cursor-rules/skills/notion-sync of WellApp-ai/Well.

Open the folder on GitHubat commit c740217

Compare with similar skills

Notion Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Notion Sync compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Notion Sync this skillWellApp-ai/Well	345	—	~1.6k	Automated safety check: Pass	MIT	2 days ago
Superset Integration Toolssuperset-sh/superset	15k	—	~1.6k	Automated safety check: Warn	Custom licence	today
Adding MCP Store ServersPostHog/posthog	40k	—	~1.6k	Automated safety check: Pass	Custom licence	today
Integration Orchestratorrampstackco/claude-skills	941	—	~5.3k	Automated safety check: Pass	MIT	2 days ago
Integrate MCPdavekilleen/Dex	493	—	~2.2k	Automated safety check: Notes	MIT	today
Dev MCP Setupevolution-foundation/evo-nexus	545	—	~615	Automated safety check: Pass	Custom licence	4 mo ago

Similar skills

Superset Integration Tools
superset-sh/superset
Lists and calls the tools of connected integrations such as Linear, GitHub, Sentry or Notion through the superset mcp command, without storing a token on the machine.
15k GitHub stars~1.6k tokensUpdated today
Agent WorkflowsAuto-check: warnings
Adding MCP Store Servers
PostHog/posthog
Official
Add a third-party MCP server (Linear, Notion, GitHub, ...) to the PostHog MCP store catalog.
40k GitHub stars~1.6k tokensUpdated today
Agent WorkflowsAuto-check passed
Integration Orchestrator
rampstackco/claude-skills
Generate a phased delivery orchestration plan for creative-direction-driven work: which skills run when, what locks at which gate, how handoffs occur, and how the cadence implements in the team's…
941 GitHub stars~5.3k tokensUpdated 2 days ago
Agent WorkflowsAuto-check passed
Integrate MCP
davekilleen/Dex
Install and wire up an existing MCP server from Smithery.ai or a GitHub repo.
493 GitHub stars~2.2k tokensUpdated today
Agent WorkflowsAuto-check: notes
Dev MCP Setup
evolution-foundation/evo-nexus
Configure MCP servers for the workspace — web search, filesystem, GitHub, Stripe, etc.
545 GitHub stars~615 tokensUpdated 4 mo ago
Agent WorkflowsAuto-check passed
Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
30k GitHub starsUsed in 1 repo~1.7k tokens
Productivity & AutomationAuto-check passed

Questions about Notion Sync

What does Notion Sync do?

Standardize Notion task updates across all modes. An agent skill from WellApp-ai/Well. Notion Sync is an agent skill from WellApp-ai/Well.

When should I use Notion Sync?

Notion Sync fits situations like: agent Workflows work in your project.

How do I install Notion Sync in Claude Code?

Run `npx skills add WellApp-ai/Well --skill notion-sync -a claude-code`. Or copy the skill folder (cursor-rules/skills/notion-sync in WellApp-ai/Well) into .claude/skills/notion-sync in your project. Claude Code loads it when a task matches its description.

How do I install Notion Sync in Codex?

Run `npx skills add WellApp-ai/Well --skill notion-sync -a codex`. Or copy the skill folder (cursor-rules/skills/notion-sync in WellApp-ai/Well) into .agents/skills/notion-sync in your project. Codex loads it when a task matches its description.

Can I use Notion Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WellApp-ai/Well --skill notion-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/notion-sync, .gemini/skills/notion-sync, .github/skills/notion-sync and .opencode/skills/notion-sync in your project.

What does Notion Sync need to run?

SKILL.md names no scripts, command-line tools or credentials: Notion Sync is instructions for the agent only.

Does Notion Sync access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Notion Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Notion Sync use?

Notion Sync is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Notion Sync use?

About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Notion Sync?

Skills that share tags, products or a category with Notion Sync: Superset Integration Tools (superset-sh/superset, 15k stars), Adding MCP Store Servers (PostHog/posthog, 40k stars), Integration Orchestrator (rampstackco/claude-skills, 941 stars) and Integrate MCP (davekilleen/Dex, 493 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Notion Sync?

WellApp-ai (a GitHub organization) maintains it in WellApp-ai/Well, which has 345 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on October 7, 2026.

Source: WellApp-ai/Well on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Notion Sync

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Notion Sync Skill

When to Use

Phases

Phase 1: Retrieve Task Page

Phase 2: Update Standard Fields

Phase 3: Append Content (Optional)

Phase 4: Confirm Sync

Phase 5: Session Journal Sync (NEW)

When to Run

5.1: Gather Session Data

5.2: Check for Existing Session

5.3: Create or Update Session Page

5.4: Append Decisions and Learnings

5.5: Link to Kanban Task

5.6: Create ADR for High-Impact Decisions

Session Journal Output

Output

Standard Field Reference

Integration

Files

Compare with similar skills

Similar skills

More from WellApp-ai/Well

Related

Questions about Notion Sync