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.
npx skills add nexu-io/open-design --skill orbit-github --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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, connect
- ⚠️ Source-of-truth protocol (read this first)
- ⚠️ Design system policy
- Canvas tokens (use these exact values)
- Page sections
- Pill / chip rules
- Implementation constraints (paired do / don't)
What does the orbit-github skill do?
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.
How do I install it?
Run `npx skills add nexu-io/open-design --skill orbit-github --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From nexu-io/open-design, a repository with 83,577 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.