analysis-memo-writerlisted

An analysis fails at the last step more often than at any earlier one. The query was right, the caveat was known, and the writeup said "engagement drove retention" because that sentence was shorter. This skill drafts that writeup from findings and figures you supply, in one fixed shape, with the sections people delete under deadline made mandatory. It uses only the numbers you give it, so it can be trusted with a result nobody has published yet, and it needs no data connection or code execution: it runs the same on claude.ai, in Claude Code, and in Claude Cowork. ## When to use this skill - The analysis is finished and now has to be read by a product lead, a finance partner, or an exec. - A result is genuinely uncertain and the writeup has to say so without becoming unreadable. - You are handing an analysis to someone who will act on it and you want the conditions on it written down. - A previous writeup got overinterpreted and the next one needs a "what this is not" section. > [!NOTE] > This skill writes; it does not compute. Every number in the draft comes from what you paste. If you ask for a percentage change and give only one of the two figures, it asks for the other rather than deriving something plausible. If your evidence is observational, the draft says "associated with" and explains what would be needed to say "caused". Neither behavior is negotiable and neither can be overridden by asking for a stronger conclusion. ## Instructions 1. **Collect the inputs befor