Tessl • The package manager for agent skills

orbit

Query GitLab 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`).

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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.

The body is lean, highly actionable, and well-structured, with executable examples and an explicit iteration-budget feedback loop. Progressive disclosure is exemplary, with all inline references resolving to real bundle files.

Dimension	Reasoning	Score
Conciseness	The body is dense and purposeful with no padding or explanation of concepts Claude already knows (no 'what is a merge request' filler); every section — Discovery, Running a query, Common pitfalls, Iteration budget — earns its tokens, matching the lean top anchor.	5 / 5
Actionability	Provides copy-paste-ready executable guidance: the PROJECT_ID resolution one-liner, a complete orbit-query JSON body, the `glab orbit remote query /tmp/q.json` invocation, and a concrete schema-introspection `--jq` example cover the common cases.	5 / 5
Workflow Clarity	Sequences discovery → query construction → pitfalls → reporting, with an explicit iteration-budget feedback loop ('at most 5 query attempts', 'validation errors count toward the budget', 'give up loudly') that acts as an error-recovery checkpoint.	5 / 5
Progressive Disclosure	SKILL.md is a clear overview with well-signaled one-level-deep references (all 9 referenced files in references/ exist) consolidated in a References table; bulk DSL, recipes, and troubleshooting are appropriately split into separate files.	5 / 5
	Total	20 / 20 Passed

Description

100%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 is specific, trigger-rich, and complete, clearly stating both what the skill does and when to use it while carving out an explicit negative boundary against plain glab. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Query GitLab Orbit via glab orbit remote CLI subcommands', 'run a local copy with glab orbit local', 'repository map / repo-map generation', 'blast-radius analysis' — with comprehensive coverage of query types, matching the top anchor rather than the 4 anchor's 'minor gaps'.	5 / 5
Completeness	Explicitly answers both 'what' (Query GitLab Orbit via CLI subcommands) and 'when' ('Use for code-structure questions...'), with concrete trigger phrases and an explicit 'Do not use for...' boundary, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases users would say ('who calls this function, where is this symbol defined', 'blast-radius analysis', 'repo-map') plus synonyms (repository map / repo-map) and the enumerated GitLab entities, giving comprehensive trigger coverage.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (GitLab Orbit knowledge-graph queries) with distinct triggers and an explicit negative boundary ('Do not use for single-entity GitLab lookups or write operations that glab handles directly'), minimizing conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: skills/orbit/SKILL.md
Commit: a2b60b1

Reviewed: 4 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.