[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CFDP62SAS22Z0P0RHN7T09":3,"skill-same:01M7CFDP62SAS22Z0P0RHN7T09":75},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":5,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7CFDP62SAS22Z0P0RHN7T09","oezkisaoglu-linkedin-tipps",null,"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.","getedgehq\u002Fskills","getedgehq","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F327350993?v=4","01M7CEH5YJQYF1PB3MDG9PA5HX","01M7CEH5ZAPY8TX4H3E04KM875",5,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Foezkisaoglu-linkedin-tipps\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Foezkisaoglu-linkedin-tipps\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: oezkisaoglu-linkedin-tipps\ndescription: \"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.\"\n---\n\n# Corporate visibility with #Ilkays365LinkedInTipps\n\nBased on Ilkay Özkisaoglu's public method. Not affiliated with or endorsed by Ilkay Özkisaoglu.\n\n## When to use\n\nUse 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.\n\nThe 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.\n\nThe 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.\n\n## Procedure\n\n1. **Set the professional purpose.** Read [references\u002Fmethod.md](references\u002Fmethod.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.\n\n2. **Choose the deliverable and scope.** Use [templates\u002Foutput-template.md](templates\u002Foutput-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.\n\n3. **Establish the expert territory.** Follow section 2 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n4. **Gather genuine material.** Apply section 3 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n5. **Convert expertise into a useful tip.** Consult illustration 1 in [examples\u002Fworked-examples.md](examples\u002Fworked-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.\n\n6. **Select a feasible format.** Apply section 4 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n7. **Create continuity and subscriber value.** Follow section 5 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n8. **Connect personal and corporate visibility.** Read section 6 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n9. **Plan meaningful participation.** Use section 7 of [references\u002Fmethod.md](references\u002Fmethod.md) and the participation fields in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). Identify relevant conversations, draft substantive contributions, and assign response ownership. Invite professional discussion with a question the audience can actually answer.\n\n10. **Choose evidence of progress.** Follow section 8 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n11. **Review and repair.** Run [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md). Resolve failed checks or identify the specific missing input. Use illustration 2 in [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md) to check newsletter depth, employee autonomy, and realistic production choices.\n\n12. **Return a reviewable package.** Complete [templates\u002Foutput-template.md](templates\u002Foutput-template.md) with the final draft, assumptions, evidence, participation plan, and review date. Explain the material improvements briefly. Use [references\u002Fsources.md](references\u002Fsources.md) for method attribution; cite the client's own factual evidence separately. Publishing and contacting people require task authorization.\n\n## Files in this skill\n\n- [SLUG.txt](SLUG.txt): Portable package identifier.\n- [SKILL.md](SKILL.md): Entry point, usage boundaries, and procedure.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Cited principles, decisions, adaptations, and edge cases.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered register of public sources fetched with curl.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Invented before-and-after illustrations with rule explanations.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Deliverable fields and instructions for filling them.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail checks and repairs for common mistakes.\n","# Corporate visibility with #Ilkays365LinkedInTipps\n\nBased on Ilkay Özkisaoglu's public method. Not affiliated with or endorsed by Ilkay Özkisaoglu.\n\n## When to use\n\nUse 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.\n\nThe 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.\n\nThe 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.\n\n## Procedure\n\n1. **Set the professional purpose.** Read [references\u002Fmethod.md](references\u002Fmethod.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.\n\n2. **Choose the deliverable and scope.** Use [templates\u002Foutput-template.md](templates\u002Foutput-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.\n\n3. **Establish the expert territory.** Follow section 2 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n4. **Gather genuine material.** Apply section 3 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n5. **Convert expertise into a useful tip.** Consult illustration 1 in [examples\u002Fworked-examples.md](examples\u002Fworked-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.\n\n6. **Select a feasible format.** Apply section 4 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n7. **Create continuity and subscriber value.** Follow section 5 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n8. **Connect personal and corporate visibility.** Read section 6 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n9. **Plan meaningful participation.** Use section 7 of [references\u002Fmethod.md](references\u002Fmethod.md) and the participation fields in [templates\u002Foutput-template.md](templates\u002Foutput-template.md). Identify relevant conversations, draft substantive contributions, and assign response ownership. Invite professional discussion with a question the audience can actually answer.\n\n10. **Choose evidence of progress.** Follow section 8 of [references\u002Fmethod.md](references\u002Fmethod.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.\n\n11. **Review and repair.** Run [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md). Resolve failed checks or identify the specific missing input. Use illustration 2 in [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md) to check newsletter depth, employee autonomy, and realistic production choices.\n\n12. **Return a reviewable package.** Complete [templates\u002Foutput-template.md](templates\u002Foutput-template.md) with the final draft, assumptions, evidence, participation plan, and review date. Explain the material improvements briefly. Use [references\u002Fsources.md](references\u002Fsources.md) for method attribution; cite the client's own factual evidence separately. Publishing and contacting people require task authorization.\n\n## Files in this skill\n\n- [SLUG.txt](SLUG.txt): Portable package identifier.\n- [SKILL.md](SKILL.md): Entry point, usage boundaries, and procedure.\n- [references\u002Fmethod.md](references\u002Fmethod.md): Cited principles, decisions, adaptations, and edge cases.\n- [references\u002Fsources.md](references\u002Fsources.md): Numbered register of public sources fetched with curl.\n- [examples\u002Fworked-examples.md](examples\u002Fworked-examples.md): Invented before-and-after illustrations with rule explanations.\n- [templates\u002Foutput-template.md](templates\u002Foutput-template.md): Deliverable fields and instructions for filling them.\n- [checklists\u002Freview-checklist.md](checklists\u002Freview-checklist.md): Pass\u002Ffail checks and repairs for common mistakes.\n",{"name":5,"description":7},"main","01960aeb08909dbd0c1a2d4f219cdb300099b8b9",0,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills","https:\u002F\u002Fgetedge.cc","https:\u002F\u002Fgithub.com\u002Fgetedgehq","2026-11-12 10:05:02",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add getedgehq\u002Fskills --skill oezkisaoglu-linkedin-tipps",{"tool":37,"command":38},"bunx","bunx skills add getedgehq\u002Fskills --skill oezkisaoglu-linkedin-tipps",{"tool":40,"command":41},"pnpm","pnpm dlx skills add getedgehq\u002Fskills --skill oezkisaoglu-linkedin-tipps","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Foezkisaoglu-linkedin-tipps\u002FSKILL.md",true,[45,51,55,59,63,67,71],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"checklists\u002Freview-checklist.md","REFERENCE","参考文档",5304,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Foezkisaoglu-linkedin-tipps\u002Fchecklists\u002Freview-checklist.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"DERIVATION.json",3367,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Foezkisaoglu-linkedin-tipps\u002FDERIVATION.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"examples\u002Fworked-examples.md",6889,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Foezkisaoglu-linkedin-tipps\u002Fexamples\u002Fworked-examples.md",{"path":60,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":15},"LICENSE","许可证",10756,{"path":64,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fmethod.md",13066,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Foezkisaoglu-linkedin-tipps\u002Freferences\u002Fmethod.md",{"path":68,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fsources.md",6310,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Foezkisaoglu-linkedin-tipps\u002Freferences\u002Fsources.md",{"path":72,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":73,"sourceHtmlUrl":74},"templates\u002Foutput-template.md",5476,"https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Foezkisaoglu-linkedin-tipps\u002Ftemplates\u002Foutput-template.md",[76,84,92,99,106,114],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CFVPC1P7JN60J5AN9AZZ5G","zero-downtime-cloud-move","Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzero-downtime-cloud-move\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CFVH8VN6G2KE8PBFD1CRMN","zayats-ceo-branding","Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fzayats-ceo-branding\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CFV9BB7G8K8CX9RKZ3GECX","yc-app-roast","YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks \"what would a YC partner think\", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-roast\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7CFV11Z1HB9EEWFQ6PCJ98X","yc-app-review","YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press \"Send my notes\" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fyc-app-review\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":110,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7CFTSVJV7XCSW62W39MX8CZ","x-growth-playbook","X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says \"analyse my X posts\", \"what works on my Twitter\", \"how do I grow on X\", \"what should I post next on X\", \"audit my X account\", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fx-growth-playbook\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":118,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":19},"01M7CFTK101S3P00MQ129G5YNH","workplan","Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: \"workplan\", \"work plan\", \"create a plan\", \"what's the plan\", \"where was I\", or when Claude detects a multi-step task that needs tracking.","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fgetedgehq\u002Fskills\u002Fblob\u002Fmain\u002Fworkplan\u002FSKILL.md",[],[]]