orbit-gmail skill
Open Orbit briefing skill — selected by the Orbit pipeline when Gmail is the user's only connected connector, or when the user explicitly scopes their daily digest to Gmail. Pulls the past 24 hours of inbox activity (replies awaited, mentions, cc, auto- categorized bulk) from the user's authenticated Gmail connection and renders the digest as the Orbit Daily Digest email opened inside Gmail's reading view. This skill should not be triggered manually — it is invoked by Orbit's daily-digest scheduler against live Gmail data.
Is the orbit-gmail skill safe?
Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.
No findings.
Install the orbit-gmail skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/nexu-io/open-design.git /tmp/open-design mkdir -p ~/.claude/skills cp -r /tmp/open-design/design-templates/orbit-gmail ~/.claude/skills/orbit-gmail
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
Orbit · Gmail Briefing
Single-connector Orbit template scoped to Gmail. The briefing renders as the Orbit Daily Digest email already opened inside Gmail's reading view — Gmail top header + the email chrome (toolbar / subject / sender / digest body / reply bar). There is no left rail, no inbox list, and no three-pane layout.
⚠️ 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:
→ → toolbar / subject / sender row / digest body / reply bar.
- Same DOM hierarchy and class names: (Gmail top bar) →
(hamburger / wordmark / search bar / help / settings / app launcher / avatar). Do not add a left rail (no Compose button, no system labels, no Categories tabs, no colored label list).
- The Gmail top header has only the elements present in the example
digest email is shown.
- Do not render an inbox list of other emails. Only the opened
strip → 需要处理 → 值得关注 → 仅供知悉 → digest footer.
- Same digest-body sections in the same order: greeting → summary
injection).
- Same reply bar at the bottom (回复 / 全部回复 / 转发).
- Same block at the end (action-btn / reply-btn link
Step 3. You may refresh mock copy (sender names, subjects, summary text, times) so it reads as "today", but you must not invent extra UI: no inbox listing, no left rail, no Categories tab strip, no extra digest sections, no chrome ornaments. If a detail is not already in example.html, 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 sections below are a reference for tokens and visual language — not a license to extend the page.
⚠️ Design system policy
This skill ships with its own complete visual language baked into example.html (Gmail / Google Sans / Material chrome). 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 defined in example.html.
This is a hard constraint: the briefing must read as a real Gmail page, not as the user's brand.
Canvas tokens (use these exact values)
page bg: #f6f8fc
surface: #ffffff
border: #e0e0e0
text: #202124
text-secondary: #5f6368
text-muted: #80868b
surface-hover: #f1f3f4
red (Gmail): #D93025 /* Compose, important markers, accent */
blue: #1a73e8 /* CTA / link */
yellow: #f4b400 /* important ★ */
green: #0f9d58
search bar bg: #eaf1fb /* light blue-tinted pill */Type stack:
- 'Google Sans', 'Roboto', -apple-system, system-ui, sans-serif
- Logo wordmark: Google Sans 22px medium
- Body: 14px / line-height 20px
- Email preview: 13px
Page sections (top to bottom — the page is one column, not a 3-pane app)
Left: hamburger (☰) + Gmail wordmark (Gmail, first G red). Center: rounded search bar (#eaf1fb bg, search icon left, settings icon right, placeholder 搜索邮件). Right: ❓ help, ⚙ settings, ▦ Google apps launcher, round avatar.
- Gmail top header () — full width, white.
— the opened email lives directly under the header. No left rail, no inbox list. Sub-blocks in order:
- Email chrome ( )
a. Email toolbar — back / archive / delete / mark unread / label / spacer / prev / next.
b. Email subject area — with the digest subject (e.g. ☀ 你昨天的 6 封重要邮件 — Open Orbit Daily) followed by an inline Orbit tag.
c. Sender row — round avatar O + Open Orbit + 收件人 我 ▾ + date right-aligned + reply icon + more icon.
d. Digest body ():
- greeting paragraph
- summary strip — 3 numeric cells (urgent / 值得关注 / 仅供知悉)
- section 🔴 需要处理 — cards with action-btn primary
- section 🟡 值得关注 — cards with action-btn ghost
- section ⚪ 仅供知悉 — cards
- digest-footer micro-tag
e. Reply bar — bottom row with 回复 / 全部回复 / 转发 buttons.
Pill / icon rules
where they appear in the example.
- Avatars: round, 40px+ for sender, 32px for card, 28px for inline.
- Labels / tags: small rounded pills with no fill (dot + text) only
belongs to the Orbit digest only.
- The single yellow important star (in the subject area or as a tag)
Implementation constraints (paired do / don't)
More skills from nexu-io/open-design
- Aarticle-magazineHuashu / huashu-md-html-inspired magazine article layout for turning Markdown or notes into a polished long-form HTML essay.
- Aaudio-jingleAudio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.
- Aaudio-jingleAudio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.
- Ablog-postA long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
- Ablog-postA long-form article / blog post — masthead, hero image placeholder, article body with figures and pull quotes, author byline, related posts. Use when the brief asks for "blog", "article", "post", "essay", or "case study".
- Abuild-testRun the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
- Acard-twitterTwitter quote or data card designed to pair with a post.
- Acard-xiaohongshuXiaohongshu-style knowledge cards, arranged as a swipeable multi-card carousel.
- Aclinical-case-reportStructured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", or "patient presentation".
- Aclinical-case-reportStructured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds", "case summary", or "patient presentation".
- Acode-importRead an existing repository's structure into the project cwd as a normalised snapshot the agent can analyse without re-walking the tree on every turn.
- Acodex-interactive-capability-mapTurn a long-form article, thread, memo, or product narrative into a compact clickable capability map with a workflow loop, use-case matrix, and responsive detail panel.