CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

orbit-cli

Index and query a local checkout offline with the GitLab Orbit CLI (`orbit`, or `glab orbit`). Reach for it when a question names a symbol or spans code structure. Examples: who calls or extends this, where it is defined, what a file defines, how definitions are distributed. One call replaces many file reads and text greps, including matches in config, templates, and docs. Works on the working tree and unpushed branches, and also searches and reads the project's GitLab. Not a fit: reading one known file, or counts and relationships across GitLab (use the `orbit` skill).

Quality

87%

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

82%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.

A dense, highly actionable body: executable commands with concrete output semantics, an explicit grep-then-context workflow, and a real, clearly linked reference file. The main gaps are upfront density of index-lifecycle detail and inlining of query-language specifics that could live in references.

Suggestions

Move the index-lifecycle minutiae (10-minute read wait, exit code 75, lock behavior for `workspace index --async`/`--wait`) into a reference file, keeping only the one-line 'the index refreshes automatically' summary in SKILL.md.

Split the grep query-language and output-format rules (GitLab kinds, `»` markers, scoping/widening) into a one-level-deep reference like `references/query-language.md`, linked from a short 'Choose the command' overview.

Make the grep→context workflow's error handling explicit, e.g. a one-line note: 'If grep exits 1 (no match), widen the scope or drop a kind qualifier before giving up.'

DimensionReasoningScore

Conciseness

No space is spent on concepts Claude already knows; nearly every sentence carries tool-specific behavior (exit code 75, 30s lock waits, `»` marker lines, glab `--yes` flag ordering). Not 5 because the opening paragraphs densely front-load index-lifecycle, timeout, and exit-code detail that could be trimmed or deferred to the reference, slightly hurting clarity-per-token.

4 / 5

Actionability

Copy-paste-ready shell commands throughout — `orbit grep "method:rate limit" src`, `orbit context duckdb_client::search::DuckDbSearch::grep src/lib.rs:120-180`, `orbit grep "mr:rate limit repo:gitlab-org/gitlab"`, `glab orbit --yes grep "..."` — covering local search, context reads, and GitLab targets, with concrete output-interpretation rules. Fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

An explicit sequence is stated — "Run `grep` first, then `context` on the symbol you will change to get its callers, callees, and covering tests" — with exit-code feedback documented ("Exit 1 means no match"). The tool is read-only, so the destructive/batch validation cap does not apply. Not 5 because validation/error-recovery checkpoints remain implicit rather than spelled out as a feedback loop.

4 / 5

Progressive Disclosure

The bundle reference `references/local/cli.md` exists, is one level deep, and is clearly signaled twice (inline "Wrapper details" pointer and the References table), matching the actual bundle structure. Not 5 because substantial query-language and output-format detail (GitLab kinds, rg-style output rules, scoping/widening behavior) is inlined in SKILL.md rather than split into additional one-level-deep reference files.

4 / 5

Total

17

/

20

Passed

Description

92%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.

A strong description: concrete capabilities, explicit when-to-use triggers with examples, negative scoping, and explicit disambiguation from the related `orbit` skill. The only weakness is modest synonym coverage of trigger terms.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Index and query a local checkout offline", "One call replaces many file reads and text greps, including matches in config, templates, and docs", "also searches and reads the project's GitLab" — covering the tool's full capability surface (indexing, search, context reads, GitLab queries). Not 4 because there are no meaningful coverage gaps; every named capability is concrete.

5 / 5

Completeness

Both what ("Index and query a local checkout offline with the GitLab Orbit CLI") and when ("Reach for it when a question names a symbol or spans code structure. Examples: ...") are explicitly answered with concrete trigger phrases, plus negative guidance ("Not a fit: reading one known file..."). This matches the anchor-5 example's structure of explicit what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

Natural developer phrasing is present — "who calls or extends this, where it is defined, what a file defines", "a question names a symbol or spans code structure" — which matches how users would ask. Not 5 because common variants like "find usages", "references", or "code navigation" are absent; not 3 since multiple natural trigger phrases beyond a single generic keyword are covered.

4 / 5

Distinctiveness Conflict Risk

A clear niche (offline local-checkout symbol/structure queries) with explicit disambiguation from the sibling skill — "counts and relationships across GitLab (use the `orbit` skill)" — and negative triggers. Minimal conflict risk; the boundary against the overlapping skill is stated outright.

5 / 5

Total

19

/

20

Passed

Validation

75%

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

Validation — 12 / 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

relative_links

Relative link issues: 2 deeper-than-1-level

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 3 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

gitlabhq/orbit-knowledge-graph

Path

skills/orbit-cli/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.