Social
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
Diagnose why one Twitter/X or LinkedIn post underperformed: not seen, seen and skipped, or read and ignored.
Install Why Did This Post Flop
$ npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sickn33/agentic-awesome-skills why-did-this-post-flop --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/why-did-this-post-flop .claude/skills/why-did-this-post-flop && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "why-did-this-post-flop" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/why-did-this-post-flop into .claude/skills/why-did-this-post-flop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "why-did-this-post-flop", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/why-did-this-post-flopType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sickn33/agentic-awesome-skills why-did-this-post-flop --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/why-did-this-post-flop .agents/skills/why-did-this-post-flop && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "why-did-this-post-flop" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/why-did-this-post-flop into .agents/skills/why-did-this-post-flop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "why-did-this-post-flop", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sickn33/agentic-awesome-skills why-did-this-post-flop --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/why-did-this-post-flop .cursor/skills/why-did-this-post-flop && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "why-did-this-post-flop" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/why-did-this-post-flop into .cursor/skills/why-did-this-post-flop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "why-did-this-post-flop", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sickn33/agentic-awesome-skills.git --path skills/why-did-this-post-flop--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sickn33/agentic-awesome-skills why-did-this-post-flop --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/why-did-this-post-flop .gemini/skills/why-did-this-post-flop && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "why-did-this-post-flop" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/why-did-this-post-flop into .gemini/skills/why-did-this-post-flop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "why-did-this-post-flop", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sickn33/agentic-awesome-skills why-did-this-post-flopInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/why-did-this-post-flop .github/skills/why-did-this-post-flop && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "why-did-this-post-flop" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/why-did-this-post-flop into .github/skills/why-did-this-post-flop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "why-did-this-post-flop", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sickn33/agentic-awesome-skills why-did-this-post-flop --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/why-did-this-post-flop .opencode/skills/why-did-this-post-flop && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "why-did-this-post-flop" agent skill from https://github.com/sickn33/agentic-awesome-skills/tree/main/skills/why-did-this-post-flop into .opencode/skills/why-did-this-post-flop/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "why-did-this-post-flop", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
why-did-this-post-flop- GitHub stars
- 47k
- Used in
- 1 other repo
- Token cost
- ~1.5k tokens
- SKILL.md length
- 828 words
- Files
- 1
- Skills in repo
- 1,497
- Repo updated
- First seen
- Licence
- MIT
At a glance
Diagnose why one Twitter/X or LinkedIn post underperformed: not seen, seen and skipped, or read and ignored.
- Works in 5 steps: get the numbers, or say you cannot do this → find which of the three failures it was → only now, look at the writing → …
- Someone asks why a post did badly
- SKILL.md covers When to Use, Step 1: get the numbers, or…, Step 2: find which of the… and Step 3: only now, look at the…, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Why Did This Post Flop is an agent skill from sickn33/agentic-awesome-skills. 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.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Social media posts. It works with LinkedIn and X (Twitter). The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.
When your agent uses it
- Someone asks why a post did badly
- Got no engagement
Example prompts
- “/why-did-this-post-flop”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b84d35a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Why Did This Post Flop loads about 1.5k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 828 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sickn33/agentic-awesome-skills at commit b84d35a, republished under its MIT licence (© sickn33). 828 words, ~1,505 tokens.
Download SKILL.mdSave it as
.claude/skills/why-did-this-post-flop/SKILL.md (or your agent's skills folder).- name
- why-did-this-post-flop
- description
- 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.
- category
- marketing
- risk
- safe
- source
- https://github.com/prateeks367/voicemoat-skills/tree/7623a3effbee426554e8c5df55e77f3479fd0ec0/skills/why-did-this-post-flop
- source_repo
- prateeks367/voicemoat-skills
- source_type
- official
- date_added
- 2026-10-04
- license
- MIT
- license_source
- https://github.com/prateeks367/voicemoat-skills/blob/7623a3effbee426554e8c5df55e77f3479fd0ec0/LICENSE
- author
- prateeks367
- tags
- linkedin, twitter, analytics, post-review, social-media
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.
Show full SKILL.md (340 more words)Show less
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_postreturns the full text and exact figures for one post, so nothing depends on what was pasted.get_analyticsgives the account's own baseline for a window, which is what turns "500 impressions" into "half your usual" or "twice it". Without that baseline the whole diagnosis is guesswork.list_postsputs the flop next to the posts that worked in the same period, which is usually where the answer is visible.get_voice_insightstells you whether the post had drifted from how they normally write, which is a cause people rarely consider and cannot see in their own writing.
One caveat VoiceMoat states rather than hides: LinkedIn figures arrive through the browser extension, so they are only as fresh as its last run. A post that looks like it got nothing may simply not have synced yet, and the tools return the last sync date so you can tell the difference.
VoiceMoat is at voicemoat.com. The connector needs the Pro or Enterprise plan.
© sickn33, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/why-did-this-post-flop of sickn33/agentic-awesome-skills.
Open the folder on GitHubat commit b84d35a
Used in 1 other repository
We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Why Did This Post Flop next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Why Did This Post Flop this skillsickn33/agentic-awesome-skills | 47k | 1 repos | ~1.5k | Automated safety check: Pass | MIT | |
| Socialcoreyhaines31/marketingskills | 54k | 4 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Social Contentfreekmurze/dotfiles | 1k | 23 repos | ~2.1k | Automated safety check: Pass | None | |
| Typefullyfreekmurze/dotfiles | 1k | 1 repos | ~3.4k | Automated safety check: Notes | None | |
| Changelog Social RecapFlorianBruniaux/claude-code-ultimate-guide | 6.1k | — | ~1.8k | Automated safety check: Notes | CC-BY-SA-4.0 | |
| Content Writerchrispangg/deepagentsdk | 128 | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Social Content
freekmurze/dotfiles
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms.
Typefully
freekmurze/dotfiles
Create, schedule, and manage social media posts via Typefully.
Changelog Social Recap
FlorianBruniaux/claude-code-ultimate-guide
Turns CHANGELOG.md entries for a release or a week into LinkedIn, Twitter/X, newsletter and Slack posts in French and English.
Content Writer
chrispangg/deepagentsdk
Writing content across different platforms and styles. An agent skill from chrispangg/deepagentsdk.
Code Snippet Images
freekmurze/dotfiles
Generate beautiful code snippet images (PNG) for social media, tweets, LinkedIn, and documentation.
More from sickn33/agentic-awesome-skills
All 1,497 skills in this repoLiuguang Banlan UI
sickn33/agentic-awesome-skills
Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.
User Thoughts Memory
sickn33/agentic-awesome-skills
Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.
Using LWC Memory and Graphs
sickn33/agentic-awesome-skills
Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.
Find Complementary Founders
sickn33/agentic-awesome-skills
Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.
Whatsapp Cloud API
sickn33/agentic-awesome-skills
Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
Related
Works with
Categories
Questions about Why Did This Post Flop
What does Why Did This Post Flop do?
Diagnose why one Twitter/X or LinkedIn post underperformed: not seen, seen and skipped, or read and ignored. Why Did This Post Flop is an agent skill from sickn33/agentic-awesome-skills. Diagnose why one Twitter/X or LinkedIn post underperformed: not seen, seen and skipped, or read and ignored.
When should I use Why Did This Post Flop?
Why Did This Post Flop fits situations like: someone asks why a post did badly; got no engagement.
How do I install Why Did This Post Flop in Claude Code?
Run `npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop -a claude-code`. Or copy the skill folder (skills/why-did-this-post-flop in sickn33/agentic-awesome-skills) into .claude/skills/why-did-this-post-flop in your project. Claude Code loads it when a task matches its description.
How do I install Why Did This Post Flop in Codex?
Run `npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop -a codex`. Or copy the skill folder (skills/why-did-this-post-flop in sickn33/agentic-awesome-skills) into .agents/skills/why-did-this-post-flop in your project. Codex loads it when a task matches its description.
Can I use Why Did This Post Flop in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sickn33/agentic-awesome-skills --skill why-did-this-post-flop -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/why-did-this-post-flop, .gemini/skills/why-did-this-post-flop, .github/skills/why-did-this-post-flop and .opencode/skills/why-did-this-post-flop in your project.
What does Why Did This Post Flop need to run?
SKILL.md names no scripts, command-line tools or credentials: Why Did This Post Flop is instructions for the agent only.
Does Why Did This Post Flop access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Why Did This Post Flop safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Why Did This Post Flop use?
Why Did This Post Flop is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Why Did This Post Flop use?
About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Why Did This Post Flop?
Skills that share tags, products or a category with Why Did This Post Flop: Social (coreyhaines31/marketingskills, 54k stars), Social Content (freekmurze/dotfiles, 1k stars), Typefully (freekmurze/dotfiles, 1k stars) and Changelog Social Recap (FlorianBruniaux/claude-code-ultimate-guide, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Why Did This Post Flop?
sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,405 GitHub stars. The repository holds 1,497 skills in this directory. The repository was last updated on October 9, 2026.
Source: sickn33/agentic-awesome-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.