CtrlK
BlogDocsLog inGet started
Tessl Logo

receiving-code-review

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

62

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/receiving-code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 highly actionable behavioral skill with concrete do/don't phrasing, explicit sequencing, and clear checkpoints. The weaknesses are redundancy across sections (repeated examples and forbidden phrases, a mistakes table that restates earlier rules) and a monolithic ~200-line body where some example material could be split out. No bundle files exist, so navigation is entirely internal and clean.

Suggestions

Deduplicate examples: the 'Fix 1-6' unclear-item scenario appears in both 'Handling Unclear Feedback' and 'Real Examples' — keep one; likewise merge the forbidden-phrase list in 'Acknowledging Correct Feedback' with 'Forbidden Responses'.

Trim the 'Common Mistakes' table or the 'your human partner's rule' quotes, since both restate guidance already given in earlier sections.

Add an explicit error-recovery loop after 'Test each fix individually' (e.g., 'If a fix breaks a test: revert it, re-verify the reviewer's premise, then re-ask') to earn full workflow validation credit.

DimensionReasoningScore

Conciseness

The body mostly avoids explaining things Claude already knows and stays lean, but has noticeable repetition: the 'Fix 1-6' / 'items 1,2,3,6' unclear-item example appears twice (Handling Unclear Feedback and Real Examples), 'You're absolutely right!' is forbidden in both Forbidden Responses and Acknowledging Correct Feedback, the Common Mistakes table restates earlier sections, and 'your human partner's rule' quotes pad two sections. This matches anchor 3 (mostly efficient but could be tightened) rather than 2, since no concept-explanation padding exists.

3 / 5

Actionability

As an instruction-only skill the guidance is fully concrete: a 6-step response pattern, exact forbidden phrases with exact replacement phrasing, copy-adaptable correct/incorrect example replies covering the common cases (unclear items, wrong suggestions, YAGNI, being wrong after pushback), and a copy-paste-ready GitHub command ('gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies'). This matches the anchor 5 example coverage.

5 / 5

Workflow Clarity

The sequence is explicit (READ→UNDERSTAND→VERIFY→EVALUATE→RESPOND→IMPLEMENT, plus Implementation Order: clarify first, blocking→simple→complex) with explicit STOP-and-ask checkpoints and validation directives ('Test each fix individually', 'Verify no regressions'). It falls short of anchor 5 because error-recovery loops after a failed test are implied rather than spelled out, and the multi-item batch flow's validation is directive without a how.

4 / 5

Progressive Disclosure

Sections are clear, well-ordered, and easy to navigate with no buried or nested references, and no bundle files exist to mislink. Since the skill exceeds 50 lines, the simple-skill exception does not apply; some content (Real Examples, response templates) could arguably live in a reference file, which keeps this at anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

70%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 with an explicit, well-scoped trigger clause and a distinct niche. The main gap is that capabilities are expressed as principles ('technical rigor and verification') rather than concrete actions, and a few natural trigger variations are absent. Voice is appropriately imperative/third-person with no first- or second-person penalty.

DimensionReasoningScore

Specificity

The description names the domain ('receiving code review feedback, before implementing suggestions') and 1-2 actions ('requires technical rigor and verification', avoiding 'blind implementation'), but does not list several concrete capabilities like verifying against the codebase, clarifying unclear items, or pushing back with reasoning. It fits anchor 3 rather than 4, which requires multiple specific listed actions.

3 / 5

Completeness

The 'when' is explicit and well-scoped ('Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable'), and the 'what' is present ('requires technical rigor and verification, not performative agreement or blind implementation'). It is not a 5 because the what-side is framed as an approach rather than concrete stated capabilities.

4 / 5

Trigger Term Quality

Natural phrases like 'code review feedback', 'implementing suggestions', 'unclear', and 'technically questionable' are terms users would actually say. It falls short of anchor 5 because common variations such as 'review comments', 'addressing feedback', or 'PR review comments' are missing.

4 / 5

Distinctiveness Conflict Risk

The receiving-feedback framing carves a distinct niche apart from skills that perform or write code reviews. Minor overlap risk remains with closely related review/PR-reply skills, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
obra/superpowers
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.