orbit-linear
Open Orbit briefing skill — selected by the Orbit pipeline when Linear is the user's only connected connector, or when the user explicitly scopes their daily digest to Linear. Pulls the past 24 hours of issue movement, status changes, assignments, and cycle progress from the user's authenticated Linear connection and renders the digest in Linear's native Inbox + cycle-progress visual language. This skill should not be triggered manually — it is invoked by Orbit's daily-digest scheduler against live Linear data.
Profile →npx skills add nexu-io/open-design --skill orbit-linear --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 · Linear Briefing Single-connector Orbit template scoped to Linear. ## ⚠️ 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 top toolbar (breadcrumb + view switcher + cycle strip + theme toggle), exactly those items - Same left-rail entries in the same order - Same issue groups ("Needs your attention" → "Updated yesterday") with the same row count and same expanded-by-default behavior - Same priority-bar / status-dot system - Same `<script>` block at the end (toggle / theme / keyboard / Linear link injection) **Step 3.** You may refresh mock values (issue identifiers, titles, labels, ages, assignees) so they read as "today", but you must **not** add extra rail entries, extra groups, extra fields in the preview pane, or any chrome ornaments not already in `example.html`. **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
- ⚠️ Source-of-truth protocol (read this first)
- ⚠️ Design system policy
- Canvas tokens — light theme (default to ship)
- Page sections
- Identifier / chip rules
- Implementation constraints (paired do / don't)
What does the orbit-linear skill do?
Open Orbit briefing skill — selected by the Orbit pipeline when Linear is the user's only connected connector, or when the user explicitly scopes their daily digest to Linear. Pulls the past 24 hours of issue movement, status changes, assignments, and cycle progress from the user's authenticated Linear connection and renders the digest in Linear's native Inbox + cycle-progress visual language. This skill should not be triggered manually — it is invoked by Orbit's daily-digest scheduler against live Linear data.
How do I install it?
Run `npx skills add nexu-io/open-design --skill orbit-linear --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.