orbit-linear
Best for Linear usersWorks with GitHubLow risk
⌘source
- author
@nexu-io- language
- TypeScript
★33kstars
3.7kforks
May 7, 2026
✦overview.md
Key Features
- ·24-hour issue movement digest
- ·Renders in Linear Inbox layout
- ·Cycle progress visualization
- ·Status change & assignment tracking
- ·Auto-triggered by daily scheduler
Use Cases
- →Get a daily summary of Linear issues updated in the last 24 hours
- →Review cycle progress and status changes each morning
- →Track new assignments across your Linear projects
Best for
- ✓Linear users
- ✓daily standups
- ✓cycle tracking
Not ideal for
- !users on other project management tools
- !manual on-demand use
FAQs
name
orbit-linear
description
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.
triggers:["linear briefing","linear digest","issue digest","linear 简报","issue 汇总"]
od:{"mode":"prototype","platform":"desktop","scenario":"orbit","featured":4,"preview":{"type":"html","entry":"index.html"},"design_system":{"requires":false},"example_prompt":"Generate today's Open Orbit Linear briefing. Linear is my only connected connector — pull yesterday's issue movement, cycle progress, status changes, and assignments and render them in Linear's native Inbox layout."}
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.
$install
1-click copynpx skills add nexu-io/open-design --skill orbit-linearSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
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.