Build a compelling promotion case by diagnosing blockers and framing advancement as solving company problems.
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
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add refoundai/lenny-skills --skill building-a-promotion-caseCompatible with
Supported agents
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:
epx add refoundai/lenny-skills --skill building-a-promotion-caseFetches 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:
.cursor/skills/building-a-promotion-case
Restart Cursor to activate building-a-promotion-case. Access via /building-a-promotion-casein your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
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.
ui-ux-pro-max
nextlevelbuilder/ui-ux-pro-max-skill · Frontend · same category
pyqt6-ui-development-rules
oimiragieo/agent-studio · Frontend · same category
nextjs-seo
laguagu/claude-code-nextjs-skills · Frontend · same category
svg-logo-designer
rknall/claude-skills · Frontend · same category
game-design-core
omer-metin/skills-for-antigravity · Frontend · same category
css
mindrally/skills · Frontend · same category
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