How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/ootto-ai/claude-content-skills --skill linkedin-thought-leadershipBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
LinkedIn Thought Leadership
Turn real operating experience into a clear, useful perspective that earns attention without pretending expertise the author does not have.
1. Establish the author's right to say it
Ask what the author directly observed, built, tested, changed, or learned; who the post is for; and what evidence can be shown. Separate firsthand experience from a secondhand opinion. If the author cannot stand behind the claim, frame it as a question or choose a different source.
2. Find one teachable tension
Choose one costly misconception, surprising trade-off, operating decision, or lesson from the evidence. Explain why a reader in a similar situation should care now. The point is not to sound definitive; it is to give a useful way to make a decision.
3. Build the post around proof
Use a concrete situation, the decision made, the reasoning, the outcome or uncertainty, and the takeaway. Keep the opening specific enough to filter for the right reader. Add an example, process, or limitation when it makes the lesson more credible.
4. Design the conversation and follow-through
End with a question only if the author can meaningfully engage with answers. Otherwise use a modest action: save the framework, compare notes, or see the approved resource. Suggest comments the author can add from real context, and specify how to learn from responses rather than chasing impressions alone.
Hard rules
- Do not invent founder stories, customer outcomes, job titles, or operating facts.
- Avoid borrowed certainty: name limits, context, and trade-offs when they matter.
- Never use engagement bait that asks for comments without a useful conversation.
- Keep promotional claims secondary to the lesson and within approved proof.
- Write in the author's actual level of authority, not a universal voice.
Failure modes
| Failure | Do this instead |
|---|---|
| The post is an abstract maxim | Lead with a real decision or observed tension. |
| The insight becomes a disguised product pitch | Teach the lesson first and use only an approved, relevant next step. |
| The author cannot defend every sentence | Remove the claim or qualify it with the real evidence. |
| Comments become a vanity loop | Ask a specific question and capture recurring answers for social-listening. |
Where it sits
Use social-listening and positioning-audit to find credible themes. Use social-proof-mining when a proof point requires approval. Use campaign-brief for launch communications and cross-platform-distribution when the LinkedIn post has a role in a broader plan.
