CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ce-resolve-pr-feedback

Judge PR feedback centrally, apply valid fixes, and complete review conversations with publication verified. Use when addressing feedback already left on a PR, preparing local fixes for a caller to publish, or completing a saved feedback batch. Use ce-code-review for reviewing code before feedback exists.

Quality

84%

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

78%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.

A tightly written orchestration overview: it routes each mode to a real, verified reference file, embeds explicit stop/validation gates, and defines completion criteria unambiguously. The main costs are jargon-dense sentences that assume familiarity with the wider skill suite and operational mechanics being one file away from the body.

Suggestions

Soften or briefly gloss suite-specific jargon in the body ('typed decision returns, trajectory-based non-convergence, and per-root invariant keys') so the overview is parseable without reading pipeline-mode.md first.

Split the long Done paragraph into a short bulleted checklist per mode so completion criteria are scannable rather than prose-embedded.

Add one sentence in the body noting that fetch/reply/resolve helper scripts live in scripts/ and are introduced by the mode references, so the bundle's tooling is discoverable from the overview.

DimensionReasoningScore

Conciseness

The body is dense and directive with no padding about concepts Claude already knows, but a few overloaded sentences (e.g. 'it owns typed decision returns, trajectory-based non-convergence, and per-root invariant keys') and the long Done paragraph could be tightened. It sits above anchor 3 (which expects unnecessary explanation) but below anchor 5's 'every token earns its place'.

4 / 5

Actionability

Concrete directives throughout: exact mode tokens, an argument-to-mode table, the exact API endpoint 'repos/OWNER/REPO/pulls/comments/COMMENT_ID', 'gh repo view' for platform confirmation, and '- [x]' checklist-tick syntax. It falls short of anchor 5 only because the executable fetch/reply mechanics are delegated to reference files rather than being copy-paste ready in the body itself.

4 / 5

Workflow Clarity

The sequence is stated up front ('Judge fresh PR review feedback centrally, then dispatch generic subagents... Publish the fixes before replying and resolving') with explicit validation gates ('Stop before any work on unknown, repeated, or conflicting control arguments', 'confirm GitHub with `gh repo view` before fetching', 'after fresh publication proof') and a Done definition acting as a completion checklist. The batch-operation cap does not apply since publication verification is pervasive, but the end-to-end flow is distributed across mode sections rather than one explicit sequence with feedback loops, keeping it below anchor 5.

4 / 5

Progressive Disclosure

The body is a clear overview routing each execution mode and decision point to exactly the right one-level-deep reference (pipeline-mode.md, return-to-caller.md, resume.md, evaluation-rubric.md, full-mode.md, targeted-mode.md, agents/pr-comment-resolver.md — all verified to exist), and the bundle scripts are surfaced by the reference files that use them. This matches the anchor for well-signaled, appropriately split, easy-to-navigate structure.

5 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description: third-person voice, concrete actions, an explicit multi-condition 'Use when' clause, and an explicit boundary against the sibling review skill. The only room for improvement is broader natural-keyword coverage and naming the reply/resolve mechanics directly.

DimensionReasoningScore

Specificity

'Judge PR feedback centrally, apply valid fixes, and complete review conversations with publication verified' names the domain and several concrete actions, while 'preparing local fixes for a caller to publish' and 'completing a saved feedback batch' add more. It stops short of anchor 5 because replying, resolving threads, and checklist ticking are only implied by 'complete review conversations'.

4 / 5

Completeness

Both halves are explicit: the what ('Judge PR feedback centrally, apply valid fixes, and complete review conversations with publication verified') and a concrete when ('Use when addressing feedback already left on a PR, preparing local fixes for a caller to publish, or completing a saved feedback batch') listing three trigger conditions. This clearly matches anchor 5 rather than anchor 4, where the when would be less specific.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present: 'PR feedback', 'feedback already left on a PR', 'fixes', 'saved feedback batch'. Coverage is good but misses common variations such as 'review comments' or 'code review feedback', so it does not reach anchor 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct (feedback already left on a PR) and the closing boundary clause 'Use ce-code-review for reviewing code before feedback exists' explicitly de-conflicts with the closest sibling skill, giving minimal conflict risk as anchor 5 requires.

5 / 5

Total

18

/

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.

Validation — 13 / 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

Path

skills/ce-resolve-pr-feedback/SKILL.md

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.