promotion-packet

Builds promotion cases through year-round evidence collection and rubric-mapped impact narratives.

1|Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Nandansai08/skillz --skill promotion-packet-nandansai08
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: promotion-packet
Source: https://github.com/Nandansai08/skillz/tree/main/skills/career-productivity/promotion-packet
Command: npx skills add https://github.com/Nandansai08/skillz --skill promotion-packet-nandansai08

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Most promotion packets fail because evidence is reconstructed from memory at packet time, claims are framed as activities instead of impact, and scope calibration is either inflated or erased by modesty. This Skill structures the entire promotion case — from the year-round evidence file to the self-review narrative — so the packet argues against the next level's actual rubric. ## Core Features & Use Cases - Year-Round Evidence File: A running doc capturing dated, linked, rubric-tagged wins as they happen, fed by a weekly review habit. - Early Gap Analysis: Maps your record against the next level's rubric dimensions (strong / thin / gap) with your manager two quarters out, so gaps are still fillable. - Impact-Framed Narrative: Converts activities into outcome + role + evidence-link claims, calibrated precisely in both directions, woven into an arc committees remember. - Use Case: A senior engineer targeting staff engineer runs a gap analysis six months early, discovers cross-team influence is thin, volunteers to lead a cross-team API effort, and writes the packet in two evenings from the evidence file. ## Quick Start Help me build my promotion packet for the next level by setting up an evidence file and gap-analyzing my record against the rubric.

Frequently Asked Questions about promotion-packet

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a promotion packet or self-review?▼

Start with a gap analysis against the next level's rubric, then frame every claim as outcome plus your specific role plus an evidence link. Weave 3-4 flagship examples into a narrative arc showing you already operate at next-level scope, and address your weakest dimension head-on with counter-evidence.

How do I document my impact for a performance review?▼

Keep a running evidence file year-round where wins land when they happen: date, what happened, impact with numbers, a link, and the rubric dimension it feeds. Reconstructing a year at packet time loses the metrics and the quieter half of your work.

When should I start preparing for a promotion cycle?▼

Start at least two quarters before the cycle. Gaps found early are fillable through targeted work like leading a cross-team effort, while gaps found at packet time become next cycle's problem. Manager alignment on the gap analysis is essential.

Should I say 'I' or 'we' in a promotion self-review?▼

Use first person with your precise role. Systematic 'we' makes committees conclude the team did everything, while inflating 'participated' to 'led' gets caught by cross-checks and discounts your honest claims. Accuracy in both directions is the standard.

What should I do if my promotion is denied?▼

Convert the no into a written contract: which specific dimension fell short, what evidence would change the answer, and by when, with your manager co-owning the plan. A vague no repeated twice is itself information about whether to pursue the promotion elsewhere.