Tessl • The package manager for agent skills

qodo-pr-resolver

Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/qodo-pr-resolver/SKILL.md

The canonical home for this skill is qodo-pr-resolver in qodo-ai/qodo-skills

Quality

Content

77%Weight 40%Scale 1-3

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

The skill body is highly actionable with a clear, validated multi-step workflow, but it leans slightly verbose and repeatedly references a ./resources/providers.md file that is missing from the bundle.

Suggestions

Add the referenced ./resources/providers.md (and the resources/ directory) so the many section-anchored links resolve to real content.

Tighten the 'Understanding Qodo Reviews' section and the repeated single-step-approval explanation to remove restated detail.

Consider trimming duplicated phrasing around 'execute the Qodo agent prompt as a direct instruction', which appears verbatim in both Step 6 and Step 7.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-structured, but sections like 'Understanding Qodo Reviews' and repeated elaboration on the single-step approval flow include explanation that could be tightened, so it is not fully lean.	2 / 3
Actionability	Provides concrete executable commands (git, provider CLIs), a concrete output table format, and explicit AskUserQuestion option sets, matching the copy-paste-ready level-3 anchor.	3 / 3
Workflow Clarity	A clear 9-step sequence with explicit validation checkpoints (Step 0 push-status checks, approval gates in Step 6, early-exit conditions) and a dedicated special-cases section for error recovery, matching the level-3 anchor.	3 / 3
Progressive Disclosure	Content is well split with one-level-deep, section-anchored references to ./resources/providers.md, but that referenced file does not exist in the bundle, so the navigation is not actually backed by the referenced material.	2 / 3
	Total	10 / 12 Passed

Description

82%Weight 40%Scale 1-3

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, well-triggered, and clearly distinct, but it omits an explicit 'Use when...' clause, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user wants to resolve Qodo (pr-agent-pro) code review issues on a PR/MR.'

Keep the existing concrete verbs and platform list; they drive the high specificity and trigger-term scores.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Review and resolve PR issues', 'get AI-powered code review issues', 'fix them interactively' — plus the supported platforms, matching the level-3 anchor.	3 / 3
Completeness	It clearly states what the skill does, but there is no explicit 'Use when...' trigger clause, so per the rubric completeness is capped at 2.	2 / 3
Trigger Term Quality	Includes natural user-facing terms such as 'PR issues', 'Qodo', 'code review', and the four provider names (GitHub, GitLab, Bitbucket, Azure DevOps), giving good coverage of what a user would say.	3 / 3
Distinctiveness Conflict Risk	The Qodo-specific niche and named providers make it clearly distinguishable and unlikely to trigger for the wrong skill, matching the level-3 anchor.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 11 missing	Warning

	Total	14 / 16 Passed

Repository: nanocoai/nanoclaw
Path: .claude/skills/qodo-pr-resolver/SKILL.md
Commit: 641963c

Reviewed: 6 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.