executive-presence
GitHub针对高管汇报、董事会问答等高压力场景，提供具备领导力的沟通指导。通过BLUF结构、精简表达、应对难题及展现沉稳举止等具体行为建议，帮助用户提升气场与专业度，避免空泛建议。
触发场景
安装
npx skills add mohitagw15856/pm-claude-skills --skill executive-presence -g -y
SKILL.md
Frontmatter
{
"name": "executive-presence",
"description": "Sharpen how you show up in high-stakes rooms — communicate with gravitas, concision, and confidence. Use when asked to improve executive presence, prepare to present to leadership, sound more senior, command a room, or get coaching before a big meeting. Produces specific guidance — how to open, structure answers (BLUF\/headline-first), handle tough questions, project calm, and the habits to drop, tuned to the moment."
}
Executive Presence Skill
Executive presence isn't a personality you're born with — it's a set of learnable behaviours: leading with the answer, speaking concisely, staying composed under pressure, and projecting calm conviction. This skill gives specific, actionable guidance for a particular high-stakes moment (a leadership presentation, a board Q&A, a tense meeting) — not generic "be confident" advice.
Required Inputs
Ask for these only if they aren't already provided:
- The moment — what you're walking into (present to execs, defend a plan, answer a hostile question, lead a crisis call).
- The audience — who's in the room, what they care about, your standing with them.
- Your goal — the decision/impression you want, and the message.
- Your concern — what you're worried about (rambling, nerves, getting derailed, sounding junior).
Output Format
Executive Presence: [the moment]
1. Lead with the answer — for this situation, the BLUF/headline-first version: state the conclusion or ask in the first sentence, then support it. Executives want the bottom line, then the why — not a build-up to it.
2. Be concise — the 2–3 points that matter, cut to the essential. Specific advice on what to drop. (Brevity reads as command; over-explaining reads as uncertainty.)
3. Handle the hard question — how to field a challenge or a question you don't fully know: acknowledge, answer the part you can, commit to follow up on the rest — calmly, without defensiveness or bluffing. A prepared line for "I don't know."
4. Project calm — concrete cues: pace (slow down, pause instead of filler), posture, owning silence, not rushing to fill gaps. How to reset if you feel flustered mid-answer.
5. Language to drop — the hedges and minimisers that undercut you ("I just think maybe…", "does that make sense?", "sorry, quick question") and the stronger replacements.
6. The open & close — a strong first line for the moment, and how to land the ending on the ask.
Quality Checks
- Advice is specific to the actual moment, not generic "be confident"
- It coaches answer-first / BLUF structure with an example for this situation
- There's a concrete plan for the hard question and for "I don't know"
- Names specific hedging language to drop, with replacements
- Includes calm/composure cues (pace, pauses, silence) — behaviours, not vibes
- Gives a strong opening and a clear close on the ask
Anti-Patterns
- Do not give generic advice ("be more confident") — coach specific behaviours for this room
- Do not bury the lead — answer-first; making execs wait for the point reads as junior
- Do not bluff a tough question — calm "here's what I know, I'll confirm the rest" beats a confident wrong answer
- Do not equate presence with talking more — concision and comfortable silence project more authority
- Do not coach a persona — it's behaviours layered on who you are, not an act that won't survive pressure
Based On
Executive-communication practice — BLUF / Minto Pyramid (answer-first), composure under pressure, and decisive, hedge-free language.
版本历史
- a38bc30 当前 2026-07-05 11:12
