← ClaudeAtlas

performance-optimizerlisted

Post-mortems a piece of content and produces the next iteration, not just an explanation. It isolates the weakest link, proposes single-variable A/B tests, and applies a double-down rule when something wins. Use when someone asks "why did this flop", "why did this win", "help me optimize/improve my content", "set up an A/B test", or wants a post-mortem. Works with any capable model.
moses607/socialforge · ★ 1 · API & Backend · score 72
Install: claude install-skill moses607/socialforge
# Performance Optimizer A post that flopped is a free experiment — but only if you extract one lesson and ship the next test. Optimization is not "make it better everywhere"; it is finding the single weakest link, changing ONE variable, and letting the numbers vote. Content has four links in series — Hook, Body/Retention, CTA/Conversion, Distribution — and the chain breaks at its weakest point. Fixing anything other than the weakest link is motion without progress. Winners are not luck to admire; they are formats to industrialize. Every result routes to one of three verbs: KILL, ITERATE, or SCALE. ## 1. Post-mortem — isolate the weakest link 1. Pull the funnel: hook rate, retention/avg watch, saves+shares per view, follows-per-view, reach. 2. Find the FIRST metric below the account's median — that is the weakest link. Attribute the outcome to it, not to a vibe. 3. Weak hook rate -> packaging problem (first frame, first line, title, thumbnail). Good hook + retention cliff -> body problem (pacing, payoff, structure). Good retention + low saves/follows -> CTA/value problem. Everything fine + low reach -> timing, niche-fit, or an unlucky test batch (re-test before concluding). 4. State ONE root cause in a sentence. If you can't, you're guessing — get more data. ## 2. Design single-variable A/B tests 1. Change exactly ONE variable per test so the result is attributable. Multi-variable "improvements" teach nothing. 2. Highest-leverage variables in order: hook line, first frame