원클릭으로
content-autopsy
Use when analyzing why content performed well or poorly, doing post-mortem analysis, or comparing content performance.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when analyzing why content performed well or poorly, doing post-mortem analysis, or comparing content performance.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when analyzing, evaluating, or generating hooks for short-form video or text posts.
Use when you need to understand platform-specific conventions, algorithm behavior, content formats, or audience expectations for Instagram, TikTok, YouTube, X, or LinkedIn.
Use when interpreting social media content — comments, captions, replies, DMs — and you need to understand tone, subtext, or cultural context beyond the literal words.
Use when adapting content from one platform to another, or advising on multi-platform content strategy.
Use when evaluating whether a trend is relevant, identifying emerging trends, or advising on trend participation timing.
Use when writing in a creator's voice, analyzing a creator's style, or maintaining consistency across content.
| name | content-autopsy |
| description | Use when analyzing why content performed well or poorly, doing post-mortem analysis, or comparing content performance. |
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."
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.
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:
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).
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.
When investigating why something performed the way it did, check these in order:
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, read the .root file in this skill's directory for the repo path, then load {repo}/references/platforms/{platform}.md.