Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Write high-performing, persuasive, and authentic LinkedIn posts across any professional niche. Uses research-backed hooks, proven post structures, and Linked...
Write high-performing, persuasive, and authentic LinkedIn posts across any professional niche. Uses research-backed hooks, proven post structures, and Linked...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
READ BEFORE USE
This skill helps you create strong LinkedIn posts that feel human, useful, and credible. It combines: proven hook frameworks, clear narrative structures, proof-first writing, and practical CTA design. Keywords: linkedin, thought leadership, personal brand, founder posts, b2b content, storytelling, case study, hooks, engagement, authority
Before writing, define: Audience — Who is this for? (founders, recruiters, engineers, operators, marketers, sales leaders, etc.) Goal — Reach, authority, leads, hiring, trust, replies, profile visits? Core insight — What is the one thing worth remembering? Proof — What makes this believable (numbers, before/after, constraints, mistakes, outcomes)? If proof is missing, use placeholders like [X%], [Y hours] and request exact values.
Choose a format first, then write: Story Framework Contrarian Case study Teardown Build-in-public Then select 2-3 hooks and finalize one.
Keep paragraphs short (1-2 lines) Front-load specifics Remove generic filler End with one clear CTA Add 3-6 hashtags max
What usually performs best: Strong first two lines (stops the scroll) Specificity (numbers > adjectives) Credible vulnerability (mistakes + lessons) Clear structure (easy to skim on mobile) Conversation CTA (quality comments over empty likes) Avoid: Buzzword soup Generic motivation posts Overlong hashtag blocks Fake certainty without evidence
“Most people do [X]. That’s exactly why they stay stuck.” “Unpopular opinion: [industry belief] is outdated.”
“In [timeframe], we improved [metric] by [number]. Here’s how.” “We cut [cost/time] by [X%]. Not with a new tool—by changing this one workflow.”
“I made this [role]-mistake for months. It cost us [outcome].” “We shipped the wrong thing fast. Here’s what fixed it.”
“The [3-step/4-step] framework I use for [outcome].” “If I had to restart as [role], I’d follow these 5 rules.”
“Would you let your team do [X] without [Y]?” “What’s your biggest bottleneck in [domain] right now?”
Best for real systems, workflows, and automations. Template: bold claim “Not as a demo. As an actual [responsibility/workflow].” “Here’s what it does:” with 4-6 concrete bullets measurable result perspective line + CTA question
Template: starting problem constraints intervention before/after metrics key lesson optional “comment TEMPLATE” CTA
Template: challenge popular view explain why it fails in practice give 3 practical principles ask a polarizing but constructive question
Template: name framework 3-5 steps one mistake to avoid one practical “do this today” action
Template: what shipped this week what worked what broke what changed next ask for informed feedback
Use these to increase clarity and trust: Specificity: “Saved 3.2 hours/week” beats “saved time.” Mechanism: Explain how, not just outcomes. Credibility: Mention tradeoffs, not only wins. Relevance: Tie insight to audience reality. Clarity: One post = one core idea.
Hook in first 1-2 lines 1-2 sentence paragraphs Prefer plain language over hype Use emojis sparingly as section markers Keep claims realistic Never invent outcomes, clients, or credentials Hashtags: 3-6 max niche + function + audience mix avoid spammy broad tags only
By default, provide: 3 hook options 1 full post 1 spicier variant 3 first-comment ideas (to deepen discussion) Optional on request: NL / EN / NL-EN mixed variants X/Twitter adaptation Short + long versions Carousel text outline
When user gives a raw idea, ask/fill: Audience: Goal: Topic: Proof points: Tone: CTA preference: Then generate outputs per contract above.
Generic “AI changed everything” without concrete examples No proof signals Too many ideas in one post CTA mismatch (asking for leads on a pure thought-leadership post) Over-formatting with noisy symbols
Before finalizing: Hook is strong and specific Core claim is clear Includes at least one proof signal Easy to skim on mobile CTA invites real conversation Hashtags are relevant and limited Tone feels authentic to author
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.