orbit-general
Helps your agent create a dashboard of recent activity from various connected tools. It shows a summary of what happened in the last 24 hours. It's useful for getting an overview of work in one place.
What it does
This feature gathers information from your connected tools (like GitHub, Slack, Google Calendar) from the past 24 hours. It presents everything in an organized visual dashboard, like a summary of your day.
When to use it
- ✓At the start of your workday to see what happened.
- ✓To get a quick overview of pending items and important activities.
- ✓When you want to know the status of projects or tasks across different platforms.
Example of what to ask your AI
“Show me a summary of my activities from the last 24 hours across all my connected tools.”
Want more? Open the sections below.
How to use
The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.
Skill link
Ready-to-paste message
How it works
It connects to your accounts (like GitHub, Google Calendar, Slack) and collects the latest information. Then, it organizes everything into a visual dashboard, highlighting the most important points from each tool.
Installation
Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.
In the terminal (Claude Code, Codex, Cursor), in your project folder:
npx skills add nexu-io/open-design --skill orbit-generalOr download just the file:
curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/design-templates/orbit-general/SKILL.md -o SKILL.mdTechnical content (original SKILL.md)
Original text by the author, straight from GitHub.
Orbit General Briefing
Cross-connector morning briefing that lives at the top of "我的设计". Pulls the past 24 hours of activity from every authenticated connector and lays them out as one editorial bento dashboard.
⚠️ 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 number and order of sections
- Same number of bento modules in the same order
- Same connector list (do not add or drop connectors)
- Same KPI labels, same Top 3 entries, same "people waiting" set
- Same footer string
- Same
<script>block at the end (link injection)
Step 3. You may freshen mock data values (counts, names, times) so
they read as "today" — but you must not invent new UI elements,
sections, modules, badges, callouts, ribbons, banners, decorations or
chrome that aren't already in example.html. If a detail is not in
the example, it does not belong in your output.
Identity guard. Treat every person name or handle in example.html
as mock content only. Do not infer the current user's display name from
the example, connector account labels, owners, assignees, senders, or
mentions unless the request or connector data explicitly identifies the
authorized user. If no explicit current-user name is available, use
neutral wording such as you, your, current user, 我, or 你.
The body sections below are a reference for the visual language and tokens — they are not a license to add features the example doesn't already render.
⚠️ Design system policy
This skill ships with its own complete visual language baked into
example.html. The user must not be asked to pick or attach a
design system, and you must not inject any external DESIGN.md
tokens into the output.
- If the active project has a design system attached, ignore it.
- If the user supplies brand tokens or a Figma file, ignore them.
- Use exclusively the colors / fonts / radii / chrome defined in
example.html.
This is a hard constraint: an Orbit briefing must read as Open Orbit's own editorial bento language, not as the user's brand.
Canvas tokens (use these exact values)
--bg: #FAF7F2 /* off-white page */
--surface: #FFFFFF /* card */
--fg: #1A1816 /* ink */
--muted: #6B6660 /* secondary text */
--border: #EAE5DD /* 1px hairline only */
--orange: #D86A47 /* accent (CTAs, hero highlight, meeting blocks) */
--green: #2E7D5B /* ok / done */
--yellow: #C9982E /* waiting */
--red: #C0473A /* alert / fail */
--radius-l: 24px /* outer container */
--radius-m: 16px /* bento cards */
--radius-s: 12px /* inner blocks */
Type stack:
- Display serif:
'Cormorant', Georgia, serif— KPI numerals, Hero h1, Top 3 serial numbers, italic comment quotes - Body sans:
'Inter', -apple-system, system-ui, sans-serif - Numbers: always
font-variant-numeric: tabular-nums
No shadows. No gradients. No emoji as primary visuals. Connector icons must be monochrome line SVG (1.5 stroke).
Page sections (top to bottom)
Hero — single row, ~80px tall. Left:
☀ 你好(Cormorant 38px). Right of greeting:· 2026 年 5 月 6 日 · 星期三(muted, 18px). Far right: round avatar (40px) + small ⚙ + ✕ icons.KPI strip — single row, ~120px tall, 5 columns equal width. Each cell: serif number (Cormorant 64px,
--fg) over a muted uppercase tracking label (Inter 11px, letter-spacing 0.06em). Optional ▲/▼ delta tag in--green/--rednext to the number. Suggested labels:待办 / 待 review / 会议 / @ 我 / agent 跑完.Today's timeline — full width, ~140px tall. Horizontal time axis from 09:00 → 19:00, hour ticks below. Meeting blocks: filled
--orangerounded rectangles spanning their start/end, with the meeting name + attendee count inside. Deep-work suggestions: pale-green translucent bands behind the axis. "Now" indicator: a 1px vertical--redline with a pulsing dot (@keyframes pulse 2s ease-in-out infinite) and a tiny现在label.Top 3 — 3 equal cards, ~220px tall. Each card: huge serif numeral 1 / 2 / 3 (Cormorant 96px, in
--fg) left-aligned; one-sentence task headline (Inter 18px medium); a
…
FAQ
What tools can it connect to?
It can connect to various tools like GitHub, Linear, Notion, Slack, Google Calendar, Gmail, Drive, Sentry, Vercel, and others.
How far back does it show information?
It shows activities from the past 24 hours.
Can I customize the appearance?
No, the appearance is fixed and follows a defined pattern to ensure consistency. It uses its own visual style called 'Open Orbit's own editorial bento language'.
Details
Original description by the author
Open Orbit briefing skill — selected by the Orbit pipeline when the user has two or more connectors connected. Pulls the past 24 hours of activity from every authenticated connector (GitHub, Linear, Notion, Slack, 飞书, Calendar, Gmail, Drive, Sentry, Vercel, …) and renders a single adaptive bento-grid dashboard at the top of "我的设计". Each connector module picks its own UI form (list, avatar stack, s
repo: nexu-io/open-design
Popularity
- GitHub stars
- 101k
- Ranking position
- #487
- License
- Apache-2.0
- Updated
- 10/16/2026
Comments
- …
More skills from this repository
sample-plugin
Makes your agent create a metadata file for tests. It helps ensure code works correctly in different situations.
nexu-io/open-design
aster-atelier
Helps your agent create an artistic website with a classic look. It uses elegant imagery, blue skies, and serif fonts for a cinematic feel.
nexu-io/open-design
audio-jingle
Makes your agent generate audio like jingles and sound effects. It can create music and voices, saving the result as an audio file.
nexu-io/open-design
blog-post
Helps your agent write long articles or blog posts. It includes space for images, quotes, and author information.
nexu-io/open-design
Similar skills
benchmark
Helps your agent measure code speed and performance. It's useful for ensuring things are fast and finding slowness issues.
affaan-m/ECC
content-hash-cache-pattern
Lets your agent use content hashes to cache file processing results. This avoids repeated processing and auto-invalidates the cache when content changes. Useful for speeding up slow tasks.
affaan-m/ECC
parallel-execution-optimizer
Makes your agent speed up complex tasks by breaking them into smaller parts and running them in parallel. It ensures everything is verified at the end.
affaan-m/ECC