orbit-notion
Best for Notion-only usersWorks with GitHubLow risk
⌘source
- author
@nexu-io- language
- TypeScript
★33kstars
3.7kforks
May 7, 2026
✦overview.md
Key Features
- ·Pulls 24h Notion activity
- ·Renders as native Notion page
- ·Uses callout, toggle, database table
- ·Single-connector Orbit template
Use Cases
- →Daily digest of Notion changes for users with only Notion connected
- →Scoped daily briefing when user explicitly filters to Notion
Best for
- ✓Notion-only users
- ✓daily activity summaries
Not ideal for
- !multi-connector setups
- !manual triggering
FAQs
name
orbit-notion
description
Open Orbit briefing skill — 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. Pulls the past 24
hours of document edits, comments, mentions, and database row changes
from the user's authenticated Notion connection and renders the
digest as a native Notion page (callout / toggle / database table
primitives). This skill should not be triggered manually — it is
invoked by Orbit's daily-digest scheduler against live Notion data.
triggers:["notion briefing","notion digest","doc digest","notion 简报","文档摘要"]
od:{"mode":"prototype","platform":"desktop","scenario":"orbit","featured":5,"preview":{"type":"html","entry":"index.html"},"design_system":{"requires":false},"example_prompt":"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."}
Orbit · Notion Briefing
Single-connector Orbit template scoped to Notion. The briefing renders as a real Notion page — same chrome, same block primitives, same typography.
⚠️ Source-of-truth protocol (read this first)
Step 1. Open and read the shipped example.html in this folder
before writing any output. That file is the canonical design — your
job is to reproduce it, not reinterpret it.
Step 2. Mirror the example's structure 1:1:
- Same DOM hierarchy and class names
- Same H2 sections in the same order (文档变更 → 评论 / @ 提及 → 数据库变更)
- Same bullet rows / comment cards / database table columns and rows
- Same callout(s) and toggle block with the same copy
- Same property chips at the top (Type / Owner / Created)
- Same
<script>block at the end (page-link → notion.so injection)
Step 3. You may refresh mock values (doc titles, mentioned people,
edit timestamps) so they read as "today", but you must not
invent extra blocks: no extra H2 sections, no extra callouts, no
extra database columns, no extra emoji decorations. If a detail is
not in example.html, it does not belong in your output.
$install
1-click copynpx skills add nexu-io/open-design --skill orbit-notionSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.