building-a-promotion-case

building-a-promotion-case is a skill for Claude Code, Codex from cnfeat/top-pm-skills. It costs 51 tokens per session (946 once invoked), scanned A, original, MIT.

A career-planning guide for preparing a case for promotion at work.

In plain words
What is it for?
Use it to prepare a promotion conversation, understand what may be holding you back, and plan ways to demonstrate readiness for the next role.
Why use it?
It helps separate possible blockers—such as visibility, support, role availability, or skill gaps—and frame advancement around measurable impact.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare a promotion conversation, understand what may be holding you back, and plan ways to demonstrate readiness for the next role.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cnfeat/top-pm-skills/building-a-promotion-case
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cnfeat/top-pm-skills --skill building-a-promotion-case
Clone the repo
git clone --depth 1 https://github.com/cnfeat/top-pm-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for building-a-promotion-case

README.md
[![agentmods](https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/building-a-promotion-case/github.svg)](https://agentmods.dev/skills/cnfeat/top-pm-skills/building-a-promotion-case)
Your own site
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/building-a-promotion-case"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/building-a-promotion-case/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for building-a-promotion-case

Your own site · 80×15
<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/building-a-promotion-case"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/building-a-promotion-case.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 946 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.00946
Opus 5 $0.00026 $0.00473
Sonnet 5 $0.00010 $0.00189
Haiku 4.5 $0.00005 $0.00095

Measured 12d ago against content hash 40ec539eae84, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

building-a-promotion-case scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

参考skill/lenny-skills-main (2)/lenny-skills-main/skills/building-a-promotion-case/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Building a Promotion Case

Help the user build a compelling case for promotion using strategies from 17 product leaders.

How to Help

When the user asks for help with getting promoted:

  1. Diagnose the situation - Ask about their current role, target role, and relationship with their manager
  2. Identify blockers - Help determine if the issue is visibility, advocacy, role availability, or skill gaps
  3. Build the case - Help frame the promotion as solving a company problem, not a personal milestone
  4. Coach on tactics - Share specific approaches for conversations and demonstrating readiness

Core Principles

Focus on impact, not promotion

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.

Promotions recognize, they don't develop

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.

Frame it as solving their problem

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.'"

Use the Magic Loop

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.

Visibility is prerequisite

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."

Build a superpower reputation

Jiaona Zhang: "Be known for something specific—complex launches, technical depth, regulatory expertise. When you're known for excellence, responsibility flows to you naturally."

Read the full file on GitHub · 77 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 77 lines · 51 tokens per session scan A 40ec539eae84

Subscribe to this mod's changes

building-a-promotion-case is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 946 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens