Agent skill · writing content · nexu-io
orbit-github
Open Orbit briefing skill — selected by the Orbit pipeline when GitHub is the user's only connected connector, or when the user explicitly scopes their daily digest to GitHub. Pulls the past 24 hours of PRs, review requests, issues, CI runs, and merges from the user's authenticated GitHub connection and renders them in a layout that mirrors GitHub's native Notifications + PR-diff visual language. This skill should not be triggered manually — it is invoked by Orbit's daily-digest scheduler against live GitHub data.
Why this skill is useful
Provides a specific template and design language for rendering GitHub notifications that the AI wouldn't generate on its own.
What it needs
Requires github account access. About 5k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
Orbit · GitHub Briefing Single-connector Orbit template scoped to GitHub. ⚠️ 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 nav-bar items (and only those) Same left-rail filter list (and only those) Same event groups in the same order, with the same row count Same diff-preview placement, same CI-fail block, same attention block Same <script> block at the end (filter / hover / link injection) Step 3. You may refresh mock values (PR numbers, titles, times, CI commit messages) so they read as "today", but you must not invent extra UI: no extra rail entries, no extra notifications, no extra event types, no extra badges, no extra chrome ornaments. If something is not already present 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, me, or my. 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 (GitHub's Primer 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/orbit-github