CtrlK
BlogDocsLog inGet started
Tessl Logo

qodo-pr-resolver

Use when the user wants to review Qodo PR feedback or fix code review comments. Capabilities: view issues by severity, apply fixes interactively or in batch, reply to inline comments, post fix summaries (GitHub, GitLab, Bitbucket, Azure DevOps, Gerrit)

71

Quality

88%

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

SKILL.md
Quality
Evals
Security

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 body is a thorough, well-sequenced multi-provider workflow with strong validation checkpoints and concrete git/tool guidance. Its weaknesses are cross-step redundancy that hurts token efficiency and references to a ./resources/ bundle that cannot be verified in the provided skill.

Suggestions

Consolidate the oscillation/convergence handling into Step 3c plus convergence.md and have Steps 6/7/8 reference it once instead of restating the rules each time.

State the Gerrit amend-then-push commit strategy once and link from Steps 6/7/8/9 rather than repeating it in each step.

Ensure the referenced ./resources/ files (providers.md, gerrit.md, convergence.md) ship in the skill bundle, or move them under a standard bundle directory (references/) so the one-level-deep links resolve.

DimensionReasoningScore

Conciseness

Most content is novel Qodo-specific domain knowledge that earns its place, but the oscillation/convergence rules are restated across Steps 3c, 6, 7 and 8, the Gerrit commit strategy repeats in Steps 6/7/8/9, and single-step approval is explained twice — could be tightened.

2 / 3

Actionability

Provides copy-paste-ready git commands (e.g. `git add <modified-files> && git commit -m "fix: <issue title>"`, `git push origin HEAD:refs/for/<target-branch>`), exact Monitor/AskUserQuestion parameters, a concrete rendered output example, and precise parse/dedup rules; deferring large per-provider API specifics to a reference is appropriate disclosure.

3 / 3

Workflow Clarity

Steps 0–10 are clearly sequenced with explicit validation checkpoints: a wait/poll loop with timeout in Step 3a, single-step approval before edits in Step 6, and an oscillation hard-stop guard — feedback loops are present for the destructive/batch fix operations.

3 / 3

Progressive Disclosure

References are well-signaled and one level deep with section anchors (providers.md, gerrit.md, convergence.md), but those ./resources/ files are not present in the staged bundle to verify, and ./resources/ is not one of the standard bundle directories — a structural gap versus the score-3 'appropriately split, easy navigation' anchor.

2 / 3

Total

10

/

12

Passed

Description

100%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 well-crafted: third-person voice, an explicit 'Use when' trigger, a concise capabilities list, and a distinctive Qodo/provider niche. It hits the top anchor on every dimension with no fluff or over-claims.

DimensionReasoningScore

Specificity

Names four concrete actions ("view issues by severity", "apply fixes interactively or in batch", "reply to inline comments", "post fix summaries") plus five named providers, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

An explicit "Use when the user wants to review Qodo PR feedback or fix code review comments" trigger answers 'when', and the "Capabilities:" list answers 'what' — both present with explicit triggers.

3 / 3

Trigger Term Quality

Includes natural phrases a user would say ("review Qodo PR feedback", "fix code review comments", "Qodo") with good coverage of common variations, not just technical jargon.

3 / 3

Distinctiveness Conflict Risk

The Qodo-specific niche and five enumerated git providers give it a clear, narrow trigger surface unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 25 missing

Warning

Total

14

/

16

Passed

Repository
qodo-ai/qodo-skills
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.