neuhaus-thought-leadership
Build CEO personal branding strategies and execution plans using Moritz Neuhaus's public Thought-Leadership-as-a-Service approach. Use for executive positioning, LinkedIn content, stakeholder trust, distribution, and measurable business impact.
- License 许可
- Apache-2.0
- 所属仓库
- getedgehq/skills
- 最近更新
- 2026-11-12
- Stars
- ★ 5
- Forks
- 0
01 前言 Front Matter
- name
- neuhaus-thought-leadership
- description
- Build CEO personal branding strategies and execution plans using Moritz Neuhaus's public Thought-Leadership-as-a-Service approach. Use for executive positioning, LinkedIn content, stakeholder trust, distribution, and measurable business impact.
02 资源文件 7
- 参考文档checklists/review-checklist.md5.5 KB
- 参考文档DERIVATION.json2.7 KB
- 参考文档examples/worked-examples.md8.5 KB
- 许可证LICENSE10.5 KB
- 参考文档references/method.md14.2 KB
- 参考文档references/sources.md4.6 KB
- 参考文档templates/output-template.md8.0 KB
03 SKILL.md 正文
CEO Thought Leadership: Strategy and Execution
Based on Moritz Neuhaus's public method. Not affiliated with or endorsed by Moritz Neuhaus.
When to use
Use this skill when a CEO, established founder, consulting partner, or executive team needs a credible public position connected to company objectives and a practical system for executing it. It supports initial brand strategy, an existing presence that attracts the wrong audience, and ongoing content and distribution decisions. The deliverable is a CEO positioning and execution brief, with sample content, responsibilities, and business measurement.
The public approach connects reputation with customer acquisition, talent attraction, and industry relevance. It combines strategic diagnosis with delivery rather than treating a content calendar as the strategy. INSIGHT's claimed experience of 475+ executive branding strategies is background about the agency, not proof that any proposed plan will succeed. This package reconstructs published guidance; it does not claim access to the complete INSIGHT Thought Leader Framework.
Procedure
-
Establish scope and readiness. Read references/method.md, sections 1 and 2. Record the business situation, existing expertise, executive role, available support, and desired deliverable. Ask only for missing information that changes the recommendation. If leadership credibility or business fundamentals are weak, document the prerequisite work before proposing reputation amplification.
-
Choose the business job. Use section 3 of references/method.md. Select the primary outcome and stakeholder group, then define what a qualified result means. Distinguish customer conversations, hiring outcomes, and industry influence. Capture a baseline or mark it unknown; do not invent targets or historical performance.
-
Map the environment. Follow section 4 of references/method.md. Examine internal and external stakeholders, competitive narratives, existing public material, role models, and anti-role models. Explain what the CEO can credibly contribute that the audience does not already receive. Treat admired accounts as context rather than transferable formulas.
-
Write the positioning. Apply section 5 of references/method.md and the positioning fields in templates/output-template.md. Define audience, problem, expertise, stance, evidence, and company connection. Prefer a defensible niche contribution to a generic promise of inspiration or an unsupported claim to industry leadership.
-
Set the voice and boundaries. Read section 6 of references/method.md. Combine demonstrated competence with human warmth. Identify personal experiences the CEO wants to share and private information they wish to keep private. For employed executives, clarify the relationship with board colleagues and corporate communications before drafting potentially sensitive claims.
-
Design the public destination. Use section 7 of references/method.md and the profile fields in templates/output-template.md. Make the profile communicate relevance, proof, and an appropriate next action. Select channels according to stakeholder behavior and objectives, with LinkedIn as the usual B2B starting point.
-
Build the execution system. Follow section 8 of references/method.md. Assign one coordinator and clear responsibilities for interviews, writing, design, production, executive review, and reporting. Agree a realistic CEO contribution schedule. Outsource preparation and production while preserving the executive's actual views and participation.
-
Produce an initial content batch. Use section 9 of references/method.md and examples/worked-examples.md. Draft concrete, evidence-backed material that connects expertise and experience to a stakeholder problem. Explain why each piece exists. Label illustrations and unresolved evidence explicitly; never manufacture first-person experiences.
-
Plan distribution and dialogue. Apply section 10 of references/method.md. Define relevant conversations and an initial organic distribution plan. Add media, events, video, webinars, podcasts, or Thought Leader Ads only when they serve the chosen objective and fit capacity. A plan does not itself authorize publishing, outreach, or advertising expenditure.
-
Measure and adapt. Use section 11 of references/method.md and the reporting fields in templates/output-template.md. Separate visibility, audience relevance, qualified outcomes, and revenue evidence. Plan monthly reporting and quarterly strategy reviews. Treat early signals as learning, and long-term industry recognition as an aspiration rather than a deadline guarantee.
-
Review and hand over. Apply checklists/review-checklist.md. Return the completed brief, sample content, unresolved inputs, owners, and next review date. Correct failed checks before marking a draft ready. For method attribution, consult references/sources.md and preserve the distinction between public claims and this package's operational additions.
Files in this skill
- SLUG.txt: Package identifier for naming and installation.
- SKILL.md: Entry point, activation guidance, and procedure.
- references/method.md: Detailed method, decision rules, limitations, and source citations.
- references/sources.md: Eight fetched public sources and their contributions.
- examples/worked-examples.md: Invented before-and-after applications with rule explanations.
- templates/output-template.md: Fill-in deliverable with field-level instructions.
- checklists/review-checklist.md: Pass/fail criteria, failure modes, and corrective actions.
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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.