Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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 agains
Passed 14 of 23 test cases with the skill, and 4 of 23 without it.
and 15 more in the full report
11 fixed3 passed either way8 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
Create the bottom footer for a GitHub briefing web page.
| Checked | Without skill | With skill |
|---|---|---|
| The footer text matches Open Orbit · auto-generated 06:42 · GitHub only | Missed | Passed |
| The footer font size is 12px | Missed | Passed |
The instructions your model reads when the skill loads.
Single-connector Orbit template scoped to GitHub.
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:
<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.
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.
example.html.This is a hard constraint: the briefing must read as a real GitHub
test cases passed, vs 4 / 23 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.