CtrlK
BlogDocsLog inGet started
Tessl Logo

ce-resolve-pr-feedback

Resolve PR review feedback. Use when addressing feedback already left on a PR. Not for reviewing the code before feedback exists; that is ce-code-review.

68

Quality

83%

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

85%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 content is a well-structured operational overview that defers per-mode detail to one-level-deep reference files, includes explicit validation/verify checkpoints in its workflow, and gives concrete commands and endpoints. It is slightly dense in a few prose sections but highly actionable.

DimensionReasoningScore

Conciseness

The body is dense and operational with no padding about concepts Claude already knows, though a few prose blocks (pipeline-mode authority, escalations) could be tightened. It is efficient with only minor trimmable instances, landing above the 3-anchor but short of the fully-lean 5.

4 / 5

Actionability

Provides concrete, executable guidance: named scripts (get-pr-comments, resolve-pr-thread), a specific GraphQL endpoint path, `gh repo view` as a positive signal, and URL-parsing details, with detailed steps delegated to reference files. Minor gaps (e.g., no inline script invocation examples) keep it just below the copy-paste-ready 5.

4 / 5

Workflow Clarity

Full mode lays out a 9-step sequence including explicit validate and verify checkpoints with a feedback loop, plus a Success Criteria checklist and a mode-detection table. This matches the 5-anchor's clear sequence with explicit validation and error-recovery feedback loops.

5 / 5

Progressive Disclosure

The body is a clear overview with well-signaled, one-level-deep references (full-mode.md, targeted-mode.md, evaluation-rubric.md, agents/pr-comment-resolver.md), all of which exist in the bundle, with detail appropriately split out. This matches the 5-anchor's clear overview with easy navigation.

5 / 5

Total

18

/

20

Passed

Description

82%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 well-constructed: it states what the skill does, when to use it, and explicitly distinguishes it from the related ce-code-review skill. Its only weakness is that the description names the headline action without enumerating the full evaluate/fix/reply/resolve workflow.

Suggestions

Optionally expand the headline action to surface the full workflow (e.g., 'Evaluate, fix, reply, and resolve PR review feedback') to lift specificity toward the 5-anchor.

DimensionReasoningScore

Specificity

Names the domain and a primary concrete action ('Resolve PR review feedback') but does not enumerate the fuller fix/reply/resolve scope in the description itself, so coverage is not comprehensive. It sits at the '1-2 concrete actions' anchor rather than the 4-anchor's 'several specific actions'.

3 / 5

Completeness

Explicitly answers both what ('Resolve PR review feedback') and when ('Use when addressing feedback already left on a PR') with concrete trigger phrases, plus an explicit boundary clause. This matches the 5-anchor's clear what-and-when with concrete triggers.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('PR review feedback', 'feedback already left on a PR') with good keyword coverage, though it omits common synonyms like 'review comments' or 'address comments'. This is above the 3-anchor's partial coverage but just short of comprehensive synonym coverage at 5.

4 / 5

Distinctiveness Conflict Risk

The explicit 'Not for reviewing the code before feedback exists; that is ce-code-review' carve-out gives it a clear niche with minimal conflict risk against the sibling review skill, matching the 5-anchor.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 deeper-than-1-level

Warning

Total

13

/

16

Passed

Repository
EveryInc/compound-engineering-plugin
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.