CtrlK
BlogDocsLog inGet started
Tessl Logo

resolve-pr-feedback

Resolve GitHub PR review feedback with source-backed triage, fixes, autogoal plan state, focused proof, 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 well-sequenced, validated workflow and correctly referenced bundle scripts. It is efficient though slightly long, and could optionally split the targeted-mode URL reference tables into a separate file.

DimensionReasoningScore

Conciseness

The body is dense and largely assumes Claude's competence with minimal concept over-explanation, though a few prose sections (e.g. the triage bullets and the output table) could be tightened slightly.

4 / 5

Actionability

Provides copy-paste-ready gh/api commands and script invocations throughout, covering full mode and all three targeted URL forms with concrete, executable examples.

5 / 5

Workflow Clarity

Full Mode is a clearly numbered 11-step sequence with explicit validation checkpoints (steps 6, 7, 10) and a fix/verify feedback loop with a repeat limit (step 11), satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

Well-organized into clear sections with the four bundle scripts referenced one level deep by real paths (all four exist in ./scripts/); minor gap is that the ~290-line body keeps the targeted-mode URL handling inline rather than in a reference file.

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, third-person, and clearly distinct, but omits an explicit 'Use when...' trigger clause, which caps its completeness. Adding a brief trigger clause would raise the score.

Suggestions

Append a 'Use when addressing GitHub PR review comments, unresolved review threads, or PR comment URLs' clause to satisfy the 'when' half of completeness.

Include a couple of natural synonyms ('address review comments', 'reply to PR comments') to broaden trigger-term coverage.

Keep the third-person voice and concrete action list intact — these are already strong.

DimensionReasoningScore

Specificity

Lists six concrete actions — 'source-backed triage, fixes, autogoal plan state, focused proof, replies, and thread resolution' — giving comprehensive coverage of the workflow rather than vague abstraction.

5 / 5

Completeness

A clear 'what' is present (the six-action list) but there is no 'Use when...' or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'GitHub PR review feedback', 'PR', 'review' are natural terms a user would say, but common synonyms like 'address review comments', 'reply to PR comments', or 'review threads' are absent.

4 / 5

Distinctiveness Conflict Risk

'Resolve GitHub PR review feedback' carves a clear niche 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.

Validation — 14 / 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.