Turn corporate expertise into credible LinkedIn posts, newsletters, and participation plans using Ilkay Özkisaoglu's public tips. Use for CEOs, corporate influencers, and B2B experts seeking professional visibility and trust.
Installs into .claude/skills of the current project.
Are you the author of Oezkisaoglu Linkedin Tipps?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/getedgehq-oezkisaoglu-linkedin-tipps)
---
name: oezkisaoglu-linkedin-tipps
description: "Turn corporate expertise into credible LinkedIn posts, newsletters, and participation plans using Ilkay Özkisaoglu's public tips. Use for CEOs, corporate influencers, and B2B experts seeking professional visibility and trust."
---
# Corporate visibility with #Ilkays365LinkedInTipps
Based on Ilkay Özkisaoglu's public method. Not affiliated with or endorsed by Ilkay Özkisaoglu.
## When to use
Use this skill to develop or improve a LinkedIn thought-leadership deliverable for a CEO, technical expert, founder, or corporate influencer. It supports a single post, a newsletter issue, or a repeatable corporate visibility plan. It is particularly suited to Mittelstand and industrial B2B organizations whose expertise exceeds their public recognition.
The intended result is useful professional content with a recognizable expert perspective, a defensible connection to corporate purpose, and a plan for conversation and learning. Select the requested deliverable before drafting. A post request does not require a new newsletter, employee program, or sales campaign.
The public series began as recurring tips and evolved into a newsletter. Its name does not impose daily publishing on every client. This package is a documented synthesis, not access to a private curriculum. The numbered procedure and drafting structures are package adaptations. Keep their attribution separate from the public principles explained in the references.
## Procedure
1. **Set the professional purpose.** Read [references/method.md](references/method.md), section 1. Identify the audience, its practical decision, the expert's relevant experience, and the business outcome. Record missing inputs as assumptions or questions. Prefer a specific audience over an ambition to reach everyone.
2. **Choose the deliverable and scope.** Use [templates/output-template.md](templates/output-template.md). Select a post, newsletter, or visibility plan. Complete only applicable fields, while retaining evidence, participation, and measurement notes. Preserve the user's language, audience, and publication constraints.
3. **Establish the expert territory.** Follow section 2 of [references/method.md](references/method.md). Define a clear perspective and a small set of relevant subject areas. Check Konsistenz: the proposed contribution should fit the person's values, expertise, and corporate role.
4. **Gather genuine material.** Apply section 3 of [references/method.md](references/method.md). Request an observation, project lesson, interview, demonstration, or sourced fact. Distinguish what happened from what the expert infers. Never manufacture customer experiences, credentials, quotations, or results to fill a gap.
5. **Convert expertise into a useful tip.** Consult illustration 1 in [examples/worked-examples.md](examples/worked-examples.md). Explain the problem, offer a concrete perspective, and give the reader a practical next action. Replace promotional adjectives with substance. Make specialist material understandable without removing its important limitations.
6. **Select a feasible format.** Apply section 4 of [references/method.md](references/method.md). Match depth and production capacity to text, newsletter, interview, video, or Live. If a format creates avoidance, start with one the expert can sustain. Add demanding production only when it serves the audience.
7. **Create continuity and subscriber value.** Follow section 5 of [references/method.md](references/method.md). Set Kontinuität independently from thematic consistency. For newsletters, state the recurring reader benefit and connect issues through a coherent topic. Do not depend on historical hashtag-follow mechanics.
8. **Connect personal and corporate visibility.** Read section 6 of [references/method.md](references/method.md). Show how the expert's knowledge helps the company become understood. For employee participation, provide boundaries and training while protecting individual voices. Avoid distributing identical posts for everyone to publish.
9. **Plan meaningful participation.** Use section 7 of [references/method.md](references/method.md) and the participation fields in [templates/output-template.md](templates/output-template.md). Identify relevant conversations, draft substantive contributions, and assign response ownership. Invite professional discussion with a question the audience can actually answer.
10. **Choose evidence of progress.** Follow section 8 of [references/method.md](references/method.md). Define success before comparing formats. Include audience relevance and business conversations alongside available visibility indicators. Treat likes, follower counts, and published case results as limited signals rather than promised outcomes.
11. **Review and repair.** Run [checklists/review-checklist.md](checklists/review-checklist.md). Resolve failed checks or identify the specific missing input. Use illustration 2 in [examples/worked-examples.md](examples/worked-examples.md) to check newsletter depth, employee autonomy, and realistic production choices.
12. **Return a reviewable package.** Complete [templates/output-template.md](templates/output-template.md) with the final draft, assumptions, evidence, participation plan, and review date. Explain the material improvements briefly. Use [references/sources.md](references/sources.md) for method attribution; cite the client's own factual evidence separately. Publishing and contacting people require task authorization.
## Files in this skill
- [SLUG.txt](SLUG.txt): Portable package identifier.
- [SKILL.md](SKILL.md): Entry point, usage boundaries, and procedure.
- [references/method.md](references/method.md): Cited principles, decisions, adaptations, and edge cases.
- [references/sources.md](references/sources.md): Numbered register of public sources fetched with curl.
- [examples/worked-examples.md](examples/worked-examples.md): Invented before-and-after illustrations with rule explanations.
- [templates/output-template.md](templates/output-template.md): Deliverable fields and instructions for filling them.
- [checklists/review-checklist.md](checklists/review-checklist.md): Pass/fail checks and repairs for common mistakes.