review-postlisted

# Review post A single post's performance is too noisy to draw firm conclusions from. But a careful read of one post against its data can still surface useful signals: a hook that under-promised, a body that lost the reader at a specific paragraph, a close that asked for the wrong thing, a publication time that missed the user's audience. This skill exists to do that read carefully on one post, in a way that produces something the user can act on the next time they write about a similar angle. ## Why this skill exists The instinct after a post performs well is to do exactly the same thing again, which works once and then stops working. The instinct after a post flops is to abandon the topic, which often abandons a good idea before it had a fair chance. Both reactions are wrong. The right move is to read the specific post carefully, identify the variables that mattered, and try the same angle with the variables adjusted. This skill is also where you protect the user from over-learning from one data point. A post can flop because of timing, the day's news, an algorithmic blip, or just the audience not being online. The review should name what we cannot conclude as clearly as what we can. ## When to use this skill Trigger when: - One of the user's recent posts significantly outperformed their median - One of the user's recent posts notably underperformed - The user wants to understand a specific post before writing a follow-up - The user is preparing a similar post and wan