Agent skill · design visual · nexu-io
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.
Why this skill is useful
Provides a specific implementation guide for rendering Linear's UI components and visual language that the AI wouldn't reliably generate on its own.
What it needs
Requires linear account access. About 4k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
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. 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 (Linear's signature compact UI). 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 Linear page, not as the user's brand. Canvas tokens — light theme (default to ship) Status dot palette (must use exactly these): Priority icon = 4 small vertical bars, height ascending. Filled bars indicate level: 0 None → 4 Urgent. Urgent uses #d4513a; High uses #c77d1a; Medium/Low use #505259. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/orbit-linear--751277