Guide · Agent skill
How to use the Orbit Notion Briefing agent skill (orbit-notion)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The orbit-notion skill is a set of instructions that teaches an AI agent to write a daily briefing of the last 24 hours of your Notion activity. It covers document edits, comments, @mentions and database row changes, and formats the result to look like a native Notion page. This guide explains what a skill is, how to install this one, what it needs, and how to trigger it, so you can decide whether it fits your workflow.
Orbit Notion Briefingnexu-io/open-design · Apache-2.0 Download the skill Quick start
- 1Download the ZIP. Download the orbit-notion ZIP from this page.
- 2Unzip the skill. Unzip the archive so the folder contains SKILL.md and example.html.
- 3Place the folder. Move it to ~/.claude/skills/ for personal use or to .claude/skills/ in a project.
- 4Or upload it in the Claude apps. Go to Settings → Capabilities → Skills and upload the skill.
- 5Connect Notion. Make sure your Notion connection is authenticated through the Open Orbit connector.
- 6Run it through the scheduler. Let the Orbit daily-digest scheduler invoke the skill, since the skill is meant to run that way.
- 7Review the briefing. Check the generated digest for the documents, comments and database changes it lists.
What is an agent skill and what does orbit-notion do?
An agent skill is a folder with a SKILL.md file that tells an AI agent how to handle a specific kind of task. The agent reads the instructions when the task matches the skill's description or triggers.
orbit-notion is an Open Orbit briefing skill scoped to Notion. It pulls the past 24 hours of document edits, comments, mentions and database row changes from your authenticated Notion connection, then renders them as a digest. The skill ships with an example.html file that defines the layout, which the agent is told to reproduce rather than redesign.
- Document edits, shown as bullet rows with a snippet of the changed text
- Comments and @mentions, shown as comment cards
- Database row changes, shown in a database-style table with status tags
- A collapsed toggle for extra changes and a closing callout
Install the orbit-notion skill
Download the ZIP of the skill from this page and unzip it. You can install it in one of two places. For a personal install, put the unzipped folder in ~/.claude/skills/. For a single project, put it in that project's .claude/skills/ folder.
You can also upload the skill in the Claude apps. Open Settings, go to Capabilities, then Skills, and upload the skill there.
- Personal: ~/.claude/skills/
- Project: .claude/skills/ inside your project folder
- Claude apps: Settings → Capabilities → Skills
~/.claude/skills/orbit-notion/Connect Notion before you use it
The skill needs an authenticated Notion connection through the Open Orbit connector. It reads live data from that connection, so it cannot produce a briefing from a file on disk.
It is designed for setups where Notion is the only connected source. The source material says the skill is selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion.
- An authenticated Notion connection through the Open Orbit connector
- An Open Orbit daily-digest scheduler or pipeline
How to trigger the skill with natural requests
The skill lists trigger phrases in its description. These include 'notion briefing', 'notion digest', 'doc digest', 'notion 简报' and '文档摘要'. The example prompt in the skill is: Generate today's Open Orbit Notion briefing. Notion is my only connected connector, pull yesterday's document edits, comments, @ mentions, and database row changes and render the digest as a native Notion page.
Important: the skill's own description says it should not be triggered manually. It is meant to be invoked by Orbit's daily-digest scheduler against live Notion data. If you ask for a briefing in a chat without the scheduler, expect the agent may not use this skill as intended. Treat the phrases above as the scheduler's matching hints, not as a manual search tool.
- Try the phrases 'notion briefing' or 'notion digest' for a daily summary
- Use the example prompt above to see the expected scope
- Do not use it for ad hoc lookups; the skill says it is tied to the scheduler
What the output looks like and what to expect
The output follows the example.html structure: a page title with property chips, an italic synopsis line, and sections for document changes, comments and @mentions, and database changes. A callout invites you to follow up on unanswered comments, and a closing callout links back to the Open Design project.
The skill forces Notion's visual style. It says to ignore attached design systems and brand tokens, so the briefing will not look like your own brand. It also says to treat names in the example as mock content, and to use neutral wording such as 'you' when the current user's name is not explicit.
- Forced Notion colors, fonts and block styles
- Design systems and brand tokens attached to a project are ignored
- Example names are placeholders, not your identity
Safety notes: network access and scripts
The skill uses the network, because it reads your Notion data through the authenticated connection. It does not run scripts. Before you install it, be sure you are comfortable with an agent reading your Notion workspace, including edits, comments and mentions.
Because it reads private workspace data, limit the connection to the Notion content you actually want summarised, and review the output before sharing it.
- Uses network: yes, to read from your Notion connection
- Runs scripts: no
- Reads edits, comments and mentions from the authenticated account
What people use it for
- A daily summary of document edits in a team's Notion workspace
- A morning list of unanswered comments and @mentions
- A database-style table of row changes with status tags
- Evaluating how a templated briefing skill is structured, for designers or developers
Frequently asked questions
How do I install the orbit-notion skill?
Download the ZIP from this page and unzip it. Put the folder in ~/.claude/skills/ for personal use or in a project's .claude/skills/ folder, or upload it in the Claude apps under Settings → Capabilities → Skills.
What does the orbit-notion skill require?
It requires an authenticated Notion connection through the Open Orbit connector and an Open Orbit daily-digest scheduler or pipeline. It uses the network and does not run scripts.
Is the orbit-notion skill free?
The source material does not state pricing or licence terms beyond listing the licence as Apache-2.0. Check the licence file in the source before relying on it.
Why won't the skill run when I ask for a briefing in chat?
The skill's description says it should not be triggered manually and is invoked by Orbit's daily-digest scheduler against live Notion data. Manual requests may not use it as intended.
Can I use my own brand colours and fonts with this skill?
No. The skill forces Notion's visual style and says to ignore attached design systems and brand tokens.
What are alternatives if I want an on-demand Notion search?
This skill is not built for manual, on-demand search. The source does not name specific alternatives, so look for a tool designed for that purpose.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use orbit-notion if you use Notion as your only connected source in the Open Orbit pipeline and want a scheduled daily digest in Notion's visual style. Pick something else if you want a manual Notion search, a custom brand look, or if you are not comfortable with an agent reading your workspace's edits, comments and mentions.
Download the skill