Skip to content
Skillpedia
Automations101k · #488

orbit-github

Has your agent create a daily summary focused on GitHub activities. It shows pull requests, issues, and other updates. It's useful for developers to track their work on GitHub.

What it does

This tool organizes your GitHub notifications into a daily summary. It shows recent updates like review requests, open issues, and code changes.

When to use it

  • ✓When you want to know what happened on GitHub in the last day.
  • ✓To quickly see review requests needing your attention.
  • ✓To keep up with updates from projects you follow.

Example of what to ask your AI

“Show me a summary of my GitHub activity today.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/nexu-io/open-design/blob/main/design-templates/orbit-github/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/nexu-io/open-design/blob/main/design-templates/orbit-github/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool connects to your GitHub account and fetches the latest information. It then organizes this data similarly to GitHub's native notification page for easy viewing.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add nexu-io/open-design --skill orbit-github

Or download just the file:

curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/design-templates/orbit-github/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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.

This is a hard constraint: the briefing must read as a real GitHub page, not as the user's brand.

Canvas tokens (use these exact values)

page bg:           #f6f8fa
card bg:           #ffffff
nav bar:           #24292f  /* GitHub black header */
nav text:          #ffffff
ink:               #1f2328
muted:             #59636e
border:            #d0d7de
hairline:          rgba(208,215,222,0.32)

state · open:      #1a7f37
state · merged:    #8250df
state · closed:    #cf222e
state · draft:     #6e7781

attention bg:      #fff8c5  /* yellow review-request block */
attention border:  #d4a72c
ci-fail bg:        #ffebe9
ci-fail border:    #cf222e

Type stack:

  • -apple-system, BlinkMacSystemFont, "Segoe UI", "Noto Sans", Helvetica, Arial, sans-serif
  • Sizes: nav 14px, headings 16/20px, body 14px, meta 12px

Page sections

  1. Top nav bar — full-width, dark (#24292f), 60px tall. Left: octocat SVG logo (white, 32px) + search input (rgba(255,255,255,0.08) background, white placeholder ghosted). Right: + plus dropdown, notifications bell with red dot if unread > 0, round avatar.

  2. Header row — light bar under the nav, 56px. Left: page breadcrumb Inbox · Daily Digest · May 6. Right: filter dropdown chips (Type ▾ Date ▾ Status ▾).

  3. Two-pane main:

    • Left rail (240px): vertical filter list. Items: Inbox · Saved · Done · All then divider then Participating · Mentions · Review requests · Assigned · Comments. Active item: light gray pill background.
    • Main pane (flex 1): event stream grouped by category.
  4. Category groups in main pane (in this order):

    • Review requests waiting on you — yellow attention block (bg #fff8c5, 1px border #d4a72c). Each row: avatar + repo path + PR title + reviewer-state row of small dots (✓ green / ⏳ yellow / ○ gray) + "X of Y reviewers" + age.
    • CI / Checks — each failed run is a red-bordered card (border-color #cf222e, bg #ffebe9) with a ✗ red glyph, run name, branch name (mono), commit message, age.
    • Issues assigned to you — plain rows, status circle (open green / closed red), title, repo path, age, label pills.
    • Activity — quieter rows for merges/closes; muted text, small merged purple pill or closed red pill.
  5. Optional PR-diff preview — inline under one PR row, show

…

FAQ

What does 'connector' mean?

A connector is a way for the AI to link to other services, like GitHub, to retrieve information.

Can I see notifications from services other than GitHub?

No, this tool is specifically set up to only show information from GitHub.

Will the tool change how my GitHub looks?

No, it only organizes the information for you. Your GitHub's appearance will remain unchanged.

Details

Original description by the author

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.

repo: nexu-io/open-design

Popularity

GitHub stars
101k
Ranking position
#488
License
Apache-2.0
Updated
10/16/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills