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.

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./devflow-plugin/skills/resolve-repo/SKILL.md

The canonical home for this skill is resolve-repo in AndreJorgeLopes/devflow

SKILL.md
Quality
Evals
Security

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.

The body is a strong, mostly lean workflow skill with highly executable guidance and excellent structure. The main weakness is minor repetition of the same constraints across sections rather than a single canonical statement.

Suggestions

De-duplicate the 'do NOT determinize scoring' rule and the local-first/scope-tightly/name-only constraints — state each once and reference it.

Add an explicit validate→fix→retry loop for the machine-checked output blocks (e.g., re-emit if the block fails format checking).

Consider consolidating the 'Important' recap into cross-references to the relevant steps to trim the recap.

DimensionReasoningScore

Conciseness

Largely lean with concrete bash and minimal concept explanation, but the 'do NOT determinize scoring' point and the local-first/scope-tightly rules are repeated across the Determinism section, Steps, and the 'Important' recap.

4 / 5

Actionability

Fully executable: copy-paste bash for repo scanning, lib function calls, glab/gh queries, clone plus setup hints, and pinned machine-checked output blocks covering the common GitLab/GitHub cases.

5 / 5

Workflow Clarity

A clear 6-step sequence with decision branches and confirmation gates for the destructive clone, but no explicit validate→fix→retry feedback loop on the machine-checked output blocks.

4 / 5

Progressive Disclosure

No bundle files exist; the only external references (the shared determinism lib and CONTRACT.md) are one-level-deep and clearly signaled, and the body is cleanly sectioned for easy navigation.

5 / 5

Total

18

/

20

Passed

Description

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

The description states concrete actions and a clear niche, but omits an explicit 'Use when...' trigger clause and leans on procedural rather than natural user-trigger keywords. Adding trigger phrasings would lift completeness and trigger_term_quality.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a ticket/issue needs to be mapped to the right repo and it's unclear which one.'

Add natural user phrasings like 'which repo,' 'find the right repo,' or 'ticket to repo' alongside the technical terms.

Optionally note the ranking/band output so the 'what' reflects the full scope of the skill.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'detect VCS platform,' 'match ticket to repo,' 'clone if missing' — with only minor coverage gaps (the scoring/ranking nuance isn't surfaced).

4 / 5

Completeness

The 'what' is clearly stated but there is no 'Use when...' trigger clause; per the rubric, a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant terms like 'repository,' 'ticket,' 'repo,' 'clone' are present but it lacks the natural trigger phrasings a user would actually say (e.g., 'which repo,' 'find the right repo').

3 / 5

Distinctiveness Conflict Risk

'Resolve the correct repository for a task' defines a specific niche with only minor overlap risk against generic git/clone skills.

4 / 5

Total

14

/

20

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.