CtrlK
BlogDocsLog inGet started
Tessl Logo

orbit-general

Open Orbit briefing skill — selected by the Orbit pipeline when the user has two or more connectors connected. Pulls the past 24 hours of activity from every authenticated connector (GitHub, Linear, Notion, Slack, 飞书, Calendar, Gmail, Drive, Sentry, Vercel, …) and renders a single adaptive bento-grid dashboard at the top of "我的设计". Each connector module picks its own UI form (list, avatar stack, status ring, heatmap, file grid, alert card, …) based on the data shape it returns, so the layout scales as Orbit's connector ecosystem grows. This skill should not be triggered manually — it is invoked by Orbit's daily-digest scheduler against the user's live connector data.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./design-templates/orbit-general/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

The body is lean, well-organized, and highly specific, but its core 'reproduce example.html' instruction fails because example.html is missing from the bundle, which drags down actionability, workflow clarity, and progressive disclosure.

Suggestions

Ship the referenced example.html in the bundle (e.g. assets/example.html) so the 'reproduce it 1:1' instruction is actually executable.

Add an explicit verification checkpoint such as 'confirm DOM hierarchy, class names, and section order match example.html before finishing' to lift workflow clarity.

Move the large inline token/section spec into the example or a reference file so SKILL.md stays an overview pointing one level deep, improving progressive disclosure.

DimensionReasoningScore

Conciseness

Dense and token-efficient — exact tokens, type stack, px sizes, and a mapping table — with no padding or explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

Concrete specs (hex values, sizes, do/don't table) are strong, but the central instruction 'reproduce example.html 1:1' depends on example.html, which is not present in the bundle, so the skill cannot be executed as written.

2 / 3

Workflow Clarity

A clear 3-step protocol (read example, mirror 1:1, freshen data only) with an identity guard is present, but there is no explicit verification checkpoint and the canonical file to verify against is missing.

2 / 3

Progressive Disclosure

The body is well-sectioned and references the canonical example.html, but no references/scripts/assets directories exist and example.html is referenced yet not shipped, breaking the disclosure contract.

2 / 3

Total

9

/

12

Passed

Description

67%Weight 40%Scale 1-3

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 distinct, but it describes an automated scheduler-invoked skill rather than giving Claude explicit 'Use when' trigger guidance, which caps completeness and weakens trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill, even if it is normally scheduler-driven, so completeness can reach 3.

Reframe scheduler jargon ('Orbit pipeline', 'daily-digest scheduler') toward user-sayable phrasing like 'morning briefing' and 'daily digest' to lift trigger-term quality.

Keep the concrete action list and connector enumeration — these are the strongest part of the description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Pulls the past 24 hours of activity from every authenticated connector' and 'renders a single adaptive bento-grid dashboard' — with enumerated connectors and UI forms.

3 / 3

Completeness

'What' is clearly answered (pulls activity, renders dashboard) and a 'when' condition exists, but there is no 'Use when...' trigger guidance directed at Claude and it states the skill is scheduler-invoked, capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Some natural terms appear ('briefing', connector names) but the description is framed in pipeline/scheduler jargon ('Orbit pipeline', 'daily-digest scheduler') and explicitly says it 'should not be triggered manually', so it is not phrased as something a user would naturally say.

2 / 3

Distinctiveness Conflict Risk

A very specific niche — 'Open Orbit briefing', bento dashboard at the top of '我的设计', connector ecosystem — with distinct triggers unlikely to collide with other skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
Reviewed

Table of Contents

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.