CtrlK
BlogDocsLog inGet started
Tessl Logo

orbit

Query the GitLab Knowledge Graph (Orbit) via `glab orbit remote` CLI subcommands or run a local copy with `glab orbit local`. Use for code-structure questions (who calls this function, where is this symbol defined), cross-project dependency and blast-radius analysis, merge-request and contributor queries that require relationship traversal or aggregation, repository map / repo-map generation, and any question spanning relationships, cross-entity joins, or multi-entity aggregation across GitLab entities (projects, users, MRs, issues, pipelines, files, definitions, vulnerabilities). Do not use for single-entity GitLab lookups or write operations that `glab` handles directly (e.g. `glab mr view`, `glab mr create`).

78

Quality

100%

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-3

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

The content is lean yet highly actionable, with executable examples, an explicit error-recovery feedback loop, and a clean progressive-disclosure structure pointing to verified reference files. It exemplifies a well-built skill body.

DimensionReasoningScore

Conciseness

The body is dense and lean — it assumes Claude's competence (no explanation of GitLab, ClickHouse, or merge requests) and every line carries actionable guidance with no concept padding.

3 / 3

Actionability

Provides a complete copy-paste-ready `json orbit-query` request body plus the `glab orbit remote query /tmp/q.json` command, concrete operator lists, and specific `--jq` examples — fully executable rather than pseudocode.

3 / 3

Workflow Clarity

The query workflow is clearly sequenced (Discovery → Running a query → Common pitfalls → Reporting) with an explicit iteration-budget feedback loop that counts HTTP 400 errors and instructs a 'give up loudly' recovery when the budget is exceeded.

3 / 3

Progressive Disclosure

The body is an overview that signals one-level-deep references (all 9 referenced files verified to exist) via a well-organized References table, with detail appropriately split into query_language.md, recipes.md, troubleshooting.md, and others.

3 / 3

Total

12

/

12

Passed

Description

100%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 concrete, trigger-rich, and self-distinguishing, explicitly answering both what the skill does and when to use it (and when not to). It is a strong, well-scoped skill description with no significant gaps.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — query via `glab orbit remote` subcommands, cross-project dependency/blast-radius analysis, MR/contributor queries with relationship traversal, and repository map generation — rather than vague language.

3 / 3

Completeness

Clearly answers both 'what' (query the GitLab Knowledge Graph via CLI subcommands) and 'when' with an explicit 'Use for...' trigger clause plus an explicit 'Do not use for...' anti-trigger.

3 / 3

Trigger Term Quality

Includes natural user phrasings such as 'who calls this function', 'where is this symbol defined', 'blast-radius analysis', and 'repository map / repo-map generation', giving good coverage of terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche (GitLab Knowledge Graph relationship/dependency queries via `glab orbit`) and explicitly distinguishes itself from `glab`'s direct single-entity commands, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
gitlabhq/orbit-knowledge-graph
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.