CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

orbit-wrapper

Use Orbit (`glab orbit` or `orbit`) to search code and read it with callers and tests. It reads MRs, issues, and failed jobs with the code they cite. Graph queries answer relationship and aggregation questions across GitLab. Skip it for writes that `glab` handles.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

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

This is an exemplary thin-wrapper skill: minimal, fully executable, and self-healing, with explicit validation checkpoints and graceful fallbacks for stale or missing tooling. It delegates all detail appropriately to the dynamically loaded skill.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and every sentence is functional — wrapper identity, the load command, fallback, link handling, version floors, and an install-approval guardrail — with no explanations of concepts Claude already knows.

5 / 5

Actionability

Fully executable, copy-paste-ready commands throughout ("!`glab orbit skills get orbit`", "orbit skills get orbit", "glab orbit skills get orbit <path>", "glab orbit --update") with concrete version requirements and recovery paths covering the common cases: stale tooling, missing CLI, and the standalone binary.

5 / 5

Workflow Clarity

A single-purpose, under-50-line skill where the simple-skill exception applies: the sequence is unambiguous with explicit validation checkpoints ("If the block above is not a skill (it should begin with `---`)" and "If that prints help or an unknown-command error") each branching into concrete recovery steps.

5 / 5

Progressive Disclosure

No bundle files exist and none are needed — all detailed content is deliberately delegated to the remotely-served skill, with clear instructions for fetching its referenced paths one level deep via "glab orbit skills get orbit <path>".

5 / 5

Total

20

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 communicates concrete capabilities in a distinctive, well-scoped way with an unusual but useful negative trigger. Its main weakness is the absence of an explicit positive "Use when..." clause, leaving the activation trigger only implied.

Suggestions

Add an explicit positive trigger clause, e.g. "Use when exploring an unfamiliar GitLab codebase, finding the callers or tests of a function, or investigating MRs, issues, or failed CI jobs."

Spell out "merge requests" alongside "MRs" so users who type the full phrase match the description naturally.

Include common synonyms such as "call sites" or "usages" next to "callers" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists several concrete actions with named objects — "search code and read it with callers and tests", "reads MRs, issues, and failed jobs with the code they cite", "Graph queries answer relationship and aggregation questions across GitLab" — but the graph-query capability is phrased at a category level rather than as fully concrete actions, leaving minor gaps versus comprehensive coverage.

4 / 5

Completeness

The "what" is explicit and multi-part, but the "when" appears only as a negative exclusion ("Skip it for writes that `glab` handles") with no positive "Use when..." clause, so the inclusion trigger is only weakly implied by contraposition.

3 / 5

Trigger Term Quality

Good natural-term coverage — "search code", "MRs", "issues", "failed jobs", "callers", "tests", "graph", "GitLab", "glab" — but misses common variations users would say, such as "merge requests" spelled out, "call sites", or "usages".

4 / 5

Distinctiveness Conflict Risk

Highly distinctive niche — Orbit/GitLab knowledge-graph tooling via "glab orbit", MRs, failed jobs, and graph queries — and the skip clause explicitly disambiguates against plain glab write operations, minimizing conflict risk.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

gitlabhq/orbit-knowledge-graph

Path

skills/orbit-wrapper/SKILL.md

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.