CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

78%

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

73%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 well-engineered, highly actionable workflow: deterministic-first bash with explicit abstain handling, pinned machine-checkable output formats, and a clearly sequenced six-step process with strong validation checkpoints and fallback paths. The main weakness is redundancy — the context-budget and no-content-reading constraints are stated three times across the Context Budget, step 3, and Important sections.

Suggestions

Consolidate the repeated constraints: state the context-budget rules (no README/source reading, name+description only, tightly scoped remote queries) once and reference them from steps 3 and Important instead of restating them in three places.

Provide the concrete search-filtered query for groups with more than 50 repos (e.g. a glab/gh search command filtered by ticket keywords) and an explicit URL-construction example for the clone step.

Move the two pinned output templates (Repo Match Results and Resolved Repository blocks) into a short reference file to slim the main body while keeping them machine-checkable.

DimensionReasoningScore

Conciseness

The body assumes Claude's competence (no explaining git, jq, or VCS concepts) and its tokens are mostly operational, but the same constraints repeat across three sections — "Never read full READMEs, source files" (Context Budget), "no cloning, no README reading, no file inspection" (step 3), "never read repo contents, READMEs, or source files" (Important) — and the sub-agent note appears at both the top and the closing section. This is more than the "minor instances that could be trimmed" of the 4 anchor, but far from the padded concept explanations of the 2 anchor.

3 / 5

Actionability

The skill provides copy-paste-ready bash for repo scanning, lib sourcing with abstain handling ("val=$(detect_vcs_platform \"$REMOTE\") || val="""), scoped glab/gh queries, cloning, and setup hints, plus exact pinned output templates. It is not a 5 because the >50-repo case ("use a search query filtered by ticket keywords") and URL construction ("construct URL from platform + group + repo name") are described rather than given as commands, and bitbucket/azure remote fetch has no command.

4 / 5

Workflow Clarity

Steps 1–6 are explicitly sequenced with clear skip conditions ("Only reach this step if no local repo matched confidently"; a HIGH local match "does NOT skip the Repo Match Results block") and explicit validation checkpoints and recovery loops: lib abstain → AI fallback, CLI missing → "fall back to local-only results", ambiguous → "return top 3 candidates and let the caller ask the user", and mandatory user confirmation before cloning. This matches the 5 anchor (explicit validation steps, feedback loops, checklists); cloning is not a destructive/batch operation, so the cap of 3 does not apply.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so the skill is a single self-contained file with clear section headers, and its only external references (~/.claude/lib/determinism/functions/*.sh and CONTRACT.md) are one level deep and clearly signaled. It matches the 4 anchor (good structure, minor organization gaps) rather than 5 because ~200 lines are entirely inline — the output-format templates could live in a reference file — and it exceeds the simple-skill exception threshold.

4 / 5

Total

16

/

20

Passed

Description

71%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 concise, concrete, third-person description that clearly states what the skill does across its full pipeline, with good domain keywords and a distinct niche. Its main weakness is the complete absence of a "Use when..." trigger clause, which caps completeness and slightly raises conflict risk with generic git/clone requests.

Suggestions

Add an explicit trigger clause, e.g. "Use when a task or ticket (Jira/Linear/GitHub issue) needs to be mapped to one of several local or remote repositories, or when the right repo to work in is unclear."

Include natural user phrasings and platform names as trigger terms ("which repo", "find the repository", "GitHub/GitLab") to improve trigger-term coverage.

Clarify scope boundaries in the description (e.g. name+description matching only, no repo-content inspection) to further reduce overlap with general git/clone skills.

DimensionReasoningScore

Specificity

"detect VCS platform, match ticket to repo, clone if missing" lists multiple concrete actions that comprehensively cover the skill's pipeline (platform detection, ticket-to-repo matching, cloning) with no vague filler. It is not a 4 because no meaningful capability from the body (remote discovery is subsumed under matching) is left uncovered.

5 / 5

Completeness

The description has a clear "what" but no "Use when..." clause or equivalent explicit trigger guidance ("Run this in a sub-agent" is an execution instruction, not a trigger), which per the judging guidelines caps completeness at 3. It is not a 2 because the "what" is concrete and specific, and not a 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Natural domain terms are present ("repository", "repo", "ticket", "clone", "VCS platform") that a user would plausibly say, but common variations like "which repo", "find the repository", or platform names (GitHub/GitLab) are missing. It sits between the 3 anchor (missing synonyms) and 5 anchor (comprehensive synonyms/extensions), closer to good-but-incomplete coverage.

4 / 5

Distinctiveness Conflict Risk

Ticket-to-repo resolution is a distinct niche ("match ticket to repo") with minimal overlap risk, but the absence of trigger guidance means generic repo/cloning/git requests could plausibly fire it. It matches the 4 anchor (mostly distinct, minor overlap with closely related git/clone skills) rather than 5 (clear distinct triggers).

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

AndreJorgeLopes/devflow

Path

devflow-plugin/skills/resolve-repo/SKILL.md

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.