CtrlK
BlogDocsLog inGet started
Tessl Logo

resolve-repo

Resolve the correct repository for a task — detect VCS platform, match ticket to repo, clone if missing. Run this in a sub-agent to avoid filling main context.

60

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with a clearly sequenced, gated workflow and concrete executable code, but it is somewhat redundant and monolithic for its length with no progressive disclosure.

Suggestions

Remove the redundant "Important" section or trim it to only constraints not already stated in Context Budget and the steps.

Factor the pinned output-format blocks (Repo Match Results, Resolved Repository) into a short reference snippet to reduce inline bulk, or at least de-duplicate the repeated format rules.

Consolidate the repeated "name + description only / no cloning to inspect" guidance into a single canonical statement.

DimensionReasoningScore

Conciseness

Mostly concrete and action-oriented, but the closing "Important" section restates constraints already given in Context Budget and Step 3 ("Name + description only", "Local repos first"), so it could be tightened.

2 / 3

Actionability

Provides executable bash for metadata scanning, lib calls, scoped remote fetching, and pinned machine-checked output blocks with a concrete example — copy-paste ready.

3 / 3

Workflow Clarity

Six steps are clearly sequenced with explicit gates ("Only reach this step if no local repo matched confidently"), machine-checked output validation, and user confirmation before cloning.

3 / 3

Progressive Disclosure

Well-organized into named sections, but it is a single ~200-line file with no one-level-deep reference split; the determinism-lib usage and output-format specs are inline rather than factored out.

2 / 3

Total

10

/

12

Passed

Description

60%

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 and action-oriented about what the skill does, but it omits an explicit trigger/"Use when" clause, leaving the activation conditions implied and limiting completeness and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. "Use when a ticket/task needs to be mapped to the right repository and you aren't sure which one to clone."

Include natural user-facing terms and variations ("which repo", "find the right repo", "ticket to repo") to improve trigger coverage.

Tighten the sub-agent note or move it to the body so the description stays focused on what/when.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "detect VCS platform, match ticket to repo, clone if missing" — matching the multi-action anchor rather than the single-domain score-2 example.

3 / 3

Completeness

Clearly states what the skill does, but the "when" is only implied; the missing explicit "Use when…" clause caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Contains relevant keywords ("repository", "ticket", "clone") but lacks natural trigger phrasing a user would say; no "Use when…" style coverage of common variations.

2 / 3

Distinctiveness Conflict Risk

The repo-resolution niche is fairly specific, but without explicit distinct triggers it could still overlap with generic git/clone or repo-discovery skills, matching the score-2 anchor.

2 / 3

Total

9

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
AndreJorgeLopes/devflow
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.