skills/building-a-promotion-case/SKILL.md
Help users get promoted at work. Use when someone is preparing for a promotion conversation, building their case for advancement, trying to understand what's blocking their promotion, or figuring out how to get to the next level in their career.
npx skillsauth add cvillamarp-lgtm/skillspodcast building-a-promotion-caseInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user build a compelling case for promotion using strategies from 17 product leaders.
When the user asks for help with getting promoted:
Ian McAllister: "I never talked to my manager about promotion. I just focused on growing my book of business. The result was I got promoted several times." Optimize for impact—promotions follow.
Christian Idiodi: "I'm promoting you to do the job, not to learn the job." You need to already be performing at the next level before the title comes. Practice "director things" before you're a director.
Claire Vo: "The conversation needs to be about what you being in a different position does for the company. Instead of 'I want to be a director,' say 'You have nine direct reports—you need leverage here.'"
Ethan Evans: "(1) Do your current job well. (2) Ask your boss how you can help. (3) Do what they ask. (4) Say 'Is there work that helps you AND helps me reach my goal?' (5) Repeat." Build partnership, not pressure.
Jeffrey Pfeffer: "No one is going to promote you if they don't know who you are. Competence alone is insufficient. You must have visibility to match your substance."
Jiaona Zhang: "Be known for something specific—complex launches, technical depth, regulatory expertise. When you're known for excellence, responsibility flows to you naturally."
Julie Zhuo: "You don't need the title to do manager tasks. Mentor an intern. Lead a process. Be an onboarding buddy. Prove competency before asking for the role."
Jackie Bavaro: "Say 'I'd like to grow into X at some point in the future. What should I work on now so I'll be ready?' This brings your manager onto your side instead of making them defensive."
Nikhyl Singhal: Four common blockers: (1) Lack of advocacy—no one is championing you. (2) Role doesn't exist at your company. (3) Impatience—you're not ready yet. (4) Development gap you're not seeing.
Tamar Yehoshua: "You're not going to get the next job unless you do really well at the one you're in. Knock it out of the park. Master the table stakes before reaching for more."
For all 22 insights from 17 guests, see references/guest-insights.md
testing
Help users communicate more effectively in writing. Use when someone is drafting memos, emails, strategy docs, announcements, or any written communication that needs to be clear, concise, and persuasive.
documentation
Help users write effective specs and design documents. Use when someone is creating technical specs, feature specs, design docs, or trying to communicate product requirements to engineering and design teams.
development
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
tools
Help users define their North Star metric. Use when someone is choosing their primary success metric, trying to align the team around a key measure, struggling with metric proliferation, or setting up their measurement strategy.