Skip to content
Skillpedia
Automations101k · #490

orbit-linear

Has your agent create a daily summary of Linear activities, like status changes and task assignments. It's useful for teams to track project and task progress.

What it does

This agent shows you a summary of your tasks and updates in Linear, the tool you use for project management. It displays what has changed in the last 24 hours, such as tasks assigned to you or that have changed status.

When to use it

  • ✓At the start of the day to see what needs attention.
  • ✓When returning from a meeting to quickly catch up.
  • ✓At the end of the day to review progress.

Example of what to ask your AI

“Show me my daily Linear digest.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/nexu-io/open-design/blob/main/design-templates/orbit-linear/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/nexu-io/open-design/blob/main/design-templates/orbit-linear/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

It connects to your Linear account and fetches the latest information about your tasks. Then, it organizes everything into an easy-to-read format, similar to the Linear interface itself.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add nexu-io/open-design --skill orbit-linear

Or download just the file:

curl -L https://raw.githubusercontent.com/nexu-io/open-design/main/design-templates/orbit-linear/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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 the example, connector account labels, owners, assignees, senders, or mentions unless the request or connector data explicitly identifies the authorized user. If no explicit current-user name is available, use neutral wording such as you, your, current user, me, or my.

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)

page bg:           #f4f5f6
surface:           #ffffff
ink:               #1b1c1f
ink-2:             #37393e
ink-3 (muted):     #6c6f78
ink-4:             #9ea1a9

border:            rgba(0,0,0,0.06)
border-card:       rgba(0,0,0,0.08)
border-strong:     rgba(0,0,0,0.12)
hover row:         rgba(0,0,0,0.025)
active row:        rgba(0,0,0,0.05)

accent:            #5e6ad2
accent-bg:         rgba(94,106,210,0.06)

attention accent:  #c77d1a   /* "needs attention" group */
attention bg:      rgba(212,148,14,0.06)

shadow-card:       0 1px 2px rgba(0,0,0,0.04), 0 0 0 1px rgba(0,0,0,0.05)

Status dot palette (must use exactly these):

backlog:    #9ea1a9   /* gray, hollow ring */
todo:       #d4940e   /* yellow, dashed ring */
progress:   #2b80c5   /* blue, partial ring */
review:     #8759c7   /* purple, partial ring */
done:       #1a8d3a   /* green, filled */
canceled:   #6c6f78   /* gray with strike */

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.

Type stack:

  • 'Inter', -apple-system, BlinkMacSystemFont, 'SF Pro Display', system-ui, sans-serif
  • Mono: 'Berkeley Mono', ui-monospace, 'SF Mono', 'JetBrains Mono', Menlo, monospace
  • Sizes: nav 13px, row title 13.5px, meta 12px, headers 11px caps with letter-spacing 0.04em

Page sections

  1. Top toolbar — single row, 44px tall, no shadow, hairline border-bottom. Left: breadcrumb Orbit › Daily Digest › May 6 (13px, …›… separators in ink-4). Then a thin divider, then ▼ My issues view switcher. Right: 🔍 search, + new, ▦ display options, avatar.

  2. Cycle progress strip — slot to the right of the breadcrumb area, one line: Cycle 12 · 60% complete · 3 days left. Render as 11px caps with a tiny inline progress bar (60px wide, 4px tall, accent fill).

  3. Three-column main:

    • Left nav (240px): vertical, no background — items at 13px. Sections: Inbox · My issues · Active · Backlog · All issues, then a divider, then 📋 Triage · 🚫 Canceled · ✅ Completed. Active row: accent-bg background, accent ink.

…

FAQ

What is Linear?

Linear is a tool used by teams to organize and track project work.

What does 'daily digest' mean?

It's a list of the most important activities that happened in the last 24 hours, such as tasks assigned to you or tasks that were completed.

Does the agent use my personal information?

It only shows information about your tasks in Linear. It does not use your name or other personal data unless strictly necessary to display your tasks.

Details

Original description by the author

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. Thi

repo: nexu-io/open-design

Popularity

GitHub stars
101k
Ranking position
#490
License
Apache-2.0
Updated
10/16/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills