Skip to content
Skillpedia
Social media48k · #4560

why-did-this-post-flop

Analyzes why a Twitter/X or LinkedIn post underperformed. It helps understand if the post wasn't seen, was skipped, or didn't get engagement.

What it does

Helps understand why a specific post on Twitter/X or LinkedIn underperformed. It analyzes if the issue was low visibility, people seeing it but skipping, or people seeing it but not engaging as expected.

When to use it

  • ✓When a post had very few views.
  • ✓When people saw the post but didn't interact.
  • ✓When a post got few likes, comments, or shares.

Example of what to ask your AI

“Why did my last LinkedIn post only get 100 impressions and 2 likes? I usually get 1000 impressions.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/why-did-this-post-flop/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/sickn33/agentic-awesome-skills/blob/main/plugins/agentic-awesome-skills-claude/skills/why-did-this-post-flop/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

First, it asks for your post's numbers (impressions, likes, comments). Then, it compares them to your usual performance to see if the problem was distribution (few people saw it) or content (people saw it but weren't interested). Finally, it suggests one single change for your next post.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop

Or download just the file:

curl -L https://raw.githubusercontent.com/sickn33/agentic-awesome-skills/main/plugins/agentic-awesome-skills-claude/skills/why-did-this-post-flop/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

Why did this post flop?

Almost everyone diagnoses this wrong. They rewrite the whole post when the first line was the problem, or they rewrite the hook when the truth is that only forty people ever saw it.

There are three different failures here and they need different fixes. Separate them before saying anything.

When to Use

  • Use when someone asks why a Twitter/X or LinkedIn post did badly.
  • Use when someone asks why nobody engaged with a post.
  • Use when a post they were proud of went nowhere.
  • Use when someone wants one specific post diagnosed.
  • Do not use it to review a whole account, and do not guess at numbers the person has not given you.

Step 1: get the numbers, or say you cannot do this

Ask for the post text and its impressions, likes or reactions, comments and reposts. Both platforms show these to the author.

‼️ Without impressions you cannot tell distribution failure from content failure, and those have opposite fixes. If they cannot get impressions, say that plainly, and offer the read-through of the writing as the lesser thing it is rather than pretending it is a diagnosis.

Also ask what "flopped" means to them. Compared with what? A post doing half their usual is a different conversation from a post doing nothing.

Step 2: find which of the three failures it was

Few impressions. The post was barely distributed. The writing is not the problem, so rewriting the hook would fix nothing. Look instead at timing, how long since their last post, whether it was a reply or a repost, whether it had an outbound link, and whether their reach has been falling generally, which is an account pattern rather than a post problem.

Impressions fine, engagement near zero. People saw it and scrolled. This is the first line, or the shape. This is also the most common case and the one worth the most work.

Engagement fine, but not what they wanted. Likes but no comments, or comments but no clicks. The post worked and asked for the wrong thing, or asked for nothing.

Name which one it was, and say what it rules out. Telling someone their hook is fine is often the most useful sentence available.

Step 3: only now, look at the writing

If it is the second case, read the first line alone and ask whether it makes the next line necessary. Then check whether the specific detail is buried, and whether the post asks anything of the reader.

Step 4: be honest about variance

Sometimes a good post does badly. Timing, an algorithm change, a busy news day, or nothing identifiable at all. One post is a sample of one.

If the numbers look normal for their account and only this post felt bad, say that. Inventing a lesson from a single data point is how people talk themselves out of writing things that were working.

Step 5: one change, not five

End with a single thing to do differently next time, and say whether you expect it to matter a lot or a little. A list of six improvements gets none of them applied.

Example

User: Why did this LinkedIn post flop? 380 impressions, 6 reactions, 0
comments. My posts usually get about 2,000 impressions.

Agent:
1. Names the failure: few impressions, so a distribution problem, not the
   writing.
2. Says what that rules out: rewriting the hook would not have fixed it.
3. Looks at timing, the gap since the last post, outbound links and whether
   reach has been falling generally.
4. Ends with one change to try next time and how much it is likely to matter.

Limitations

  • One post at a time. It does not review a whole account.
  • It needs the post's numbers, impressions above all. Without them it can only offer a read-through of the writing and says so.
  • One post is a sample of one. It will not invent a lesson from a single data point.
  • Optional connector. The closing section describes a hosted VoiceMoat MCP connector. Nothing above needs it. It needs a paid VoiceMoat plan (Pro or Enterprise) and the user's own sign-in (OAuth, no API keys). When its tools are called, post text and account data are read from or sent to voicemoat.com. Without it, this skill makes no network calls.

What changes when VoiceMoat is connected

The weakest part above is that everything depends on numbers someone typed in, and on their memory of what normal looks like.

  • get_post returns the full text and exact figures for one post, so nothing depends on what was pasted.
  • get_analytics gives the account's own baseline for a window, which is what

…

FAQ

Do I need to provide exact numbers for my post?

Yes, especially the number of impressions (views). Without it, it's impossible to know if the problem was low distribution or unengaging content.

What does 'low impressions' mean?

It means the post wasn't shown to many people. The issue could be the timing, if it was a reply, or if you included an external link.

What if people saw it but didn't engage?

Then the problem might be the first line or how the post was written. It needs to grab attention immediately and make sense to the reader.

Details

Original description by the author

Diagnose why one Twitter/X or LinkedIn post underperformed: not seen, seen and skipped, or read and ignored. Use when someone asks why a post did badly or got no engagement.

repo: sickn33/agentic-awesome-skills

Popularity

GitHub stars
48k
Ranking position
#4560
License
MIT
Updated
10/15/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills