orbit-github
Best for daily standupsWorks with GitHubLow risk
⌘source
- author
@nexu-io- language
- TypeScript
★33kstars
3.7kforks
May 7, 2026
✦overview.md
Key Features
- ·Aggregates 24h of GitHub activity
- ·Renders PRs, review requests, issues, CI, merges
- ·Mirrors GitHub Notifications + PR-diff layout
- ·Triggered via daily-digest scheduler
- ·Single-connector GitHub template
Use Cases
- →Daily GitHub digest for a developer with only GitHub connected
- →Morning review of pending PRs and CI status
- →Scoped pull-request and issue summary for team leads
Best for
- ✓daily standups
- ✓GitHub-centric workflows
- ✓quick status overviews
Not ideal for
- !multi-platform digests
- !manual ad-hoc queries
- !non-GitHub users
FAQs
name
orbit-github
description
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.
triggers:["github briefing","github digest","pr digest","github 简报","代码活动汇总"]
od:{"mode":"prototype","platform":"desktop","scenario":"orbit","featured":2,"preview":{"type":"html","entry":"index.html"},"design_system":{"requires":false},"example_prompt":"Generate today's Open Orbit GitHub briefing. GitHub is my only connected connector — pull yesterday's PRs, review requests, issues, CI runs, and merges and render them as a GitHub Notifications + PR-diff page."}
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.
The sections below are a reference for tokens and visual language — not a license to extend the page.
⚠️ Design system policy
$install
1-click copynpx skills add nexu-io/open-design --skill orbit-githubSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
3/ 5
mediumPartially actionable with several concrete steps, but still missing important details.