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.

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./design-templates/orbit-linear/SKILL.md

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concrete, well-organized Linear design spec, but it leans on an example.html that is not shipped in the bundle, offers no output-validation step, and keeps all tokens inline rather than splitting them into a referenced file.

Suggestions

Ship the referenced example.html in the bundle (or remove the dependency on it) so the 'reproduce 1:1' instruction is actually executable.

Add a verification checkpoint (e.g. diff the generated DOM/class names against example.html, or confirm row heights and status-dot palette match) before declaring the briefing done.

Move the full token tables into a referenced file (e.g. tokens.md) and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Most content is necessary design spec Claude would not know (exact tokens, fonts, px sizes), but the source-of-truth protocol and design-system policy repeat guardrails ('ignore it' stated twice, 'reproduce it, not reinterpret it' restated) and could be tightened; not a 3 due to this redundancy, not a 1 because no basic concepts are over-explained.	2 / 3
Actionability	Provides concrete spec (hex colors, font stacks, row heights, DOM structure, do/don't table), but the primary directive — 'Open and read the shipped example.html... your job is to reproduce it' — points to a file absent from the bundle, leaving the canonical executable reference missing; fits 'some concrete guidance but incomplete, missing key details'.	2 / 3
Workflow Clarity	A clear Step 1/2/3 sequence (read example, mirror 1:1, refresh mock values) is present, but there is no validation or verification checkpoint for the HTML reproduction, matching the 'steps listed but validation gaps' anchor; not a 3 because no explicit validation/feedback loop exists.	2 / 3
Progressive Disclosure	Well-sectioned with clear headings, but all design tokens are inline in SKILL.md and the single external reference (example.html) does not exist in the bundle, fitting 'some structure but content that should be separate is inline' with a broken referenced path; not a 1 because organization is decent, not deeply nested.	2 / 3
	Total	8 / 12 Passed

Description

67%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and well-scoped to a distinct Linear-only Orbit daily-digest niche, but it frames triggering as automated pipeline behavior rather than providing explicit user-facing 'Use when...' trigger guidance, capping completeness and trigger-term coverage.

Suggestions

Add an explicit 'Use when the user asks for their Linear briefing/digest, or scopes their daily digest to Linear' clause to lift completeness and trigger-term quality.

Surface the natural trigger phrases ('linear briefing', 'linear digest', 'issue digest') inside the description body rather than only in the separate triggers list.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Pulls the past 24 hours of issue movement, status changes, assignments, and cycle progress' and 'renders the digest in Linear's native Inbox + cycle-progress visual language' — matching the multiple-specific-actions anchor; not a 2 because the action set is comprehensive rather than partial.	3 / 3
Completeness	Clearly answers 'what' but the 'when' is framed as automated scheduler invocation ('invoked by Orbit's daily-digest scheduler') with no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric caps at 2; not a 3 because explicit trigger guidance is absent.	2 / 3
Trigger Term Quality	Contains relevant natural terms ('Linear', 'daily digest', 'cycle progress') but embeds them in explanatory prose without enumerating common user-facing variations (e.g. 'linear briefing', 'linear digest'), fitting the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	A clearly bounded niche — 'selected by the Orbit pipeline when Linear is the user's only connected connector' — with distinct context unlikely to overlap with other skills; not a 2 because the scoping is sharp rather than merely 'somewhat specific'.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/orbit-linear/SKILL.md
Commit: f2760fd

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.