CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

96

1.72x
Quality

95%

Does it follow best practices?

Impact

100%

1.72x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 provides concrete clone commands and real repository metadata without padding. It is appropriately lean for its single-purpose scope.

DimensionReasoningScore

Conciseness

The body is a lean registry of concrete metadata (git URLs, project URLs, local paths, one-line descriptions) with no re-explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

It gives a concrete executable command ('git clone <git_url> <local_path>') alongside the real git URLs and local paths needed to fill it in, making the guidance directly usable.

3 / 3

Workflow Clarity

This is a simple single-task skill whose one conditional action ('If a repository is not cloned locally, clone it ...') is unambiguous; the rubric's simple-skills note allows a 3 in that case, and cloning is not a destructive/batch operation requiring a validation checkpoint.

3 / 3

Progressive Disclosure

The body is under 50 lines, needs no external references, and is organized into clear sections (## Repositories, per-repo ### headers), meeting the under-50-lines well-organized-sections allowance for a 3.

3 / 3

Total

12

/

12

Passed

Description

90%

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 clear, well-scoped description with explicit 'Use when' triggers and concrete actions. Its only weakness is second-person voice, which costs it a specificity point under the rubric's voice guideline.

Suggestions

Rewrite the 'Use when' clause in third person (e.g., 'Use when finding where a related repo is checked out locally, retrieving its git URL, or cloning it if missing') to avoid the second-person specificity penalty.

Replace the jargon phrase 'other consumed repos' with plainer wording such as 'other repositories this project depends on' so the trigger reads as something a user would naturally say.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('find where a related repo is checked out locally, get its git URL, or clone it if it is missing'), which meets the score-3 anchor; however, it uses second-person voice ('Use when you need to find'), which the judging guidelines penalize by reducing specificity by one point.

2 / 3

Completeness

It explicitly states both what it is ('Registry of related repositories ... with their git URLs and local checkout paths') and when to use it ('Use when you need to find ... or clone it if it is missing'), satisfying the explicit-trigger requirement.

3 / 3

Trigger Term Quality

Natural terms a user would actually say are well covered ('git URL', 'clone', 'checkout', 'checked out locally') alongside project names (Siphon, Rails), matching the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

The niche (a registry of related-repo git URLs and local checkout paths) is distinct and its triggers are specific enough that it is unlikely to fire for an unrelated skill.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

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.