nexu-io/open-design

orbit-gmail

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 schedu

74Collecting
See how to use itView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/orbit-gmail"
Automated source guideDesignDeep source

Source checked Jul 28, 2026·Refresh due Oct 26, 2026

Reorganized from the pinned upstream SKILL.md

Source-grounded design guide: orbit-gmail

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, an…

npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/orbit-gmail"
Check the pinned source

The pinned source contains enough sections and task detail for a source-grounded deep guide; automated content is still not an independent test.

820 source words · 6 usable sections

Design process

Read orbit-gmail through these 5 source sections

Sections are extracted automatically from the pinned SKILL.md and link back to the source.

01

Implementation constraints (paired do / don't)

Review the “Implementation constraints (paired do / don't)” section in the pinned source before continuing.

SKILL.md · Implementation constraints (paired do / don't)
Review and apply the “Implementation constraints (paired do / don't)” source section.
02

⚠️ 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.

SKILL.md · ⚠️ Source-of-truth protocol (read this first)
Same DOM hierarchy and class names: (Gmail top bar) →The Gmail top header has only the elements present in the exampleDo not render an inbox list of other emails. Only the opened
03

⚠️ 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.

SKILL.md · ⚠️ Design system policy
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.
04

Canvas tokens (use these exact values)

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

SKILL.md · Canvas tokens (use these exact values)
'Google Sans', 'Roboto', -apple-system, system-ui, sans-serifLogo wordmark: Google Sans 22px mediumBody: 14px / line-height 20px
05

Page sections (top to bottom — the page is one column, not a 3-pane app)

1. Gmail top header () — full width, white. 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.

SKILL.md · Page sections (top to bottom — the page is one column, not a 3-pane app)
Gmail top header () — full width, white.Email chrome ( )greeting paragraph

SkillSignal prompt templates

Provide the task, context, and acceptance criteria

These prompts were written by SkillSignal from the source structure; they are not upstream text.

Source-grounded prompt

Use for a design task while explicitly checking the source sections.

Use orbit-gmail for this design task: [task]. Inputs and constraints: [details]. Work through these pinned SKILL.md sections: “Implementation constraints (paired do / don't)”, “⚠️ Source-of-truth protocol (read this first)”, “⚠️ Design system policy”, “Canvas tokens (use these exact values)”, “Page sections (top to bottom — the page is one column, not a 3-pane app)”. Cite the concrete requirements that shape each step, do not invent capabilities absent from the source, and verify the result against: [acceptance criteria].

Design checklist

Verify each item before delivery

The source section “Implementation constraints (paired do / don't)” has been checked.

The source section “⚠️ Source-of-truth protocol (read this first)” has been checked.

The source section “⚠️ Design system policy” has been checked.

The source section “Canvas tokens (use these exact values)” has been checked.

Choose a different workflow

When another Skill is the better fit

orbit-gmail

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 schedu

A separate implementation from nexu-io/open-design; compare its source, maintenance signals, and permission requirements.

Open source detail

ab-testing

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

churn-prevention

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

A separate implementation from coreyhaines31/marketingskills; compare its source, maintenance signals, and permission requirements.

Open source detail

FAQ

What does the orbit-gmail source document cover?

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, an…

How do I install orbit-gmail?

The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/examples/orbit-gmail". Inspect the command and pinned source before running it.

Repository stars
82,073
Repository forks
9,485
Quality
74/100
Source repository last pushed

Quality breakdown

Based on traceable docs and repository signals; stars are not treated as quality.

74/100
Documentation26/30
Specificity11/25
Maintenance20/20
Trust signals17/25

Compare before choosing

Related Agent Skills and source variants

These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.

orbit-gmail by nexu-io

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 schedu

ab-testing by coreyhaines31

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program

churn-prevention by coreyhaines31

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers o

design-intelligence by event4u-app

Grounded design brief from the adopted corpus — style, WCAG-checked color tokens, typography, layout pattern, anti-patterns. Use on ui-design-brief or any which-style/palette/font/chart decision.

design-system-capture by event4u-app

Write and maintain DESIGN.md + PRODUCT.md — captures visual decisions and interaction patterns so design tasks stay consistent across sessions without re-scanning past work.

View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 5 min

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:

  • Same DOM hierarchy and class names: <header> (Gmail top bar) → <main class="digest-wrap"><div class="email-chrome"> → toolbar / subject / sender row / digest body / reply bar.
  • The Gmail top header has only the elements present in the example (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).
  • Do not render an inbox list of other emails. Only the opened digest email is shown.
  • Same digest-body sections in the same order: greeting → summary strip → 需要处理 → 值得关注 → 仅供知悉 → digest footer.
  • Same reply bar at the bottom (回复 / 全部回复 / 转发).
  • Same <script> block at the end (action-btn / reply-btn link injection).

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.

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)

  1. Gmail top header (<header>) — full width, white. 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.

  2. Email chrome (<main class="digest-wrap"> <div class="email-chrome">) — the opened email lives directly under the header. No left rail, no inbox list. Sub-blocks in order:

    a. Email toolbar — back / archive / delete / mark unread / label / spacer / prev / next.

    b. Email subject area<h1 class="email-subject"> with the digest subject (e.g. ☀ Eli, 你昨天的 6 封重要邮件 — Open Orbit Daily) followed by an inline Orbit tag.

    c. Sender row — round avatar O + Open Orbit <orbit@opendesign.local> + 收件人 我 ▾ + date right-aligned + reply icon + more icon.

    d. Digest body (<div class="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

  • Avatars: round, 40px+ for sender, 32px for card, 28px for inline.
  • Labels / tags: small rounded pills with no fill (dot + text) only where they appear in the example.
  • The single yellow important star (in the subject area or as a tag) belongs to the Orbit digest only.

Implementation constraints (paired do / don't)

Don'tDo
Render a left rail (Compose / system labels / colored labels)Skip the rail entirely; the page is single-column under the header
Render an inbox list of other emailsShow only the opened Orbit Daily Digest email
Render a Categories tab strip (主要 / 社交 / 推广)Skip it; the digest occupies the reading view directly
Use non-Google typographyUse 'Google Sans', 'Roboto', -apple-system, system-ui, sans-serif
Add drop shadows on the Gmail chromeFlat surfaces; only the subtle Material 1 elevation when an element is focused
Render avatars as squaresAlways circles — sender 40px, card 32px, inline 28px
Use lorem ipsumWrite real-shaped Gmail copy: "Q3 预算确认", "Login redesign 反馈", senders like Allen Liu / Marie / Nina Park
Use dark modeStay on Gmail's default light theme (#f6f8fc page)
Brand the Gmail chrome with OrbitOrbit branding lives only inside the digest body (subject Orbit tag + footer micro-tag)
Put yellow important stars on multiple inbox rowsOnly the Orbit Daily Digest row can carry the important marker
Skill path
plugins/_official/examples/orbit-gmail/SKILL.md
Commit SHA
89d6d4ef21ba
Repository license
Apache-2.0
Data collected