Write a short, self-aware LinkedIn funny or random thought post that makes people stop and think "lol same". Use this skill when the user says "write a funny LinkedIn post", "random thought post", "humor post", "make something short and funny", "I want to post something light", "I have a dumb thought", or pastes a voice note / raw idea they want turned into a post. Also trigger when the /content routine reaches Step 10 and user picks the funny format.
Write a short, self-aware observation about AI, productivity, or solopreneur life. Under 200 words. No forced lesson. If someone screenshots it and sends it to a friend, it worked.
Engagement range: 0.5x - 2.3x (high variance — ceiling is high when it lands) Dial settings: Emotion 3-5 / Humor 7-10 / Technical 1-4
Read all three before writing:
context/my-voice-dna.md — voice rules.claude/skills/acquisition-repurpose-linkedin-funny/references/funny-posts-swipe-file.md — 10 real examples + 6 patterns + 3 [YOUR_NAME] templates.claude/skills/acquisition-repurpose-linkedin-funny/references/how-to-use-swipe-file.md — the system for applying the swipe fileDo not write without reading the swipe file first. The patterns are the engine.
Mode A — Content Routine (repurposing) The funny angle comes from existing content produced earlier in the /content pipeline (YouTube script, newsletter, article). Look for:
Mode B — Standalone (raw thought or voice note) The user gives a rough idea, a dumb observation, or a pasted voice note in text. The spark is already there — your job is to shape it into a post, not invent new content.
If neither mode is clear, ask:
"Is this based on a piece of content we're repurposing, or is it a standalone thought you want to turn into a post?"
Mode A (routine): Extract from the existing content already in context. Find the irony, the before/after, the thing that went wrong, or the absurd outcome.
Mode B (standalone): If no spark in context, ask:
"What's the observation, moment, or topic? Give it rough — I'll make it land."
One sentence is enough. The spark can come from:
Use the swipe file to choose the right pattern. Here are the 6 that work:
Pattern 1 — Absurd Math Fake budget breakdown where the absurd AI/tech expense dwarfs everything normal. Best for: AI tool spending, time wasted, ridiculous trade-offs. Template:
[Normal expense] = $X
[Normal expense] = $X
[AI/Tech obsession] = $ABSURD
How is anyone supposed to [live/function]?!
Pattern 2 — Self-Deprecating Confession Admit something embarrassing but universally true. Setup → absurd choice → punchline. Best for: AI tool hoarding, late-night rabbit holes, overthinking basic things. Template:
[Responsible choice]? [Another option]? [Third option]?
Nah. I [absurd tech behavior].
Now [consequence that sounds sad but is funny].
[Self-aware punchline with optional emoji]
the user's version: "I have 47 MCP servers installed. I use 3. The other 44 are emotional support repos."
Pattern 3 — Dialogue Format Real (or imagined) conversation where someone calls out your LinkedIn-brained thinking. Best for: roasting hustle culture, making fun of solopreneur self-seriousness. Template:
[Person]: "[Normal question]"
Me: "[LinkedIn-brained answer]"
[Person]: "[Calls out the cringe]"
Me: "..."
Lesson: [Humble punchline]
Pattern 4 — Fake Controversy / LinkedIn Parody One-liner parody of how people talk on LinkedIn. No setup needed — the joke IS the format. Best for: roasting "unpopular opinion" posts, motivational content that says nothing. Example: "Unpopular opinion: I'd rather be happy than sad. Agree or disagree?"
Pattern 5 — Insider Test Creates an in-group feeling. Makes readers who "get it" feel smart. Best for: technical jokes, AI practitioner humor, things only your audience would notice. the user's version: "If your CLAUDE.md file is longer than your actual codebase, you're not engineering context. You're writing fan fiction."
Pattern 6 — Third → First Person Reveal Open with a dramatic third-person setup. Reveal it's you. Vulnerability is the punchline. Best for: genuine fuck-ups, unexpected outcomes, things that sound bad but turned out fine. Template:
[Third-person dramatic setup about "a founder" or "someone I know"]
...
That person was me. [emoji]
[One-sentence lesson — optional, keep it light]
Pick one pattern. Do not mix two patterns in the same post.
Format rules:
the user's humor DNA:
the user's humor triggers:
Non-negotiable:
Gut test: Would [YOUR_NAME] actually laugh at this? If yes, post it. If it feels clever but cold, it's not in voice.
Length check: Under 400 characters is the target. If it needs a second scroll, cut it.
[YOUR_NAME] Test (self-audit — answer before saving):
Run these yourself. If any answer is "no", revise before proceeding.
Save to inbox/outputs/md/YYYY-MM-DD-acquisition-repurpose-linkedin-funny.md
Include at the top:
Post type: Funny / Random Thoughts (Type 6)
Pattern used: [Pattern name from Step 4]
Mode: [Content Routine / Standalone]
Dial: Emotion [X] / Humor [X] / Technical [X]
Push to Notion after saving the file:
mcp__claude_ai_Notion__notion-search with query "LinkedIn Content Dashboard" to find the database ID.mcp__claude_ai_Notion__notion-create-pages to create the record:
context/content-pillars.md — if no clear match, skip this field| Situation | Action |
|---|---|
| Source is too technical to be funny | Find the irony inside the technical topic (the before/after, the unexpected result, the thing that went wrong) |
| Nothing funny emerges | Be honest: "This topic doesn't have a natural funny angle — want a contrarian or story post instead?" Don't force humor. |
| Post ends up too long | Cut everything after the punchline. The joke is in the setup, not the explanation. |
| User gives a one-word topic | Ask: "What happened with [topic]? Give me the actual moment and I'll make it land." |
| User gives a voice note / messy text | Extract the core observation, strip the filler, apply the closest pattern. Don't sanitize the energy — keep your raw voice. |
| User wants emoji heavy post | Gently suggest one emoji max — your style is dry, not bubbly |