CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

orbit-package-registry

Use Orbit graph queries to answer questions about GitLab Package Registry packages and Container Registry repositories across projects and groups. Use it to find which projects host a package. It covers package versions and their files, declared dependencies, known vulnerabilities, and the pipelines that built them. Load it with the `orbit` skill. Skip it for one project's package list or for publishing, which `glab` and the package manager handle.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An excellent single-file skill: dense with non-obvious domain rules, fully executable query recipes covering the common cases, and explicit guidance on interpreting partial or permission-limited results. The only structural improvement would be splitting the recipes into a reference file to keep SKILL.md leaner.

DimensionReasoningScore

Conciseness

Every rule conveys non-obvious domain knowledge (status filter values, 'STARTS WITH' vs. fixed-depth group walking, SBOM match semantics, Security Manager role effects, pagination traps) with no padding and no re-explanation of concepts Claude already knows. This matches the anchor 'every token earns its place'.

5 / 5

Actionability

Nine complete, executable 'gql orbit-query' blocks with concrete real-world names and versions, plus exact 'glab api' shell commands for tag counts. The guidance is copy-paste ready and the recipes cover the common question types end to end.

5 / 5

Workflow Clarity

As a single-purpose, read-only query skill the action is unambiguous ('Run each recipe with glab orbit query'), each task type has a named recipe, and result validation is addressed ('a response with has_more: true or truncated: true... Group and count instead, or page with SKIP') along with safety caveats about missing vulnerability links. No destructive or batch operations, so no validation cap applies.

5 / 5

Progressive Disclosure

The body is well-organized (Rules vs. Recipes) with working internal anchor links and cohesive placement, but at roughly 130 lines with everything inline it exceeds the under-50-line threshold that would let a sectioned single file score 5. It is not anchor 3 because the structure is clear and navigable, and no content is buried.

4 / 5

Total

19

/

20

Passed

Description

83%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, specific description that clearly states what the skill does, defines a distinct GitLab package/container registry niche, and includes both a positive trigger and negative boundary guidance. Its only weakness is a narrow 'when' clause that names just one triggering scenario despite the skill covering several.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('find which projects host a package', 'package versions and their files, declared dependencies, known vulnerabilities, and the pipelines that built them') that comprehensively mirror the body's recipes. It stays at anchor 5 rather than 4 because there are no meaningful gaps in coverage relative to what the skill does.

5 / 5

Completeness

The 'what' is clear (Orbit graph queries over Package Registry and Container Registry data) and a 'when' is explicit ('Use it to find which projects host a package') plus negative triggers ('Skip it for one project's package list or for publishing'). It is not anchor 5 because the positive 'when' clause covers only one scenario while the body supports several more (versions, files, dependencies, vulnerabilities, pipelines).

4 / 5

Trigger Term Quality

It includes natural terms users would say — 'packages', 'dependencies', 'vulnerabilities', 'Container Registry', 'which projects host a package' — giving good keyword coverage. It falls short of anchor 5 because common synonyms like 'container images' or format-specific terms (e.g., 'npm packages') are absent.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (GitLab Package/Container Registry questions via Orbit graph queries) and actively reduces conflict risk with explicit skip guidance steering publishing and single-project listing tasks to 'glab and the package manager'. Minimal overlap with other skills.

5 / 5

Total

18

/

20

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.

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

Path

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