Promo Packet

Promo packet

A promotion packet is read by people who do not know your work, in a stack of others, against a written bar for the target level. It is decided not on how hard you worked but on whether you already operate at that level and left durable impact. Packets fail when they narrate activity, claim team wins as personal, or reach for a level the evidence does not support.

Method

1. Read the ladder for the target level first. Pull the leveling guidelines

and write down the specific expectations of the level you claim: scope of ownership, ambiguity handled, blast radius of impact. Build the packet to answer those exact bars, not a generic "did great work" case.

1. Show you already operate at the next level. Committees promote people who

have been performing at the target level, usually for two or more quarters, not people who might grow into it. Lead with examples that sit clearly in the next level's scope, and be honest when the evidence is current-level work done well.

1. Lead with impact, quantify it, tie it to the business. For each major

piece of work, state the outcome and its magnitude: revenue moved, latency cut, an incident class eliminated, teams unblocked. "Led the X migration" is activity; "led the X migration, cutting infra cost 22% and unblocking three teams" is impact.

1. Separate your contribution from the team's. Name what you personally drove

versus what the group delivered, in the artifacts and in your words. Reviewers discount packets that claim collective wins wholesale, and a peer on the committee will know. Precise credit reads as more senior than inflated credit.

1. Gather evidence that outlives the meeting. Link the design docs, launch

records, postmortems, and code behind each claim, plus peer and cross-functional feedback that speaks to scope and influence. A claim a reviewer can click into beats a paragraph they must take on trust.

1. Pass the skim test. Committees read many packets fast. Put the

level-defining impact in the first half page, use headings that map to the ladder's dimensions, and cut work that is real but off-thesis. A packet that buries its best evidence on page four gets scored on page one.

Checks

• Does the packet name the target level's stated bars and answer each with

specific evidence?

• Could a skeptical reviewer who never met you verify the top three impact

claims from the links alone?

• Is every headline win clearly yours, or would a teammate reading it dispute the

credit?

Boundaries

A packet documents impact that already happened: it cannot manufacture readiness, and padding a thin case spends a committee's trust you will want next cycle. Leveling ladders, packet formats, and committee norms differ sharply by company, so follow your organization's template and calibration rules. The committee's consistency work across candidates belongs to the perf-calibration skill.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Amey-Thakur
• Source: Amey-Thakur/AI-SKILLS
• License: MIT
• Homepage: https://amey-thakur.github.io/AI-SKILLS/

Install and usage instructions live in the source repository linked above.