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.
Install / Use
npx skills add nexu-io/open-design --skill orbit-gmailInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Tags
Our assessment of orbit-gmail
orbit-gmail scores 90/100 on our quality scale, 153rd of 1,003 Automation skills we index (top 16%).
Its SKILL.md is 7.3 KB long, split into 7 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 97,896 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated today, so orbit-gmail is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit ā read the skill file before letting an agent act on it.
orbit-gmail compared with similar skills
All 4 of these similar skills score higher than orbit-gmail; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| orbit-gmail (this skill)by nexu-io | 90 | 97.9k | today | SKILL.md |
| Agent-Reachby Panniantong | 100 | 85.3k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 73.2k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 83.4k | today | MCP Server |
| algorithmic-artby anthropics | 100 | 177.9k | 2d ago | SKILL.md |
Frequently asked questions
- How do I install orbit-gmail?
- Run
npx skills add nexu-io/open-design --skill orbit-gmail. The install tabs above show the steps for each supported agent. - Which AI agents does orbit-gmail work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is orbit-gmail safe to use?
- It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is orbit-gmail still maintained?
- The repository was last updated today, so orbit-gmail is actively maintained.
Skill content
View source on GitHubname: orbit-gmail description: | 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. triggers:
- "gmail briefing"
- "inbox digest"
- "email summary"
- "gmail ē®ę„"
- "é®ä»¶ęč¦" od: mode: prototype platform: desktop scenario: orbit preview: type: html entry: index.html design_system: requires: false example_prompt: "Generate today's Open Orbit Gmail briefing. Gmail is my only connected connector ā pull yesterday's mail and render it as the opened Orbit Daily Digest email inside Gmail's reading view."
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.
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)
-
Gmail top header (
<header>) ā full width, white. Left: hamburger (ā°) + Gmail wordmark (Gmail, firstGred). Center: rounded search bar (#eaf1fbbg, search icon left, settings icon right, placeholderęē“¢é®ä»¶). Right: ā help, ā settings, ⦠Google apps launcher, round avatar. -
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.ā ä½ ęØå¤©ē 6 å°éč¦é®ä»¶ ā Open Orbit Daily) followed by an inlineOrbittag.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-footermicro-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't | Do |
|---|---|
| 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 emails | Show only the opened Orbit Daily Digest email |
| Render a Categories tab strip (äø»č¦ / 社交 / ęØå¹æ) | Skip it; the digest occupies the reading view directly |
| Use non-Google typography | Use 'Google Sans', 'Roboto', -apple-system, system-ui, sans-serif |
| Add drop shadows on the Gmail chrome | Flat surfaces; only the subtle Material 1 elevation when an element is focused |
| Render avatars as squares | Always circles ā sender 40px, card 32px, inline 28px |
| Use lorem ipsum | Write real-shaped Gmail copy: "Q3 é¢ē®ē”®č®¤", "Login redesign åé¦", senders like Allen Liu / Marie / Nina Park |
| Use dark mode | Stay on Gmail's default light theme (#f6f8fc page) |
| Brand the Gmail chrome with Orbit | Orbit branding lives only inside the digest body (subject Orbit tag + footer micro-tag) |
| Put yellow important stars on multiple inbox rows | Only the Orbit Daily Digest row can carry the important marker |
Related Skills
Agent-Reach
85.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu ā one CLI, zero API fees.
ruflo
73.2kš The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Scrapling
83.4kš·ļø An adaptive Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit ā see the Safety scan above for what the skill file itself contains.
