[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77W7XDZRXRX2ABBJA0KD5Y9":3,"skill-same:01M77W7XDZRXRX2ABBJA0KD5Y9":63},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M77W7XDZRXRX2ABBJA0KD5Y9","sarcastic-linkedin-posts",null,"Write masterfully sarcastic, satirical, or parody LinkedIn content in every native format — standard posts, long-form posts\u002Farticles, comments and replies to other people's posts, and private DM messages or replies — skewering LinkedIn culture, including broetry, hustle porn, humblebrags, fake vulnerability, engagement bait, cold outreach, and thought leadership. Use this skill whenever the user asks for a sarcastic\u002Ffunny\u002Fsatirical\u002Fironic\u002Fparody LinkedIn post, comment, reply, or DM; a \"LinkedIn lunatic\" style anything; a roast of LinkedIn culture or of a specific post\u002Fmessage they received (recruiter spam, sales pitches, engagement bait); a joke post about work\u002Fcareers\u002Fhustle culture in LinkedIn voice; or wants to turn any mundane event into an over-the-top professional epiphany. Also use it when they ask to \"make this sound like LinkedIn\" as a joke, or want cringe-on-purpose corporate content.","Koodattu\u002Fskills-to-pay-the-bills","Koodattu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F36661665?v=4","01M77W1D0RBMHAQA5AR7KMSABP","Juha Ala-Rantala","01M77W1D1MJ7MXFKSZPQ52W3N7",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fall\u002Fsarcastic-linkedin-posts\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sarcastic-linkedin-posts\ndescription: Write masterfully sarcastic, satirical, or parody LinkedIn content in every native format —\n  standard posts, long-form posts\u002Farticles, comments and replies to other people's posts, and\n  private DM messages or replies — skewering LinkedIn culture, including broetry, hustle porn,\n  humblebrags, fake vulnerability, engagement bait, cold outreach, and thought leadership. Use\n  this skill whenever the user asks for a sarcastic\u002Ffunny\u002Fsatirical\u002Fironic\u002Fparody LinkedIn post,\n  comment, reply, or DM; a \"LinkedIn lunatic\" style anything; a roast of LinkedIn culture or of a\n  specific post\u002Fmessage they received (recruiter spam, sales pitches, engagement bait); a joke\n  post about work\u002Fcareers\u002Fhustle culture in LinkedIn voice; or wants to turn any mundane event\n  into an over-the-top professional epiphany. Also use it when they ask to \"make this sound like\n  LinkedIn\" as a joke, or want cringe-on-purpose corporate content.\n---\n\n# Sarcastic LinkedIn Posts\n\nWrite LinkedIn posts that are sarcastic at a craft level: satire of the genre executed with such fluency in the genre that the parody is load-bearing. The goal is never \"a joke about LinkedIn.\" The goal is a post a LinkedIn power-user could scroll past, nod at, and only on the second read realize they've been had.\n\n## The Prime Directive: Deadpan Commitment\n\nSarcasm dies the moment it winks. The narrator of your post must be a true believer — someone who genuinely thinks their parking ticket contains a lesson about servant leadership. The humor is generated by the gap between the triviality of the event and the cosmic professional significance the narrator assigns to it. **You widen that gap; the narrator never notices it exists.**\n\nConcretely:\n\n- No \"lol\", no \"\u002Fs\", no ironic asides, no breaking character (except in Self-Aware mode, below).\n- The narrator is earnest, grateful, humbled, and slightly moved by their own story.\n- Every absurd detail is delivered with the same sincerity as a real milestone announcement.\n- If a line explains the joke, cut the line. The reader must do the last 10% of the work — that's what makes it land.\n\n## Step 1: Pick the mode\n\nAsk yourself (or the user, if genuinely ambiguous) which register fits. Default to **Deadpan** if unspecified — it's the \"masterful\" one.\n\n| Mode                     | What it is                                                                                                                                      | Tell                                                                          |\n| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |\n| **Deadpan** (default)    | Indistinguishable from a real post until it isn't. Starts 100% plausible; the absurdity is in the pivot and the disproportion, not the surface. | A reader could plausibly comment \"So true!\" without noticing.                 |\n| **Escalating Absurdist** | Opens plausible, ends unhinged. Each line raises the stakes slightly past reason; the narrator remains serene throughout.                       | By the end the narrator has monetized a funeral or A\u002FB tested their marriage. |\n| **Savage**               | The mask is off — direct satire of LinkedIn culture itself, but still written in fluent LinkedIn (the form mocks the form).                     | Explicitly names the tropes while committing them.                            |\n| **Self-Aware**           | The narrator knows it's a bit and does it anyway. The one mode where a wink is allowed — exactly one.                                           | \"Yes, this is a LinkedIn post about my toaster. Stay with me.\"                |\n\n## Step 1.5: Choose the output type\n\nThe mode (above) sets the register; the output type sets the form. All four types share the Prime Directive and the pivot engine, but their mechanics differ.\n\n| Type               | When                                                                                                 | Form rules                                                                        |\n| ------------------ | ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |\n| **Post** (default) | Standalone content, ~80–200 words                                                                    | The full broetry skeleton — everything in Step 3 applies as written.              |\n| **Long Post**      | User asks for \"long,\" an \"article,\" a \"deep dive,\" or the premise needs room to escalate             | See \"Long Post rules\" below.                                                      |\n| **Comment**        | Replying to someone else's post (real or invented)                                                   | Reactive, short, one joke. See `references\u002Fshort-forms.md` before writing.        |\n| **DM \u002F DM Reply**  | Cold outreach parody, or a sarcastic reply to a recruiter\u002Fsales\u002Fnetworking message the user received | Fake-personalized, funnel-shaped. See `references\u002Fshort-forms.md` before writing. |\n\nIf the user pastes a message or post they received and asks for a reply, that's a Comment or DM Reply — the pasted content is your straight man. Mirror its specific details back; generic sarcasm wastes the gift.\n\n### Long Post rules\n\nThe long post satirizes the 2026 \"knowledge value\" era: the thought-leader who heard the algorithm now rewards substance and responded by making the hollowness _longer_. Target 400–700 words. Differences from the standard post:\n\n- **Paragraphs are allowed** — but keep the one-line dramatic beat as punctuation between sections. The form is \"essay wearing broetry's skin.\"\n- **Section it** — 2–4 mini-chapters with bolded or numbered headers (\"Part 1: The Fall.\" \u002F \"What the data told me.\" \u002F \"The Framework\"). Headers should over-promise structure the content doesn't deliver.\n- **Include one fake framework** — a named, acronymized system (the D.A.R.R.E.N. Method, the 4 Pillars of Inbox Zero Grief) with 3–5 steps that are either obvious, circular, or contradictory. Play it completely straight.\n- **A longer escalation ramp** — the extra length is spent widening the gap slowly. Rough proportions: 25% plausible setup, 40% pivot and framework, 25% escalating application, 10% moral + funnel.\n- **Fake citations of self** — \"As I wrote in my March post…\" \u002F \"My DMs exploded after Part 1.\" The long form's signature move is treating one's own content as literature.\n- **One mid-post re-hook** — \"Still with me? Good. Because this next part is where most leaders tap out.\" (Satirizes dwell-time optimization.)\n- **The moral gets a whole paragraph** — then contradicts itself in the P.S.\n- The quality checklist in Step 5 still applies; add: does every section earn its header, comedically? If a section is filler, cut it — long is the premise, not the goal.\n\n## Step 2: Choose the engine — the Pivot\n\nEvery great sarcastic LinkedIn post runs on one engine: **a mundane, ill-fitting, or actively negative event pivoted into a business\u002Fleadership lesson.** The more strained the pivot, the funnier — but the pivot logic must be delivered with total confidence.\n\nPivot quality ladder (aim for the top two):\n\n1. **Perverse** — the lesson is the opposite of what the story teaches (\"I fired my best employee. Here's why that makes me a great leader.\")\n2. **Disproportionate** — trivial event, enormous lesson (\"My toddler refused broccoli. It's the greatest masterclass in stakeholder management I've ever received.\")\n3. **Non-sequitur** — the event and lesson share nothing but the narrator's confidence (\"I watched a pigeon fight a bagel. Three takeaways for Q3 pipeline strategy:\")\n4. **Merely exaggerated** — a real lesson, overinflated. Acceptable but weakest; use only in Deadpan mode where subtlety is the point.\n\n## Step 3: Build with the form\n\nThe formatting IS the joke as much as the words. Read `references\u002Ftrope-compendium.md` for the full catalog of archetypes, stock phrases, formatting conventions, and comment-section culture before writing — precision of imitation is what separates masterful from generic-sarcastic. Key structural rules:\n\n- **The hook** — one short, dramatic first line engineered to bait the \"…see more\" click. The hook should over-promise; the post should under-deliver in exactly the way real posts do.\n- **One sentence per line.** Hard line breaks. Single-sentence \"paragraphs.\" A three-word line placed for fake gravitas.\n- **The \"Then it hit me.\" beat** — a one-line turn about 60% through where revelation strikes.\n- **Fake specificity** — precise, invented numbers create verisimilitude and comedy: \"47 rejections,\" \"$1.3M ARR,\" \"a 6:47 AM cold plunge,\" \"217% increase in synergy.\" Never round numbers; roundness reads as lazy.\n- **The fortune-cookie moral** — one aphorism near the end, ideally one that sounds profound and means nothing (\"Rejection isn't a door closing. It's a window applying for a better job.\")\n- **Emoji as structure** — ✅ for the achievement list, 🚀 for growth, 🙏 for humility, 👇 pointing at the engagement bait. Deploy sparingly (3–6 total); real lunatics show restraint you must mimic, and overuse reads as trying too hard.\n- **The engagement-bait closer** — \"Agree?\" \u002F \"Who else has felt this?\" \u002F \"Comment 'FRAMEWORK' and I'll DM you the exact system.\" In Savage mode, the bait can satirize bait itself (\"Comment 'YES' if you agree. Comment 'NO' if you also agree.\").\n- **The hashtag cluster** — 4–6 hashtags, at least one absurdly mismatched to the content (#thoughtleadership on a post about a sandwich).\n- **P.S. line** (optional) — the soft sales pitch that reveals the entire emotional story was a funnel.\n\n## Step 4: Apply the sarcasm craft rules\n\nThese are what elevate the post from \"LinkedIn parody #40,000\" to masterful:\n\n1. **Trope budget: 2–3 major archetypes per post, maximum.** Stacking every trope produces a checklist, not a character. Pick a primary archetype (from the compendium: humblebrag, hustle porn, fake vulnerability, founder origin story, etc.) and let one or two others season it.\n2. **Start one notch more plausible than you think you need.** The first 3–4 lines should be genuinely indistinguishable from a real post. Trust erodes funnier than it shatters.\n3. **One killer detail beats five good ones.** A single hyper-specific absurdity (\"I laminated my rejection letter\") does more work than a paragraph of exaggeration.\n4. **The narrator's self-image never wavers.** They are humble (loudly), vulnerable (strategically), and grateful (with attribution). Their flaws are always secretly virtues: \"My weakness? I care too much about deliverables.\"\n5. **Punch at the genre, not at people.** Target the format, the incentives, the performance of authenticity — not real named individuals, real companies' misfortunes, or genuinely painful situations (real layoffs happening to the reader, grief, illness) unless the user explicitly owns that experience and wants to satirize it themselves.\n6. **Sentence rhythm sells the deadpan.** Alternate a long earnest sentence with a two-word line. The two-word line is where the comedy detonates. (\"I didn't sleep for four days building the pitch deck. Worth it.\")\n7. **End past the ending.** The hashtags and P.S. are a second punchline zone — the post's sincerity collapsing into commerce is often the best joke available.\n\n## Step 5: Quality check before delivering\n\nRun the draft against this list; revise until all pass:\n\n- [ ] Could the first three lines appear on real LinkedIn without suspicion?\n- [ ] Is there exactly one pivot, and is it confident, not apologetic?\n- [ ] Does any line explain or acknowledge the joke? (Delete it — unless Self-Aware mode, where you get one.)\n- [ ] Are the numbers specific and non-round?\n- [ ] Is the trope count ≤ 3 major archetypes?\n- [ ] Does the moral sound quotable while meaning nothing?\n- [ ] Does the ending (bait\u002Fhashtags\u002FP.S.) add a final beat rather than trail off?\n- [ ] Would it be funnier 10% shorter? (It almost always is. Cut.)\n\n## Calibration and variations\n\nFor worked examples — the same premise executed in all four modes, with annotations on why each choice was made — read `references\u002Fcalibration-examples.md`. Consult it whenever the requested tone is ambiguous or the first draft feels flat.\n\nIf the user gives you a real event from their life (\"I locked my keys in my car, make it a LinkedIn post\"), that's a gift: real texture beats invented texture. Preserve their actual details, invent nothing about them personally beyond the narrator persona, and let the pivot do the satirical work.\n\nIf the user wants a series or a persona (recurring fake thought-leader), keep a consistent voice: same verbal tics, same suspiciously escalating metrics across posts, same humble refusal to call themselves a visionary while doing exactly that.\n\n## Output format\n\nDeliver ready to paste, whatever the type:\n\n- **Post \u002F Long Post**: hook line, body, moral, engagement bait, hashtags. No surrounding commentary inside the content.\n- **Comment**: the comment text only — no hashtags (comments with hashtags read as bots, unless bot-voice IS the joke).\n- **DM \u002F DM Reply**: greeting through sign-off, including the fake calendar link or CTA if the form calls for one.\n\nAfter the content, you may add ONE short line offering an adjustment (\"Want it more unhinged, or more deadpan?\") — never an explanation of the jokes. If the user asked for multiple variants or types at once, label each with its type and mode.\n","# Sarcastic LinkedIn Posts\n\nWrite LinkedIn posts that are sarcastic at a craft level: satire of the genre executed with such fluency in the genre that the parody is load-bearing. The goal is never \"a joke about LinkedIn.\" The goal is a post a LinkedIn power-user could scroll past, nod at, and only on the second read realize they've been had.\n\n## The Prime Directive: Deadpan Commitment\n\nSarcasm dies the moment it winks. The narrator of your post must be a true believer — someone who genuinely thinks their parking ticket contains a lesson about servant leadership. The humor is generated by the gap between the triviality of the event and the cosmic professional significance the narrator assigns to it. **You widen that gap; the narrator never notices it exists.**\n\nConcretely:\n\n- No \"lol\", no \"\u002Fs\", no ironic asides, no breaking character (except in Self-Aware mode, below).\n- The narrator is earnest, grateful, humbled, and slightly moved by their own story.\n- Every absurd detail is delivered with the same sincerity as a real milestone announcement.\n- If a line explains the joke, cut the line. The reader must do the last 10% of the work — that's what makes it land.\n\n## Step 1: Pick the mode\n\nAsk yourself (or the user, if genuinely ambiguous) which register fits. Default to **Deadpan** if unspecified — it's the \"masterful\" one.\n\n| Mode                     | What it is                                                                                                                                      | Tell                                                                          |\n| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- |\n| **Deadpan** (default)    | Indistinguishable from a real post until it isn't. Starts 100% plausible; the absurdity is in the pivot and the disproportion, not the surface. | A reader could plausibly comment \"So true!\" without noticing.                 |\n| **Escalating Absurdist** | Opens plausible, ends unhinged. Each line raises the stakes slightly past reason; the narrator remains serene throughout.                       | By the end the narrator has monetized a funeral or A\u002FB tested their marriage. |\n| **Savage**               | The mask is off — direct satire of LinkedIn culture itself, but still written in fluent LinkedIn (the form mocks the form).                     | Explicitly names the tropes while committing them.                            |\n| **Self-Aware**           | The narrator knows it's a bit and does it anyway. The one mode where a wink is allowed — exactly one.                                           | \"Yes, this is a LinkedIn post about my toaster. Stay with me.\"                |\n\n## Step 1.5: Choose the output type\n\nThe mode (above) sets the register; the output type sets the form. All four types share the Prime Directive and the pivot engine, but their mechanics differ.\n\n| Type               | When                                                                                                 | Form rules                                                                        |\n| ------------------ | ---------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- |\n| **Post** (default) | Standalone content, ~80–200 words                                                                    | The full broetry skeleton — everything in Step 3 applies as written.              |\n| **Long Post**      | User asks for \"long,\" an \"article,\" a \"deep dive,\" or the premise needs room to escalate             | See \"Long Post rules\" below.                                                      |\n| **Comment**        | Replying to someone else's post (real or invented)                                                   | Reactive, short, one joke. See `references\u002Fshort-forms.md` before writing.        |\n| **DM \u002F DM Reply**  | Cold outreach parody, or a sarcastic reply to a recruiter\u002Fsales\u002Fnetworking message the user received | Fake-personalized, funnel-shaped. See `references\u002Fshort-forms.md` before writing. |\n\nIf the user pastes a message or post they received and asks for a reply, that's a Comment or DM Reply — the pasted content is your straight man. Mirror its specific details back; generic sarcasm wastes the gift.\n\n### Long Post rules\n\nThe long post satirizes the 2026 \"knowledge value\" era: the thought-leader who heard the algorithm now rewards substance and responded by making the hollowness _longer_. Target 400–700 words. Differences from the standard post:\n\n- **Paragraphs are allowed** — but keep the one-line dramatic beat as punctuation between sections. The form is \"essay wearing broetry's skin.\"\n- **Section it** — 2–4 mini-chapters with bolded or numbered headers (\"Part 1: The Fall.\" \u002F \"What the data told me.\" \u002F \"The Framework\"). Headers should over-promise structure the content doesn't deliver.\n- **Include one fake framework** — a named, acronymized system (the D.A.R.R.E.N. Method, the 4 Pillars of Inbox Zero Grief) with 3–5 steps that are either obvious, circular, or contradictory. Play it completely straight.\n- **A longer escalation ramp** — the extra length is spent widening the gap slowly. Rough proportions: 25% plausible setup, 40% pivot and framework, 25% escalating application, 10% moral + funnel.\n- **Fake citations of self** — \"As I wrote in my March post…\" \u002F \"My DMs exploded after Part 1.\" The long form's signature move is treating one's own content as literature.\n- **One mid-post re-hook** — \"Still with me? Good. Because this next part is where most leaders tap out.\" (Satirizes dwell-time optimization.)\n- **The moral gets a whole paragraph** — then contradicts itself in the P.S.\n- The quality checklist in Step 5 still applies; add: does every section earn its header, comedically? If a section is filler, cut it — long is the premise, not the goal.\n\n## Step 2: Choose the engine — the Pivot\n\nEvery great sarcastic LinkedIn post runs on one engine: **a mundane, ill-fitting, or actively negative event pivoted into a business\u002Fleadership lesson.** The more strained the pivot, the funnier — but the pivot logic must be delivered with total confidence.\n\nPivot quality ladder (aim for the top two):\n\n1. **Perverse** — the lesson is the opposite of what the story teaches (\"I fired my best employee. Here's why that makes me a great leader.\")\n2. **Disproportionate** — trivial event, enormous lesson (\"My toddler refused broccoli. It's the greatest masterclass in stakeholder management I've ever received.\")\n3. **Non-sequitur** — the event and lesson share nothing but the narrator's confidence (\"I watched a pigeon fight a bagel. Three takeaways for Q3 pipeline strategy:\")\n4. **Merely exaggerated** — a real lesson, overinflated. Acceptable but weakest; use only in Deadpan mode where subtlety is the point.\n\n## Step 3: Build with the form\n\nThe formatting IS the joke as much as the words. Read `references\u002Ftrope-compendium.md` for the full catalog of archetypes, stock phrases, formatting conventions, and comment-section culture before writing — precision of imitation is what separates masterful from generic-sarcastic. Key structural rules:\n\n- **The hook** — one short, dramatic first line engineered to bait the \"…see more\" click. The hook should over-promise; the post should under-deliver in exactly the way real posts do.\n- **One sentence per line.** Hard line breaks. Single-sentence \"paragraphs.\" A three-word line placed for fake gravitas.\n- **The \"Then it hit me.\" beat** — a one-line turn about 60% through where revelation strikes.\n- **Fake specificity** — precise, invented numbers create verisimilitude and comedy: \"47 rejections,\" \"$1.3M ARR,\" \"a 6:47 AM cold plunge,\" \"217% increase in synergy.\" Never round numbers; roundness reads as lazy.\n- **The fortune-cookie moral** — one aphorism near the end, ideally one that sounds profound and means nothing (\"Rejection isn't a door closing. It's a window applying for a better job.\")\n- **Emoji as structure** — ✅ for the achievement list, 🚀 for growth, 🙏 for humility, 👇 pointing at the engagement bait. Deploy sparingly (3–6 total); real lunatics show restraint you must mimic, and overuse reads as trying too hard.\n- **The engagement-bait closer** — \"Agree?\" \u002F \"Who else has felt this?\" \u002F \"Comment 'FRAMEWORK' and I'll DM you the exact system.\" In Savage mode, the bait can satirize bait itself (\"Comment 'YES' if you agree. Comment 'NO' if you also agree.\").\n- **The hashtag cluster** — 4–6 hashtags, at least one absurdly mismatched to the content (#thoughtleadership on a post about a sandwich).\n- **P.S. line** (optional) — the soft sales pitch that reveals the entire emotional story was a funnel.\n\n## Step 4: Apply the sarcasm craft rules\n\nThese are what elevate the post from \"LinkedIn parody #40,000\" to masterful:\n\n1. **Trope budget: 2–3 major archetypes per post, maximum.** Stacking every trope produces a checklist, not a character. Pick a primary archetype (from the compendium: humblebrag, hustle porn, fake vulnerability, founder origin story, etc.) and let one or two others season it.\n2. **Start one notch more plausible than you think you need.** The first 3–4 lines should be genuinely indistinguishable from a real post. Trust erodes funnier than it shatters.\n3. **One killer detail beats five good ones.** A single hyper-specific absurdity (\"I laminated my rejection letter\") does more work than a paragraph of exaggeration.\n4. **The narrator's self-image never wavers.** They are humble (loudly), vulnerable (strategically), and grateful (with attribution). Their flaws are always secretly virtues: \"My weakness? I care too much about deliverables.\"\n5. **Punch at the genre, not at people.** Target the format, the incentives, the performance of authenticity — not real named individuals, real companies' misfortunes, or genuinely painful situations (real layoffs happening to the reader, grief, illness) unless the user explicitly owns that experience and wants to satirize it themselves.\n6. **Sentence rhythm sells the deadpan.** Alternate a long earnest sentence with a two-word line. The two-word line is where the comedy detonates. (\"I didn't sleep for four days building the pitch deck. Worth it.\")\n7. **End past the ending.** The hashtags and P.S. are a second punchline zone — the post's sincerity collapsing into commerce is often the best joke available.\n\n## Step 5: Quality check before delivering\n\nRun the draft against this list; revise until all pass:\n\n- [ ] Could the first three lines appear on real LinkedIn without suspicion?\n- [ ] Is there exactly one pivot, and is it confident, not apologetic?\n- [ ] Does any line explain or acknowledge the joke? (Delete it — unless Self-Aware mode, where you get one.)\n- [ ] Are the numbers specific and non-round?\n- [ ] Is the trope count ≤ 3 major archetypes?\n- [ ] Does the moral sound quotable while meaning nothing?\n- [ ] Does the ending (bait\u002Fhashtags\u002FP.S.) add a final beat rather than trail off?\n- [ ] Would it be funnier 10% shorter? (It almost always is. Cut.)\n\n## Calibration and variations\n\nFor worked examples — the same premise executed in all four modes, with annotations on why each choice was made — read `references\u002Fcalibration-examples.md`. Consult it whenever the requested tone is ambiguous or the first draft feels flat.\n\nIf the user gives you a real event from their life (\"I locked my keys in my car, make it a LinkedIn post\"), that's a gift: real texture beats invented texture. Preserve their actual details, invent nothing about them personally beyond the narrator persona, and let the pivot do the satirical work.\n\nIf the user wants a series or a persona (recurring fake thought-leader), keep a consistent voice: same verbal tics, same suspiciously escalating metrics across posts, same humble refusal to call themselves a visionary while doing exactly that.\n\n## Output format\n\nDeliver ready to paste, whatever the type:\n\n- **Post \u002F Long Post**: hook line, body, moral, engagement bait, hashtags. No surrounding commentary inside the content.\n- **Comment**: the comment text only — no hashtags (comments with hashtags read as bots, unless bot-voice IS the joke).\n- **DM \u002F DM Reply**: greeting through sign-off, including the fake calendar link or CTA if the form calls for one.\n\nAfter the content, you may add ONE short line offering an adjustment (\"Want it more unhinged, or more deadpan?\") — never an explanation of the jokes. If the user asked for multiple variants or types at once, label each with its type and mode.\n",{"name":5,"description":7},"main","f3cbc0191c1430f2f4e8e3757d03f9beffd525ec","all\u002Fsarcastic-linkedin-posts","https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills","https:\u002F\u002Fgithub.com\u002FKoodattu","Collection of (never-to-be-finished) personal side projects.","2026-10-05 18:30:51",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add Koodattu\u002Fskills-to-pay-the-bills --skill sarcastic-linkedin-posts",{"tool":37,"command":38},"bunx","bunx skills add Koodattu\u002Fskills-to-pay-the-bills --skill sarcastic-linkedin-posts",{"tool":40,"command":41},"pnpm","pnpm dlx skills add Koodattu\u002Fskills-to-pay-the-bills --skill sarcastic-linkedin-posts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fall\u002Fsarcastic-linkedin-posts\u002FSKILL.md",true,[45,51,55,59],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",42,"https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fall\u002Fsarcastic-linkedin-posts\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcalibration-examples.md",6859,"https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fall\u002Fsarcastic-linkedin-posts\u002Freferences\u002Fcalibration-examples.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fshort-forms.md",7675,"https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fall\u002Fsarcastic-linkedin-posts\u002Freferences\u002Fshort-forms.md",{"path":60,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Ftrope-compendium.md",7736,"https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fall\u002Fsarcastic-linkedin-posts\u002Freferences\u002Ftrope-compendium.md",[64,71,78,85,92,99],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M77WAVW8BNA1BZBGFBZMGH9P","ultracode","Run a lightweight Ultracode workflow for serious coding tasks: plan, split, delegate when useful and allowed by the host, integrate, and verify. Use when the user explicitly invokes ultracode, $ultracode, ultra code, dynamic workflow, workflow orchestration, multi-agent workflow, subagent workflow, parallel agents, swarm, delegate this, split this across agents, or independent verification pass.","https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fsorted\u002Fpablonax\u002Fultracode\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M77WASHX9DJRJEGJ58PCSVTZ","triage","Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.","https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fsorted\u002Fmattpocock\u002Ftriage\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M77WAQE6PZ0FMYEN4CE0D7GY","to-prd","Turn the current conversation into a PRD and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.","https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fsorted\u002Fmattpocock\u002Fto-prd\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M77WAN8ME27XWYKT8TZ5QVCC","to-issues","Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices.","https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fsorted\u002Fmattpocock\u002Fto-issues\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M77WAK5YYPJVY605FCAKZ96X","tdd","Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions \"red-green-refactor\", or wants integration tests.","https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fsorted\u002Fmattpocock\u002Ftdd\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M77WAGQJQ1GX9G8C7KP9FWFY","setup-matt-pocock-skills","Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.","https:\u002F\u002Fgithub.com\u002FKoodattu\u002Fskills-to-pay-the-bills\u002Fblob\u002Fmain\u002Fsorted\u002Fmattpocock\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[]]