Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review cycle, or diagnose pay compression and equity issues.
npx skills add https://github.com/cbrock84/headcount --skill compensation-and-leveling
> Compensation touches employment law, pay transparency requirements, and equal pay obligations that
> vary by jurisdiction. Structural work here is fine; specific decisions about individuals should be
> reviewed by qualified counsel or an HR professional.
Pay structure without a leveling framework produces negotiated salaries, and negotiated salaries
produce inequity that correlates with who negotiates hardest.
Define each level by scope and impact, not tenure or task list:
problem nobody has identified?
Levels must be distinguishable in a sentence. If two adjacent levels cannot be told apart by
someone who does not know the people in them, they are one level.
For each level, benchmark against a market defined by the roles you actually compete with for
candidates — not the whole industry, and not aspirational peers.
case by case.
eventually costs more to fix than to prevent.
Compression — new hires paid near or above tenured staff — is the predictable result of moving
markets and static internal pay. It is corrosive because it is discovered, and it is always
discovered.
Run a pay equity analysis on a schedule: pay by level, controlling for level and location,
disaggregated by demographic. Where a gap exists, fix it directly rather than waiting for the next
cycle. Findings here need qualified review before action.
level. A promotion is recognition that someone is already operating there, not a bet that they
will.
counteroffer is right, it should reflect a correction you should have already made.
imports someone else's inequity.
Take cbrock84/compensation-and-leveling from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.