Build a compelling promotion case by diagnosing blockers and framing advancement as solving company problems.
Works with
Diagnose the situation by understanding current role, target role, manager relationship, and identifying whether blockers are visibility, advocacy, role availability, or skill gaps
Core principle: perform at the next level before requesting the title; promotions recognize readiness, they don't develop it
Frame promotion conversations around business impact and company needs,
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbuilding-a-promotion-caseExecute the skills CLI command in your project's root directory to begin installation:
Fetches building-a-promotion-case from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate building-a-promotion-case. Access via /building-a-promotion-case in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
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
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
building-a-promotion-case has been reliable in day-to-day use. Documentation quality is above average for community skills.
building-a-promotion-case is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: building-a-promotion-case is the kind of skill you can hand to a new teammate without a long onboarding doc.
building-a-promotion-case has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: building-a-promotion-case is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added building-a-promotion-case from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: building-a-promotion-case is focused, and the summary matches what you get after install.
building-a-promotion-case has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: building-a-promotion-case is focused, and the summary matches what you get after install.
building-a-promotion-case is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 39