agentsclimarketplace

Writing linkedin posts

Skill Ai11-Consulting-GmbH/marketing-skills/writing-linkedin-posts

Create engaging, authentic LinkedIn posts (English or German / auf Englisch oder Deutsch) like a Top Voice. Use this skill for LinkedIn posts, LinkedIn-Beiträge, LinkedIn-Posts schreiben, social media posts for LinkedIn, professional thought leadership content, viral/engaging LinkedIn content, or any LinkedIn engagement strategy work. Triggers: "LinkedIn post", "LinkedIn-Post", "LinkedIn-Beitrag", "schreib mir einen LinkedIn", "professional social content", "thought leadership", "Top Voice".From its SKILL.md

Install
npx -y skills add Ai11-Consulting-GmbH/marketing-skills --skill writing-linkedin-posts

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

21.2 KB, ~4.9k tokens by cl100k_base, as published. Nobody here has run it

LinkedIn Post Writer

Create engaging, authentic LinkedIn posts that drive meaningful engagement and establish thought leadership. This skill is bilingual: posts can be produced in English or German (Deutsch) — locked at Step 0 and binding for the entire session.


How To Use This Skill

This skill is a procedure, not a reference manual. Follow Steps 0 → 5 in order. The sections below the steps (Core Principles, Post Anatomy, Post Formats, etc.) are reference material the steps point into — read them when a step tells you to, not as a linear document.

Step 0  Language Gate           (MANDATORY first action)
Step 1  Topic & Context         (interview the user)
Step 2  Format Selection        (pick one of four templates)
Step 3  Draft                   (apply principles + template)
Step 4  Self-Critique Gate      (run checklist; revise if any item fails)
Step 5  Present & Iterate       (show user, offer revisions)

Step 0 — Language Gate (MANDATORY FIRST STEP)

Before doing anything else — before asking about topic, format, hook, audience, or anything in the rest of this skill — you MUST ask the user exactly one question:

"Do you want this LinkedIn post in English or German?"

Use the AskUserQuestion tool with exactly two options: English and German (Deutsch). Do not offer a third option, do not combine this with any other prompt, question, statement, or option, do not skip it even if the user's request is already written in English or German.

Fallback: If AskUserQuestion is unavailable in the current runtime, ask the question in plain text and wait for the user's reply before proceeding.

Then bind the rest of the workflow to that choice:

  • English → the final post MUST be written in English. All hook patterns, body, and close are in English. Internal reasoning and any clarifying questions you ask afterward may still be in English regardless of the choice.
  • German → the final post MUST be written in German (Deutsch). Apply the same principles, but adapt idiom, register, and phrasing natively for a German-speaking LinkedIn audience — do not literal-translate English clichés. See ### German-Specific Guidance below for register, anti-patterns, and hashtag conventions.

Treat the locked language as a hard constraint — do not switch mid-draft, do not produce a bilingual version unless the user explicitly asks for one after the gate.

Cross-skill instruction: When German is selected, treat all English examples in this skill and its references (references/hooks.md, references/examples.md) as structural templates only — the body, hook, and tone must be authentically German, not translated.


Step 1 — Topic & Context Interview

Once the language is locked, gather what you need to write something specific rather than generic. Ask the user for:

  1. Topic / angle — what is this post actually about? A specific experience, observation, contrarian belief, or framework?
  2. The concrete seed — a moment, number, conversation, decision, or data point you can anchor the post on. If the user offers nothing concrete, ask for one specific example before drafting.
  3. Audience — who's the intended reader? (founders, engineers, hiring managers, peers in a specific industry, etc.)
  4. Goal of the post — establish credibility on a topic, spark discussion, share a lesson, attract a specific kind of reader?
  5. Anything to avoid — names to anonymize, employer details to protect, topics off-limits.

If the user has already supplied some of this in their initial message, do not re-ask — confirm and proceed. Bundle remaining questions into a single AskUserQuestion call when possible (3–4 questions max). Do NOT proceed to Step 2 with "generic professional content" as the topic — push back and request a specific seed.

Voice calibration (optional): If the user has past posts or a known POV, ask whether they want you to match a specific tone, a recurring theme, or a signature phrase/framework they're known for. See ## Voice Calibration Reference below.


Step 2 — Format Selection

Choose ONE format from the four templates in ## Post Formats below. The mapping:

User intentFormat
Tell what happened to me and what I learnedStory Post
Give readers a process / framework / listList Post
Push back on conventional wisdomContrarian Post
Name a pattern I've noticedObservation Post

If the post would naturally need a carousel, image, poll, or video, note that to the user but still produce the text-only version first — the media is supplementary, not the post.

State your chosen format to the user before drafting so they can redirect if needed.


Step 3 — Draft

Write the post using:

  • The locked language (Step 0)
  • The gathered context (Step 1)
  • The chosen format template (Step 2)
  • The principles in ## Core Principles, ## Post Anatomy, and ## Writing Guidelines below
  • Hook patterns from references/hooks.md (German section if German is locked)
  • Anti-patterns from ## What to Avoid — do not produce any of them

Target length: 150–300 words (English) / 130–260 words (German). Use whitespace generously — short paragraphs (1–3 sentences), line breaks between thoughts. Hashtags: 0–3 at the very end, after a blank line — fewer is better; many top creators now use zero.

Do not present the draft yet. Proceed to Step 4.


Step 4 — Self-Critique Gate

Run the draft through the checklist below. If ANY item fails, revise before presenting to the user. Do not present a draft that fails any item.

[ ] 0. Language: Post is entirely in the language locked at Step 0 — no mixed-language slips.
[ ] 1. Hook: Would the first 2 lines stop MY scroll? Specific, honest, not formulaic.
[ ] 2. Focus: Exactly ONE clear idea? (If two ideas, split into two posts.)
[ ] 3. Specificity: At least one concrete detail (number, name, moment, quote) — no pure abstraction.
[ ] 4. Authenticity: Sounds like the user, not "LinkedIn me". No performed vulnerability.
[ ] 5. Format: Scannable — short paragraphs, whitespace, no wall of text.
[ ] 6. Close: Invites genuine engagement; no "Agree?", "Comment YES if…", "Follow me for more".
[ ] 7. Vulnerability check: If personal, sharing to HELP the reader, not to process feelings.
[ ] 8. Anti-pattern scan: None of the patterns in `## What to Avoid` (especially the AI-tell list).
[ ] 9. Cringe test: Would the user be proud of this post in a year?

If a German post: also verify no English buzzwords snuck in where a natural German word exists, register is consistent (Du or Sie, not both), and hashtags are appropriate to German LinkedIn norms.


Step 5 — Present & Iterate

Show the user the final draft. After the draft, offer (in this order):

  1. Alternative hooks — 2–3 different opening lines they can swap in.
  2. Length variant — a shorter or longer version on request.
  3. Tone shift — more analytical / more personal / more direct.

Do not include unsolicited self-praise about why the post works. Let the post stand.


German-Specific Guidance

This section is binding when German is locked at Step 0.

Register: Du vs. Sie

  • Default to "du" for personal posts on LinkedIn — DACH norm since roughly 2023 for individual creators.
  • Use "Sie" only for explicitly formal/institutional contexts (B2B, public sector, traditional industries, or if the user requests it).
  • Pick one and stay consistent. Mixing Du and Sie in the same post reads as careless.

Gendergerechte Sprache

Use gender-neutral / inclusive German where natural: Mitarbeitende, Kolleg:innen, Führungskräfte. Avoid awkward forms that hurt readability. The user's preference overrides — ask in Step 1 if unclear.

German-Specific Anti-Patterns (additional)

Avoid these German LinkedIn clichés on top of the global anti-patterns below:

  • Gratitude/humility theater openers: "Ich bin so dankbar/stolz/demütig…", "Ich darf / Ich durfte…" (false modesty).
  • Englisch-Buzzword-Salat: "Quick Learnings aus meiner Journey im Mindset-Reframing." Use German where German works; keep English terms only when they're genuinely the term of art (e.g. "Sprint", "Pull Request", "OKR").
  • Über-formal corporate-speak: "Hiermit darf ich Ihnen mitteilen…". This is a LinkedIn post, not a Geschäftsbrief.
  • "Spoiler:"-Eröffner as fake suspense.
  • Direct calques of English clichés: "Lass mich ehrlich sein…" (literal of "Let me be honest") feels translated rather than written.

Hashtags (German)

Use the German tag when one has real traction (#Führung, #Karriere, #NewWork, #Personalentwicklung). Keep the English tag when the German equivalent has little use (#leadership often outperforms #Führungskraft). Mixed-language hashtag sets are acceptable on German LinkedIn. Still cap at 0–3.

Length (German)

German runs ~10–15% fewer words for equivalent content because compounds replace multi-word English phrases. Target 130–260 Wörter; LinkedIn truncates around 3,000 characters but if you're near that limit, the post is too long.


Core Principles

Authenticity Over Performance

LinkedIn has matured. Readers can spot manufactured vulnerability and engagement bait instantly. The posts that resonate are genuinely useful or genuinely human — not optimized for virality.

What works:

  • Real experiences with honest reflection
  • Specific insights from your actual work
  • Admitting what you don't know
  • Sharing without needing validation

What doesn't:

  • Performed vulnerability for engagement
  • Stories that feel too perfectly structured
  • Lessons that sound like motivational posters

One Idea Per Post

The biggest mistake is cramming multiple tips, stories, or angles into one post. Focus on:

  • One core idea
  • One story
  • One insight
  • One lesson

If you have five points, that's five posts.

Value Without Strings

Every post must educate, inspire, or entertain. Ask: "Would I find this valuable if a stranger posted it?" Not "Will this get engagement?"


Voice Calibration Reference

Use this when the user wants help defining their voice (typically during Step 1).

Find their POV:

  • What topic do they have genuine expertise in?
  • What's their contrarian belief in their industry?
  • What perspective do they bring that others don't?
  • What would they want to be known for saying?

Consistency markers — develop 2–3 recognizable elements:

  • A recurring theme or topic area
  • A consistent tone (analytical, warm, direct, witty)
  • A signature format
  • Phrases or frameworks they've coined

Voice calibration target:

  • More polished than a text to a friend
  • Less formal than a company memo
  • As smart as their best work conversations
  • As human as their real personality

Post Anatomy

The Hook (Lines 1–2)

The first 2–3 lines appear before "See more" and determine everything.

Modern hooks that work (English examples — German equivalents in references/hooks.md):

TypeExampleWhy It Works
Honest admission"I've been wrong about remote work."Genuine, not performed
Specific observation"I've noticed something in every founder who scaled past $10M."Credibility + curiosity
Direct challenge"Most career advice optimizes for the wrong thing."Provokes thought
Unexpected angle"The best hire I made had the worst resume."Subverts expectations
Simple truth"Nobody talks about how lonely leadership is."Resonates emotionally

Hooks to retire (do not generate these):

  • "This one thing made me $X" — scam-ad energy
  • "The CEO pulled me aside and said..." — manufactured suspense
  • "I'm excited to announce..." — corporate and skippable
  • "[Number] words that changed my life" — too formulaic
  • "A stranger approached me at [airport / coffee shop / Uber]…" — overused trope
  • "My [7-year-old / dad / Uber driver] asked me why I…" — staged-conversation hook
  • "I studied 100 [CEOs / founders]. Here's what they do differently:" — thread-bait
  • "Most people won't read past line 3. But if you do…" — engagement-bait pivot
  • "Three years ago I was sleeping on a friend's couch. Today…" — gratitude-bait reversal
  • "Spoiler:" / "Plot twist:" / "Here's the kicker:" / "Let me explain:" / "Quick story:" — AI-tell cadences
  • Em-dash–heavy parallel constructions like "I didn't just get a promotion — I got a life lesson" — AI cadence

See references/hooks.md for the full pattern catalogue, including the German hook section.

The Body

Structure for scannability:

  • Short paragraphs (1–3 sentences max)
  • Line breaks between thoughts
  • Bullet points for lists (but don't overuse)
  • Bold for emphasis sparingly

Storytelling framework:

  1. Set the scene (briefly — one sentence)
  2. Introduce tension or conflict
  3. Show the turning point
  4. Deliver the insight
  5. Make it applicable to the reader

The Close

End with purpose, not desperation.

Good closes:

  • Genuine question that invites perspective
  • Specific call to action ("Bookmark this for your next negotiation")
  • Reflection that lingers ("Something to sit with this week")

Avoid:

  • "Agree?" (lazy)
  • "Comment YES if..." (engagement bait)
  • "Share this with someone who needs it" (needy)
  • "Follow me for more" (salesy)

Vulnerability Done Right

Authentic sharing builds connection. Performed vulnerability destroys trust.

Strategic Vulnerability vs. Exploitation

Share when:

  • The experience taught you something others can learn
  • You've processed it enough to offer perspective
  • It serves the reader, not your need for validation
  • Time has passed and you have hindsight

Don't share when:

  • The wound is still fresh
  • You're seeking sympathy, not providing value
  • It could harm others involved
  • It feels performative even to you

The Vulnerability Test

Before posting something personal, ask:

  1. Am I sharing this to help others or to process my own feelings?
  2. Would I be comfortable if this went viral?
  3. Does this include genuine insight or just pain?
  4. Have I protected others who were involved?

Post Formats

Step 2 selects one of these templates. Use it as a skeleton, then draft to it in Step 3.

Story Post

Best for: Personal experiences, lessons learned, career moments

[Hook — honest admission or surprising outcome]

[One sentence of context]

[What happened — the tension or challenge]

[The turning point]

[What you learned]

[Question or reflection for reader]

List Post

Best for: Frameworks, actionable advice, curated insights

[Hook — clear value promise]

[Why this matters — one sentence]

1. [Point with brief context]
2. [Point with brief context]
3. [Point with brief context]
(3–7 items max)

[Closing insight or question]

Contrarian Post

Best for: Challenging conventional wisdom (with substance)

[Your contrarian position, stated directly]

[The common belief you're challenging]

[Your reasoning — why you see it differently]

[Evidence or experience]

[Nuanced conclusion — acknowledge complexity]

[Invite discussion]

Contrarian guardrails:

  • Have genuine expertise on the topic
  • Argue against ideas, not people
  • Offer an alternative, not just criticism
  • Acknowledge what the other side gets right
  • Be open to being wrong

Observation Post

Best for: Industry insights, trends, patterns you've noticed

[What you've observed]

[Specific evidence or examples]

[Why it matters]

[Your interpretation]

[Question to test if others see it too]

Media Formats

Text-only posts are the default. Consider media only when it adds genuine value:

  • Document/Carousel: 5–10 slides for step-by-step guides or frameworks. Each slide stands alone. Strong save rates.
  • Image: Use for genuine value (charts, diagrams, event photos). Avoid stock photos and generic graphics. Native uploads historically outperform external links, though the gap has narrowed.
  • Polls: For genuine discussion or research questions. Always share your own take on the result afterward.
  • Video: Short-form (under 90 seconds) works for tips and insights. Longer video (3–8 minutes) is increasingly surfaced in LinkedIn's dedicated video tab. Captions are essential — most viewers watch muted.

Writing Guidelines

Tone Spectrum

Find the right spot on each scale for the user's POV:

Corporate    ←————————→ Casual
Reserved     ←————————→ Vulnerable
Analytical   ←————————→ Emotional
Serious      ←————————→ Playful

Most Top Voices sit slightly right of center on each.

Length

  • Optimal: 150–300 words (English) / 130–260 words (German). Enough for depth, short enough to finish.
  • LinkedIn truncates posts around 3,000 characters. If you're near that limit, the post is too long — split it.
  • Use whitespace generously. Dense text kills engagement.

Formatting Rules

  • Never use hashtags inline with text.
  • Place 0–3 hashtags at the very end after a blank line. Fewer is better; many top creators now use zero. LinkedIn has progressively devalued hashtags since 2024 — the feed relies on topic classification, not tag matching.
  • One or two emoji at most — emoji-heavy posts signal low effort. Many strong posts use zero.
  • Use first-person singular (English: "I"; German: "ich") not first-person plural for personal posts.

What to Avoid

Content anti-patterns

  • "I'm excited to announce…" (corporate speak — just announce the thing)
  • Humblebrags disguised as lessons
  • Recycled viral post formats: airport conversations, Uber-driver wisdom, the wise stranger
  • The fake-child-quote setup: "My 7-year-old asked me why I work so much…"
  • The founder humble-flex: "We just crossed $1M ARR. But honestly I almost quit last month."
  • The gratitude-reversal: "Three years ago I was sleeping on a couch. Today…"
  • Posting others' frameworks without credit
  • Tragedy exploitation (using global events for engagement)

AI-tell anti-patterns (2025–2026)

LinkedIn audiences have become highly attuned to AI-written cadences. Avoid:

  • Em-dash–heavy parallel constructions: "I didn't just lose the deal — I lost a belief about how deals work."
  • Cadence tells: "Here's the kicker:", "Let me explain:", "Quick story:", "Let me be clear:", "Spoiler:", "Plot twist:"
  • Tricolons of escalation: "Not just X. Not just Y. But Z." in every paragraph.
  • "It wasn't just A. It was B." as a reflex closing.
  • Symmetric short-sentence stacks that read like a TED transcript run through a beautifier.
  • Generic founder-philosophy abstractions ("clarity creates momentum") with no specific story underneath.

If you find yourself reaching for any of these in Step 3, revise — they signal AI authorship to a sophisticated reader and undermine the user's credibility.

Engagement anti-patterns

  • "Comment YES if you agree"
  • "Share this with 3 people"
  • Tagging people who didn't ask to be tagged
  • Posting controversial takes you don't actually believe
  • Fake questions where you just want to share your answer

Format anti-patterns

  • Every. Sentence. As. Its. Own. Line.
  • Excessive emoji strings
  • ALL CAPS FOR EMPHASIS
  • Hashtag stuffing
  • Walls of text without whitespace

AI-disclosure note

LinkedIn audiences in 2025–2026 are increasingly able to detect AI-written content. If the user is using this skill to draft posts they'll publish as their own, the strongest outputs will sound like the user, with their specific stories and quirks — not a generic LLM cadence. When the post relies heavily on a user-supplied seed (a real moment, number, or story), AI-tell risk drops dramatically. When the user supplies only an abstract topic, push back in Step 1 for a concrete seed — it's the single biggest defense against AI-tell slop.


Content Categories That Perform

  1. Career lessons — Failures, pivots, decisions made
  2. Behind-the-scenes — Real work experiences, how things actually work
  3. Industry insights — Patterns you've noticed, trends you're seeing
  4. How-to frameworks — Actionable processes readers can apply
  5. Contrarian takes — Challenge assumptions (with substance)
  6. Personal milestones — Only when tied to broader insights

References

  • references/hooks.md — Complete hook catalogue, English and German sections, with the full Hooks-to-Retire table.
  • references/examples.md — Annotated full-post examples in English and German.
  • references/engagement-strategy.md — Post-publication strategy (first-comment timing, comment quality, what not to do). Surface this only when the user asks about engagement, growth, or what to do after posting — it is not part of the Steps 0–5 drafting flow.

What ships with it: 3 files

29.1 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 326,499. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.