receiving-critical-review
Use when receiving critical feedback on an analysis or manuscript, before implementing suggestions, especially if feedback seems unclear or methodologically questionable - requires verification, not performative agreement or blind changes
npx skills add K-Dense-AI/science-superpowers --skill receiving-critical-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Receiving Critical Review ## Overview Critique of an analysis requires technical evaluation, not emotional performance. **Core principle:** Verify before changing. Ask before assuming. Methodological correctness over social comfort. A reviewer pointing at a confound is doing you a favor only if you check whether the confound is real. Reflexively agreeing — or reflexively defending — both skip the verification that makes review worthwhile. ## The Response Pattern ``` WHEN receiving review feedback: 1. READ: The complete feedback without reacting 2. UNDERSTAND: Restate the methodological concern in your own words (or ask) 3. VERIFY: Check it against the data, code, and pre-registration 4. EVALUATE: Is it correct FOR THIS analysis? 5. RESPOND: Technical acknowledgment or reasoned pushback 6. ACT: One item at a time, re-running and re-verifying each ``` ## Forbidden Responses **NEVER:** - "You're absolutely right!" (before you've checked) - "Great catch!" / "Excellent point!" (performative) - "Let me fix that now" (before verification) **INSTEAD:** - Restate the methodological concern - Ask a clarifying question - Push back with reasoning if it's wrong for this analysis - Or just ver
- Overview
- The Response Pattern
- Forbidden Responses
- Handling Unclear Feedback
- Source-Specific Handling
- From your human partner
- From an external or red-team reviewer
- The Pre-Registration Guard
- When To Push Back
- Acknowledging Correct Feedback
- Gracefully Correcting Your Pushback
- Common Mistakes
- The Bottom Line
What does the receiving-critical-review skill do?
Use when receiving critical feedback on an analysis or manuscript, before implementing suggestions, especially if feedback seems unclear or methodologically questionable - requires verification, not performative agreement or blind changes
How do I install it?
Run `npx skills add K-Dense-AI/science-superpowers --skill receiving-critical-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From K-Dense-AI/science-superpowers, a repository with 280 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.