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

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%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, well-sequenced behavioral skill with concrete templates and validation checkpoints. Its main weakness is redundancy across sections (Real Examples duplicates earlier material) and a monolithic structure.

Suggestions

Remove or compress the 'Real Examples' section, since its scenarios already appear in 'Handling Unclear Feedback' and 'YAGNI Check', to reduce token redundancy.

Consolidate the repeated 'You're absolutely right!' / 'Great point!' prohibitions into a single forbidden-phrases list referenced once instead of restating across multiple sections.

Consider moving the long example transcripts into a separate EXAMPLES.md reference to move progressive disclosure from a monolithic file toward a one-level-deep structure.

Dimension	Reasoning	Score
Conciseness	Mostly terse and imperative, but the Real Examples section reuses scenarios already shown (Fix 1-6, YAGNI, 'You're absolutely right') and several phrases recur across sections, adding noticeable redundancy that could be trimmed; not quite the 'minor instances' of the level-4 anchor.	3 / 5
Actionability	Provides concrete ✅/❌ response templates, specific decision trees (the 5-point external-reviewer checklist), and a copy-paste-ready `gh api .../replies` command covering the common cases, matching the fully-actionable top anchor for an instruction skill.	5 / 5
Workflow Clarity	Clear sequenced workflows (6-step Response Pattern, Implementation Order) with explicit validation checkpoints ('STOP - do not implement anything yet', 'Test each fix individually', 'Verify no regressions') and a feedback loop for unclear items, matching the top anchor.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections and self-contained with no external references needed, but it is a ~200-line monolithic file with no one-level-deep references, so it sits just below the ideal split-and-navigate top anchor.	4 / 5
	Total	17 / 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.

A strong description with an explicit 'Use when...' trigger, clear domain, and concrete behavioral stance. It is slightly less specific in enumerating concrete actions than the top specificity anchor, but otherwise excellent.

Dimension	Reasoning	Score
Specificity	Names the domain (code review feedback) and a couple of concrete actions ('verification', 'before implementing suggestions') but does not enumerate multiple specific capabilities, so it sits at the 'names domain and 1-2 concrete actions' anchor rather than the comprehensive level above.	3 / 5
Completeness	Explicitly answers both what ('requires technical rigor and verification, not performative agreement or blind implementation') and when ('Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('code review feedback', 'implementing suggestions', 'feedback seems unclear or technically questionable'); good coverage with a few common variants missing, so just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	'Receiving code review feedback' is a clear, narrow niche with distinct triggers and minimal overlap risk with other skills, matching the top anchor.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: skills/receiving-code-review/SKILL.md
Commit: b36e082

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.