Agent skill

Executive Communication

by RefoundAI in RefoundAI/lenny-skills

Help users master the high-stakes communication required to navigate executive reviews, board meetings, and strategic decision-making with clarity and confidence.

MITAuto-check passed

Install Executive Communication

skills CLI
$ npx skills add RefoundAI/lenny-skills --skill executive-communication -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install RefoundAI/lenny-skills executive-communication --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/RefoundAI/lenny-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/executive-communication .claude/skills/executive-communication && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
executive-communication
GitHub stars
1.4k
Token cost
~2.2k tokens
SKILL.md length
1,258 words
Files
3 (incl. references)
Skills in repo
76
Repo updated
First seen
Licence
MIT

At a glance

Help users master the high-stakes communication required to navigate executive reviews, board meetings, and strategic decision-making with clarity and confidence.

  • Works in 4 steps: Analyze the audience - Identify the… → Structure the narrative - Use frameworks… → Frame the tradeoffs - Present choices in… → …
  • SKILL.md covers How to Help, Core Principles, Templates & Frameworks and Questions to Help Users, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Executive Communication is an agent skill from RefoundAI/lenny-skills. Help users master the high-stakes communication required to navigate executive reviews, board meetings, and strategic decision-making with clarity and confidence.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/artifacts.md` and `references/guest-insights.md`).

The repository describes itself as: 86 product management skills from Lenny's Podcast for Claude Code and AI agents. Hiring, user research, strategy, shipping, and more. The licence is MIT.

Example prompts

  • “/executive-communication”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Analyze the audience - Identify the specific values and communication styles of the executives involved to tailor the message effectively.
  2. Structure the narrative - Use frameworks like SCR or the Pyramid Principle to ensure the core message and conclusion are delivered upfront.
  3. Frame the tradeoffs - Present choices in terms of company-wide objectives rather than team capacity to facilitate better prioritization.
  4. Iterate on delivery - Refine the medium and language based on feedback to ensure the message is received as intended and project confidence.

What it can do on your machine

Read from SKILL.md and the folder at commit 13598cc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Executive Communication loads about 2.2k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 47 tokens; SKILL.md has 1,258 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~47
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from RefoundAI/lenny-skills at commit 13598cc, republished under its MIT licence (© RefoundAI). 1,258 words, ~2,158 tokens.

Download SKILL.mdSave it as .claude/skills/executive-communication/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
executive-communication
description
Help users master the high-stakes communication required to navigate executive reviews, board meetings, and strategic decision-making with clarity and confidence.

Executive Communication

Master the art of framing, transparency, and decision-ready communication to build trust with leadership.

Help the user with executive communication using insights from 9 guests and posts across Lenny's Podcast and Newsletter.

How to Help

  1. Analyze the audience - Identify the specific values and communication styles of the executives involved to tailor the message effectively.
  2. Structure the narrative - Use frameworks like SCR or the Pyramid Principle to ensure the core message and conclusion are delivered upfront.
  3. Frame the tradeoffs - Present choices in terms of company-wide objectives rather than team capacity to facilitate better prioritization.
  4. Iterate on delivery - Refine the medium and language based on feedback to ensure the message is received as intended and project confidence.

Core Principles

Start from the obvious

Casey Winters: "One of the ways I try to frame it to my team is if you're not an executive, whatever you're working on, you're basically writing and telling a story. And when you talk to an exec about that story, you have to start with chapter one, which is what part of the company strategy are you working on? What metrics are you trying to improve? What assumptions are you making that are guiding what you're building?"

Begin your narrative at the last point in the story that is completely obvious to your audience. This ensures everyone is aligned before you dive into new assumptions or complex project details.

Align with leader values

From "A PM’s guide to influence": "It’s often more effective to speak their language and demonstrate how my proposal will help them reach their goals, not mine, because stakeholders are focused on their own problems and are more receptive to proposals that address what’s already top of mind for them."

Overcome skepticism by recasting your proposal to prioritize the leader's specific philosophy. Pivot the framing from internal team metrics to the stakeholder's primary business values.

Control the bad news narrative

From "Communicating bad news - Issue 26": "The trick to sharing bad news effectively is to imagine being on the other side of the table. What would you want to know if you were in charge? If you’re like most people, you’d want to know everything, as soon as possible, plus exactly how to best move forward. So start there."

Ensure stakeholders hear bad news directly from you first. Proactively provide context and a clear path forward rather than just reporting a failure in isolation.

Frame tradeoffs by goals

From "How to communicate tradeoffs so leaders will listen": "While presenting the pros and cons between two priorities, I’d somehow always end up committing to doing both, and in less time than I had planned. As you’d expect, this usually went … badly. I’d burn myself out or, worse, burn out my team."

Force prioritization by framing choices in terms of company goals rather than team capacity. Present clear rankings of what falls above and below the line to make the cost of projects visible.

Take radical ownership of reception

From "Essential reading for product builders—part 2": "But make no mistake, when this happens, it is your fault. You have to sit down and ask questions from a place of humility to hear what they took away from what you said. Take full responsibility for any discrepancy from what you intended and make corrections with your entire audience."

Take full personal responsibility for how your communication is received. Treat any gap between your intended message and the audience's understanding as your own failure to clarify.

Project assertive confidence

From "Getting buy-in": "Presence is a combination of verbal cues, body language, and mindset. One of the actions you can take to improve your presence is to stop saying “sorry” when it’s not warranted."

Build executive presence by replacing submissive qualifiers like 'just' or 'actually' with direct phrasing. Swap apologies for mistakes with immediate commitments to fix the issue.

Structure for decision value

From "Getting buy-in": "Good storytelling means you present a narrative that resonates with your audience. Focus on why stakeholders should care about the idea. For example, prioritizing a recommendation feature will improve conversion or changing the sprint process will free up time to reduce tech debt."

Strip away any context or backstory that does not directly support a decision. Structure the message around the specific value the proposal provides to the stakeholder's own metrics.

Show full SKILL.md (535 more words)Show less

Templates & Frameworks

  • McKinsey Situation-Complication-Resolution (SCR) Framework (This Week #3: Finding product/market fit, interviewing for a Director of PM role, and structuring discussions with senior leaders) - A storytelling framework for structuring business communications, especially presentations to senior leaders. Can be applied to any medium and many contexts.
  • SCQA / Pyramid Principle for Executive Communication (Essential reading for product builders—part 2) - A four-part framework for structuring any executive communication: Situation, Complication, Question, Answer. The answer sits at the top of a pyramid with evide
  • Communicating Failure to Leadership — 7-Step Framework (This Week #7: Effectively communicating about a failure to execs, managing founder expectations, and hiring a Director of PM) - A structured approach for presenting a failed project or missed goals to executive stakeholders, including mindset preparation and delivery tactics
  • Tradeoff Decision Meeting Facilitation Guide (How to communicate tradeoffs so leaders will listen) - Step-by-step guide for running a meeting where you present a tradeoff decision document to executives.
  • Weekly Leadership Update (How to make an impact in your first 90 days) - A regular async written update format for new leaders to build trust and visibility
  • Executive Patterns Notes Doc (A PM’s guide to influence) - A running document to track executive behavior patterns—questions they ask, feedback they give—to anticipate reactions in future meetings
  • CEO Test for Tradeoff Framing (How to communicate tradeoffs so leaders will listen) - A simple mental model for ensuring your tradeoff communication hits the right level — ask yourself what the CEO would want to know.
  • Dinosaur Brain Executive Reviews (Ami Vora) - A framework for structuring product reviews based on the limited cognitive load executives can dedicate to any single project.
  • Buy-in Meeting Narrative Structure (Megan Cook) - A framework for opening a pitch or proposal meeting with executives.

See references/artifacts.md for the full list with details.

Questions to Help Users

  • "Who is your primary executive audience and what do they value most?"
  • "What is the single most important decision or takeaway you need from this interaction?"
  • "Have you structured your message to lead with the conclusion rather than a build-up?"
  • "How does your proposal directly impact the company's top-level metrics or strategic goals?"
  • "If you are delivering bad news, what is your recommended plan of action and timeline for recovery?"
  • "Are there any qualifiers or submissive language patterns in your draft that could be removed?"

Common Mistakes to Flag

  • The 'Movie Arc' reveal - Building tension for a big reveal at the end wastes executive time and risks the meeting being cut short before the core point is made.
  • Focusing on team capacity - Framing tradeoffs as 'we don't have enough people' instead of 'we are choosing Goal A over Goal B' makes the team look like a bottleneck.
  • Defensive communication gaps - Treating a misunderstanding as the audience's fault instead of taking ownership of the communication gap undermines your leadership presence.
  • Including excessive backstory - Adding context that doesn't directly support the required decision confuses the core message and slows down the operating cadence.
  • Using submissive language - Phrases like 'Sorry to bother you' or 'I just wanted to' project a lack of confidence and lower your perceived executive presence.

Deep Dive

For all 20 sourced insights from 9 guests, see references/guest-insights.md

  • Product Reviews
  • Managing Up
  • Running Meetings
  • Written Communication

© RefoundAI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/executive-communication of RefoundAI/lenny-skills.

  • SKILL.md
  • references/artifacts.md
  • references/guest-insights.md

Open the folder on GitHubat commit 13598cc

Compare with similar skills

Executive Communication next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Executive Communication compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Executive Communication this skillRefoundAI/lenny-skills1.4k—~2.2kAutomated safety check: PassMIT
Executealirezarezvani/claude-skills28k—~831Automated safety check: PassMIT
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
Requirementsrizsotto/Bear6.5k—~2kAutomated safety check: PassGPL-3.0
How To Communicatedatabasus/databasus8.8k—~3.9kAutomated safety check: PassMIT
Music Masterruvnet/ruflo74k—~270Automated safety check: PassMIT

Similar skills

  • Execute

    alirezarezvani/claude-skills

    /cs:execute <decision — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.

    28k GitHub stars~831 tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Requirements

    rizsotto/Bear

    Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…

    6.5k GitHub stars~2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • How To Communicate

    databasus/databasus

    Communicate clearly in every response, progress update and agent-authored document.

    8.8k GitHub stars~3.9k tokensUpdated 15 days ago
    DatabasesAuto-check passed
  • Music Master

    ruvnet/ruflo

    Run a mastering pass (LUFS loudness normalization + peak limiting) on an existing production

    74k GitHub stars~270 tokensUpdated today
    DatabasesAuto-check passed
  • Breadcrumb Navigation

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Implement accessible breadcrumb navigation.

    74k GitHub stars~418 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from RefoundAI/lenny-skills

All 76 skills in this repo
  • Customer Interviews

    RefoundAI/lenny-skills

    Help users conduct high-impact customer interviews that move beyond surface-level feature requests to identify root emotional frustrations and specific causal triggers.

    1.4k GitHub stars~1.7k tokensUpdated 2 mo ago
    Auto-check passed
  • Time Energy Management

    RefoundAI/lenny-skills

    Help users master their personal output by shifting from reactive scheduling to intentional energy management, internal trigger mastery, and proactive boundary setting.

    1.4k GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check passed
  • User Onboarding Activation

    RefoundAI/lenny-skills

    Help users reach their first moment of core value by optimizing the first-run experience, removing friction, and aligning product design with psychological triggers.

    1.4k GitHub stars~2.1k tokensUpdated 2 mo ago
    Auto-check passed
  • Acquisition Channels

    RefoundAI/lenny-skills

    Help users identify unique distribution advantages and master the lifecycle of acquisition channels to build a sustainable engine for growth and retention.

    1.4k GitHub stars~2.2k tokensUpdated 2 mo ago
    Auto-check passed
  • AI Assisted Prototyping

    RefoundAI/lenny-skills

    Help users build functional product prototypes from natural language or visual mocks using AI coding tools.

    1.4k GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check passed
  • AI Evals

    RefoundAI/lenny-skills

    Help users build robust infrastructure for measuring, monitoring, and iterating on AI product performance using human, code-based, and LLM-as-a-judge methodologies.

    1.4k GitHub stars~1.7k tokensUpdated 2 mo ago
    Auto-check passed

Questions about Executive Communication

What does Executive Communication do?

Help users master the high-stakes communication required to navigate executive reviews, board meetings, and strategic decision-making with clarity and confidence. Executive Communication is an agent skill from RefoundAI/lenny-skills. Help users master the high-stakes communication required to navigate executive reviews, board meetings, and strategic decision-making with clarity and confidence.

How do I install Executive Communication in Claude Code?

Run `npx skills add RefoundAI/lenny-skills --skill executive-communication -a claude-code`. Or copy the skill folder (skills/executive-communication in RefoundAI/lenny-skills) into .claude/skills/executive-communication in your project. Claude Code loads it when a task matches its description.

How do I install Executive Communication in Codex?

Run `npx skills add RefoundAI/lenny-skills --skill executive-communication -a codex`. Or copy the skill folder (skills/executive-communication in RefoundAI/lenny-skills) into .agents/skills/executive-communication in your project. Codex loads it when a task matches its description.

Can I use Executive Communication in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add RefoundAI/lenny-skills --skill executive-communication -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/executive-communication, .gemini/skills/executive-communication, .github/skills/executive-communication and .opencode/skills/executive-communication in your project.

What does Executive Communication need to run?

SKILL.md names no scripts, command-line tools or credentials: Executive Communication is instructions for the agent only.

Does Executive Communication access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Executive Communication safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Executive Communication use?

Executive Communication is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Executive Communication use?

About 2.2k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 11k tokens, read only when the agent opens those files.

What are the alternatives to Executive Communication?

Skills that share tags, products or a category with Executive Communication: Execute (alirezarezvani/claude-skills, 28k stars), Debugging Executions (n8n-io/n8n, 207k stars), Requirements (rizsotto/Bear, 6.5k stars) and How To Communicate (databasus/databasus, 8.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Executive Communication?

RefoundAI (a GitHub organization) maintains it in RefoundAI/lenny-skills, which has 1,377 GitHub stars. The repository holds 76 skills in this directory. The repository was last updated on July 16, 2026.

Source: RefoundAI/lenny-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.