Other vs Testing · both proven

internal-comms vs receiving-code-review

Both skills were run through Claude twice: once on a fixed brief without the skill, once with it. The briefs differ because each is written for the job the skill claims to do, so compare each skill against its own baseline, then decide which difference matters for your work. They are in different categories, so this is a choice of job, not a head-to-head on the same job.

internal-comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

Category: Other
Source: anthropics/skills
License: Not stated
Proof model: claude-opus-5-5
Brief: “Write this week's status update for the Checkout Redesign project as a single HTML page for the leadership channel. Facts to use: the new cart page shipped to 10% of traffic on Tuesday; conversion in the test group is up 2.1% so far; the payments team is two days late on the saved-cards work; a legal review of the new terms copy is still open; launch to 100% is planned for the 30th if the saved-cards work lands by Friday. Keep it short enough to read in a minute.”
Skill commit: dbd4588

Without the skillWith internal-comms

⇆

Without, runWith internal-comms, run3 independent runs per side, none selected by hand.

Download the with-skill page

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

Category: Testing
Source: obra/superpowers
License: MIT
Proof model: claude-opus-5-5
Brief: “I received this code review on my pull request that adds caching to our product API. Decide what to do with each comment and present your responses and planned changes as a single HTML page. 1. "Cache TTL of 24h is too long, prices change during the day." 2. "Use Redis instead of the in-memory Map so all 4 instances share the cache." 3. "Rename getProd to getProduct." 4. "You should rewrite this whole module in TypeScript." 5. "The cache key ignores the currency query param, so EUR users can get USD prices." 6. "Add a test."”
Skill commit: 2ce8aa1

Without the skillWith receiving-code-review

⇆

Without, runWith receiving-code-review, run3 independent runs per side, none selected by hand.

Download the with-skill page

We don’t pick a winner for you: the pages are the evidence. Both proofs can be repeated with the brief, model and commit shown above. See alternatives to internal-comms or alternatives to receiving-code-review.