related-repositories

Registry of related repositories (Siphon, Rails, and other consumed repos) with their git URLs and local checkout paths. Use when you need to find where a related repo is checked out locally, get its git URL, or clone it if it is missing.

1.72x

Quality

85%

Does it follow best practices?

Impact

100%

1.72x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

86%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 compact, well-structured registry skill that is directly actionable and appropriately scoped. The only notable gap is the absence of a post-clone verification step.

Dimension	Reasoning	Score
Conciseness	A lean data registry with no concept over-explanation; a few per-entry 'description' fields restate the heading (e.g. 'GitLab Knowledge Graph (orbit) Primary repository'), the minor trimming that keeps it below the 5 anchor.	4 / 5
Actionability	Provides the concrete command 'git clone <git_url> <local_path>' alongside every real git URL and local checkout path, making the common cases (look up a repo, clone if missing) fully copy-paste executable.	5 / 5
Workflow Clarity	The single workflow — look up the repo in the registry, clone if missing — is unambiguous, but there is no verify checkpoint confirming the clone succeeded, so it sits below the 5 anchor.	4 / 5
Progressive Disclosure	Under ~50 lines, self-contained with no need for external bundle references, and organized into clear per-repo sections; the simple-skill exception allows the top score.	5 / 5
	Total	18 / 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 well-crafted description that clearly states both purpose and trigger conditions with concrete, natural language. Minor gains are possible in trigger synonym coverage and sharpening distinctiveness from generic git skills.

Dimension	Reasoning	Score
Specificity	Names the domain (registry of related repos with git URLs and checkout paths) and three concrete actions — 'find where a related repo is checked out locally, get its git URL, or clone it if it is missing' — fitting the 'several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Explicitly answers both 'what' (registry with git URLs and local checkout paths) and 'when' ('Use when you need to find… get its git URL, or clone it if it is missing') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural developer phrases ('related repo', 'checked out locally', 'git URL', 'clone') a user would say, with good but not exhaustive coverage; a few synonyms are absent so it sits below the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	Clear niche (a related-repository registry) with distinct triggers and minimal conflict risk, though generic 'clone a repo' could overlap with general git skills, placing it just below the 5 anchor.	4 / 5
	Total	17 / 20 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
Path: .claude/skills/related-repositories/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.