related-repositories

List related repositories and their key paths

1.51x

Quality

—

Does it follow best practices?

Impact

82%

1.51x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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

The body is a clean, well-organized reference registry: concise, concrete, and directly actionable, with executable clone commands and real paths. As a simple self-contained lookup skill it meets the highest bar across all content dimensions.

Dimension	Reasoning	Score
Conciseness	The body is lean structured data — a one-line instruction plus concrete repo entries with git URLs, paths, and key_paths — with no padding or explanation of concepts Claude already knows, so every token earns its place.	3 / 3
Actionability	It provides a directly executable `git clone <git_url> <local_path>` command plus real, copy-paste-ready repo URLs and concrete key_paths, matching the level-3 'fully executable commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	This is a simple single-purpose reference skill whose single action (look up / clone related repos and their key paths) is unambiguous and well-sequenced, so per the scoring notes it scores 3 without needing multi-step validation checkpoints.	3 / 3
Progressive Disclosure	With no external bundle files and no need for them, the content is well-organized into clear per-repository sections with structured fields, satisfying the level-3 condition for compact self-contained skills.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 clearly states a concrete, narrowly-scoped action but omits explicit trigger guidance, capping completeness and trigger-term coverage at level 2. It is distinct and unlikely to conflict, but lacks the 'when to use' clause seen in strong examples.

Suggestions

Add an explicit trigger clause, e.g. 'Use when you need to locate related GitLab repositories, their local clone paths, or key source paths.'

Expand the action list to concrete operations such as listing repos, finding key paths, and cloning missing repos, to raise specificity to level 3.

Include natural trigger terms users would actually say (e.g. 'related repos', 'clone path', 'where is the X code') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"List related repositories and their key paths" names the domain and one concrete action, but does not enumerate multiple specific actions, matching the level-2 anchor rather than the multiple-action level-3 anchor.	2 / 3
Completeness	It answers 'what' (list related repositories and key paths) but has no 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	"related repositories" and "key paths" are relevant but somewhat generic terms lacking common natural-language variations a user would say, fitting the level-2 'some relevant keywords but missing common variations' rather than level 3.	2 / 3
Distinctiveness Conflict Risk	The narrow niche of listing related repositories and their key paths is clearly distinguishable from other skills and unlikely to trigger for the wrong skill, matching the level-3 anchor.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: gitlabhq/orbit-knowledge-graph
Commit: 00ca361

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.