CtrlK
BlogDocsLog inGet started
Tessl Logo

resolve-pr-feedback

Resolve GitHub PR review feedback with source-backed triage, fixes, autogoal plan state, mandatory autoreview closeout, replies, and thread resolution.

67

Quality

81%

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

88%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 highly actionable with a clear, validated multi-step workflow and bundled scripts referenced one level deep; minor conciseness gains and content splitting could push it higher.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence with no padding or over-explanation of basic concepts, though the fix/validate/autoreview pipeline is restated in Targeted Mode and could be tightened slightly.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands and concrete script paths for fetching, replying, and resolving, covering the common PR-feedback cases.

5 / 5

Workflow Clarity

The 11-step Full Mode is clearly sequenced with explicit validation (step 6), an autoreview closeout gate (step 7), a re-fetch verify loop (step 10), and a repeat-limit stop condition for churn.

5 / 5

Progressive Disclosure

Scripts are bundled and clearly referenced as one-level-deep paths, and the file is well sectioned; the three URL-handling subsections are somewhat detailed inline but navigation is still easy.

4 / 5

Total

18

/

20

Passed

Description

75%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 is specific and distinctive, clearly enumerating the workflow's actions, but it omits an explicit 'Use when...' trigger clause that would tell Claude when to invoke it.

Suggestions

Add a 'Use when ...' clause naming the natural trigger phrases (e.g., 'Use when addressing PR review comments, unresolved threads, or a specific PR comment URL').

Include common user synonyms like 'address comments', 'reply to review', and 'resolve threads' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in one sentence: 'source-backed triage, fixes, autogoal plan state, mandatory autoreview closeout, replies, and thread resolution', giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

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

3 / 5

Trigger Term Quality

Natural terms like 'PR review feedback' and 'thread resolution' are present, but common user phrases such as 'address comments' or 'reply to review' and synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (resolving GitHub PR review feedback) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

17

/

20

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
udecode/plate
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.