New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Analyzing why content performed well or poorly

Content autopsy

by scrollmark · MIT license · ★ 15 on GitHub

Content autopsy cover

Use when analyzing why content performed well or poorly, doing post-mortem analysis, or comparing content performance.

---
name: content-autopsy
description: Use when analyzing why content performed well or poorly, doing post-mortem analysis, or comparing content performance.
---

# Content Autopsy

This is an investigation, not a report card. The goal is understanding what happened and why — framed as "here's what likely drove this" rather than "this was good/bad."

## Signal vs. Noise

A single post's performance is noisy. External factors can dominate: time of day, platform outages, competing events, algorithmic lottery. One viral post doesn't mean you cracked the code. One flop doesn't mean the content was bad.

Look for patterns across multiple posts before drawing conclusions. If someone asks about a single post, analyze it but flag that single-post analysis is inherently uncertain.

## Metric Interpretation

Different metrics tell different stories. Read them in layers:

Overview

This is an investigation, not a report card. The goal is understanding what happened and why — framed as "here's what likely drove this" rather than "this was good/bad."

Manual install (npx, ZIP)
Claude Codenpx skills add scrollmark/social-skills --skill content-autopsy -g -a claude-code
Claude Code (degit)npx degit scrollmark/social-skills/skills/content-autopsy#master ~/.claude/skills/content-autopsy
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md3.6 KB
Read SKILL.md here
scrollmark/master1 file shown
SKILL.md
Show the full text54 lines

Content Autopsy

This is an investigation, not a report card. The goal is understanding what happened and why — framed as "here's what likely drove this" rather than "this was good/bad."

Signal vs. Noise

A single post's performance is noisy. External factors can dominate: time of day, platform outages, competing events, algorithmic lottery. One viral post doesn't mean you cracked the code. One flop doesn't mean the content was bad.

Look for patterns across multiple posts before drawing conclusions. If someone asks about a single post, analyze it but flag that single-post analysis is inherently uncertain.

Metric Interpretation

Different metrics tell different stories. Read them in layers:

Reach / impressions — how far did the algorithm push this? High reach means the platform thought it was worth distributing. Low reach on otherwise good content usually means the hook didn't convert or the initial audience didn't engage fast enough.

Engagement rate — of people who saw it, how many interacted? Break this down by type:

  • Likes are low-effort (cheap signal)
  • Comments are medium-effort (stronger signal, especially longer ones)
  • Saves and shares are high-intent (strongest signal — "I want this later" or "someone else needs to see this")

Retention / watch time — for video, where did people drop off? The drop-off point often reveals the problem. Mass drop-off at 3 seconds = hook failed. Drop-off in the middle = pacing issue. Drop-off before the end = too long or lost the thread.

Follow-through — did engagement translate to follows, profile visits, link clicks? High engagement but no follows = entertaining but not compelling enough to commit to. Save-heavy but low likes = useful reference content (often undervalued).

Performance Patterns

Spike-and-die — went semi-viral then flatlined. Usually means the content appealed broadly but didn't connect with a retainable audience. Common with trending audio or meme formats where the trend did the work, not the creator's unique angle.

Slow burn — modest initially, grows over days or weeks. Common with search-discoverable content (YouTube especially) or content that gets shared in group chats over time. Often the most valuable content a creator makes.

Second wave — initial modest performance, then the algorithm resurfaces it. Can be triggered by a share from a larger account, sudden trend alignment, or the algorithm's own re-testing cycle.

Save-heavy — low visible engagement but high saves. The content is reference-worthy. This often looks like underperformance but is actually high-quality signal — people are bookmarking it to come back to.

Causal Analysis

When investigating why something performed the way it did, check these in order:

  1. Hook — did people stay past the first few seconds? If not, nothing else matters.
  2. Topic — was there demand for this? Was the timing right relative to trends or conversations?
  3. Format — was it native to the platform? Right length, right aspect ratio, right pacing?
  4. Audience match — did it reach the right people? Broad distribution to the wrong audience tanks engagement rate.
  5. Timing — posting time, day of week, competing with a major event?

It's usually one or two of these, not all five. Start with the most likely culprit based on the metrics.

For platform-specific metric interpretation, load references/platforms/{platform}.md from this skill's own directory.

1---
2name: content-autopsy
3description: Use when analyzing why content performed well or poorly, doing post-mortem analysis, or comparing content performance.
4---
5 
6# Content Autopsy
7 
8This is an investigation, not a report card. The goal is understanding what happened and why — framed as "here's what likely drove this" rather than "this was good/bad."
9 
10## Signal vs. Noise
11 
12A single post's performance is noisy. External factors can dominate: time of day, platform outages, competing events, algorithmic lottery. One viral post doesn't mean you cracked the code. One flop doesn't mean the content was bad.
13 
14Look for patterns across multiple posts before drawing conclusions. If someone asks about a single post, analyze it but flag that single-post analysis is inherently uncertain.
15 
16## Metric Interpretation
17 
18Different metrics tell different stories. Read them in layers:
19 
20**Reach / impressions** — how far did the algorithm push this? High reach means the platform thought it was worth distributing. Low reach on otherwise good content usually means the hook didn't convert or the initial audience didn't engage fast enough.
21 
22**Engagement rate** — of people who saw it, how many interacted? Break this down by type:
23- Likes are low-effort (cheap signal)
24- Comments are medium-effort (stronger signal, especially longer ones)
25- Saves and shares are high-intent (strongest signal — "I want this later" or "someone else needs to see this")
26 
27**Retention / watch time** — for video, where did people drop off? The drop-off point often reveals the problem. Mass drop-off at 3 seconds = hook failed. Drop-off in the middle = pacing issue. Drop-off before the end = too long or lost the thread.
28 
29**Follow-through** — did engagement translate to follows, profile visits, link clicks? High engagement but no follows = entertaining but not compelling enough to commit to. Save-heavy but low likes = useful reference content (often undervalued).
30 
31## Performance Patterns
32 
33**Spike-and-die** — went semi-viral then flatlined. Usually means the content appealed broadly but didn't connect with a retainable audience. Common with trending audio or meme formats where the trend did the work, not the creator's unique angle.
34 
35**Slow burn** — modest initially, grows over days or weeks. Common with search-discoverable content (YouTube especially) or content that gets shared in group chats over time. Often the most valuable content a creator makes.
36 
37**Second wave** — initial modest performance, then the algorithm resurfaces it. Can be triggered by a share from a larger account, sudden trend alignment, or the algorithm's own re-testing cycle.
38 
39**Save-heavy** — low visible engagement but high saves. The content is reference-worthy. This often looks like underperformance but is actually high-quality signal — people are bookmarking it to come back to.
40 
41## Causal Analysis
42 
43When investigating why something performed the way it did, check these in order:
44 
451. **Hook** — did people stay past the first few seconds? If not, nothing else matters.
462. **Topic** — was there demand for this? Was the timing right relative to trends or conversations?
473. **Format** — was it native to the platform? Right length, right aspect ratio, right pacing?
484. **Audience match** — did it reach the right people? Broad distribution to the wrong audience tanks engagement rate.
495. **Timing** — posting time, day of week, competing with a major event?
50 
51It's usually one or two of these, not all five. Start with the most likely culprit based on the metrics.
52 
53For platform-specific metric interpretation, load `references/platforms/{platform}.md` from this skill's own directory.
54 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 15
Checked
Source
scrollmark/social-skills ↗
Creator
scrollmark · 3 listings
View creator

Similar skills

See all →
SkillReverse engineer native, managed, Electron/JavaScriptREAmorluto/rea · by morlutoReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.★ 316k GitHub starsSkillBrainstorms ideas into designs before any creative workBrainstorming Ideas Into Designsobra/superpowers · by obraYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.★ 290k GitHub starsSkillRequires technical rigor and verificationCode Review Receptionobra/superpowers · by obraUse 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★ 290k GitHub starsSkillDiagnosis loop for hard bugs and performance regressionsDiagnosing bugsmattpocock/skills · by mattpocockDiagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.★ 267k GitHub starsSkillImplement the result of /to-spec and /to-tickets in codeImplement specmattpocock/skills · by mattpocockImplement the result of /to-spec and /to-tickets in code.★ 267k GitHub starsSkillWriting a PR bodymattpocock/skills · by mattpocockUse when writing a PR body.★ 267k GitHub stars

More from scrollmark