Salary Benchmarking
sickn33/agentic-awesome-skills
Salary benchmark register: role, department and grade against market and internal minimum, median and maximum.
Build a defensible salary range for a role — what it actually pays given the market, location, level, and your value — so you can ask, counter, or set pay with a real number.
MITAuto-check passed
Install Salary Benchmarking
$ npx skills add mohitagw15856/pm-claude-skills --skill salary-benchmarking -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills salary-benchmarking --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/salary-benchmarking .claude/skills/salary-benchmarking && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "salary-benchmarking" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/salary-benchmarking into .claude/skills/salary-benchmarking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salary-benchmarking", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/salary-benchmarkingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill salary-benchmarking -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills salary-benchmarking --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/salary-benchmarking .agents/skills/salary-benchmarking && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "salary-benchmarking" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/salary-benchmarking into .agents/skills/salary-benchmarking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salary-benchmarking", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill salary-benchmarking -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills salary-benchmarking --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/salary-benchmarking .cursor/skills/salary-benchmarking && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "salary-benchmarking" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/salary-benchmarking into .cursor/skills/salary-benchmarking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salary-benchmarking", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/salary-benchmarking--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill salary-benchmarking -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills salary-benchmarking --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/salary-benchmarking .gemini/skills/salary-benchmarking && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "salary-benchmarking" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/salary-benchmarking into .gemini/skills/salary-benchmarking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salary-benchmarking", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills salary-benchmarkingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill salary-benchmarking -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/salary-benchmarking .github/skills/salary-benchmarking && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "salary-benchmarking" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/salary-benchmarking into .github/skills/salary-benchmarking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salary-benchmarking", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill salary-benchmarking -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills salary-benchmarking --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/salary-benchmarking .opencode/skills/salary-benchmarking && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "salary-benchmarking" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/salary-benchmarking into .opencode/skills/salary-benchmarking/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "salary-benchmarking", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
salary-benchmarking- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 552 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build a defensible salary range for a role — what it actually pays given the market, location, level, and your value — so you can ask, counter, or set pay with a real number.
- Works in 6 steps: Use multiple sources. No single site is… → Adjust for the real drivers. Level,… → Place yourself honestly. Position within… → …
- Asked what should I be paid
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Triangulate,… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Salary Benchmarking is an agent skill from mohitagw15856/pm-claude-skills. Build a defensible salary range for a role — what it actually pays given the market, location, level, and your value — so you can ask, counter, or set pay with a real number. Use when asked what should I be paid, is my salary fair, research market pay for [role], or how much to ask for. Produces a structured way to research the range from multiple sources, the factors that move your number (level, location, industry, skills, company size), where you likely sit in the band, and how to frame the number — flagging…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked what should I be paid
- Is my salary fair
- Research market pay for [role]
- How much to ask for
Example prompts
- “/salary-benchmarking”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Use multiple sources. No single site is truth — combine salary surveys, aggregators, live job postings, peer/recruiter input, and…
- Adjust for the real drivers. Level, location/cost-of-living, industry, scarce skills, and company size/stage can each shift pay…
- Place yourself honestly. Position within the band based on your actual experience, skills, and results — not aspiration or imposter-driven…
- Build a defensible range. Produce a low/target/high with the reasoning, so the number survives scrutiny.
- Frame with evidence, not entitlement. Present the number tied to market data and your value; avoid a single cherry-picked figure or an…
- Caveat the data. It's noisy and can lag the market — triangulate and adjust rather than trusting one source or a stale number.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Salary Benchmarking loads about 1.2k tokens when it runs. Until then it costs about 163 tokens; SKILL.md has 552 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 552 words, ~1,182 tokens.
Download SKILL.mdSave it as
.claude/skills/salary-benchmarking/SKILL.md (or your agent's skills folder).- name
- salary-benchmarking
- description
- Build a defensible salary range for a role — what it actually pays given the market, location, level, and your value — so you can ask, counter, or set pay with a real number. Use when asked what should I be paid, is my salary fair, research market pay for [role], or how much to ask for. Produces a structured way to research the range from multiple sources, the factors that move your number (level, location, industry, skills, company size), where you likely sit in the band, and how to frame the number — flagging that pay data varies and should be triangulated, not taken from one source. Not the same as running the negotiation.
Salary Benchmarking
"Am I underpaid?" and "what should I ask for?" both need the same thing: a defensible number, not a guess or a single glassdoor figure. This builds that range by triangulating sources and adjusting for the factors that actually move pay — level, location, industry, skills, company size — then places you within the band and helps you frame it. (Making the ask itself is a separate negotiation skill.)
What This Skill Produces
- A research method — how to build a range from multiple sources (surveys, aggregators, postings, peers, recruiters) rather than one figure
- The adjusting factors — how level/seniority, location/cost-of-living, industry, in-demand skills, and company size/stage shift the number
- Your position in the band — a reasoned estimate of where you likely sit (and why), given your experience and value
- A defensible range — a low/target/high you can justify with the factors behind it
- Framing guidance — how to state the number and the evidence, without overclaiming
- A triangulation caveat — pay data is noisy and often stale; cross-check, and adjust for your specifics
Required Inputs
Ask for these if not provided:
- The role — title, level/seniority, and field
- Location — and whether the role is remote (which market applies)
- Your profile — years, key/in-demand skills, notable results
- Context — current pay, company size/industry, and the goal (raise, offer, new role)
- Sources seen — any numbers you already have
Framework: Triangulate, Adjust, Position
- Use multiple sources. No single site is truth — combine salary surveys, aggregators, live job postings, peer/recruiter input, and community data to form a range.
- Adjust for the real drivers. Level, location/cost-of-living, industry, scarce skills, and company size/stage can each shift pay substantially — apply them to the raw range.
- Place yourself honestly. Position within the band based on your actual experience, skills, and results — not aspiration or imposter-driven lowballing.
- Build a defensible range. Produce a low/target/high with the reasoning, so the number survives scrutiny.
- Frame with evidence, not entitlement. Present the number tied to market data and your value; avoid a single cherry-picked figure or an unbacked demand.
- Caveat the data. It's noisy and can lag the market — triangulate and adjust rather than trusting one source or a stale number.
Show full SKILL.md (194 more words)Show less
Output Format
Salary benchmark: [role/level] · [location/remote] · [industry]
Research from: [surveys · aggregators · live postings · peers · recruiters]. Adjust for: level [x] · location/COL [y] · industry · scarce skills · company size/stage. Your position in the band: [where + why — experience/skills/results]. Defensible range: low [ ] · target [ ] · high [ ] — justified by [factors]. How to frame it: [number + evidence, tied to value].
Pay data is noisy and can be stale — triangulate multiple sources and adjust for your specifics. (Running the negotiation itself is a separate step.)
Quality Checks
- Builds the range from multiple sources, not one
- Adjusts for level, location, industry, skills, and company size
- Positions the person honestly within the band
- Produces a defensible low/target/high with reasoning
- Frames the number with evidence, not entitlement
- Caveats data noise/staleness and triangulation
Anti-Patterns
- A single-source number treated as truth.
- Ignoring location/level/industry adjustments.
- Aspirational or imposter-driven self-positioning.
- A number with no justification.
- Trusting stale data without triangulating.
Example Trigger Phrases
- "What should someone in my role actually be paid?"
- "Am I underpaid? Help me research the market."
- "How much should I ask for in this new role?"
- "Build me a defensible salary range for a mid-level [role] in [city]."
- "Is this job offer's salary fair for my experience?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/salary-benchmarking of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Salary Benchmarking next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Salary Benchmarking this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Salary Benchmarkingsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| Benchmarkaffaan-m/ECC | 277k | 3 repos | ~654 | Automated safety check: Pass | MIT | |
| Benchmarkaffaan-m/ECC | 276k | — | ~412 | Automated safety check: Pass | MIT | |
| Benchmarkaffaan-m/ECC | 276k | — | ~330 | Automated safety check: Pass | MIT | |
| Benchmarkandroidx/androidx | 6.1k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Benchmark
affaan-m/ECC
Measure performance baselines and detect regressions across browser Core Web Vitals (LCP, INP, CLS, page weight), API endpoint latency percentiles, and build/test feedback times, with before/after…
Benchmark
affaan-m/ECC
このスキルを使用して、パフォーマンスベースラインを測定し、PR前後の回帰を検出し、スタック代替案を比較します. An agent skill from affaan-m/ECC.
Benchmark
affaan-m/ECC
使用此技能测量性能基线，检测PR前后的回归，并比较堆栈替代方案。
Benchmark
androidx/androidx
Benchmarking and improving the performance of Jetpack Compose.
Benchmark
samchon/typia
Defines typia benchmark fixture integrity, result reporting, and publication safeguards.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Salary Benchmarking
What does Salary Benchmarking do?
Build a defensible salary range for a role — what it actually pays given the market, location, level, and your value — so you can ask, counter, or set pay with a real number. Salary Benchmarking is an agent skill from mohitagw15856/pm-claude-skills. Build a defensible salary range for a role — what it actually pays given the market, location, level, and your value — so you can ask, counter, or set pay with a real number.
When should I use Salary Benchmarking?
Salary Benchmarking fits situations like: asked what should I be paid; is my salary fair; research market pay for [role]; how much to ask for.
How do I install Salary Benchmarking in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill salary-benchmarking -a claude-code`. Or copy the skill folder (skills/salary-benchmarking in mohitagw15856/pm-claude-skills) into .claude/skills/salary-benchmarking in your project. Claude Code loads it when a task matches its description.
How do I install Salary Benchmarking in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill salary-benchmarking -a codex`. Or copy the skill folder (skills/salary-benchmarking in mohitagw15856/pm-claude-skills) into .agents/skills/salary-benchmarking in your project. Codex loads it when a task matches its description.
Can I use Salary Benchmarking in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill salary-benchmarking -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/salary-benchmarking, .gemini/skills/salary-benchmarking, .github/skills/salary-benchmarking and .opencode/skills/salary-benchmarking in your project.
What does Salary Benchmarking need to run?
SKILL.md names no scripts, command-line tools or credentials: Salary Benchmarking is instructions for the agent only.
Does Salary Benchmarking access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Salary Benchmarking safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Salary Benchmarking use?
Salary Benchmarking is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Salary Benchmarking use?
About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Salary Benchmarking?
Skills that share tags, products or a category with Salary Benchmarking: Salary Benchmarking (sickn33/agentic-awesome-skills, 47k stars), Benchmark (affaan-m/ECC, 277k stars), Benchmark (affaan-m/ECC, 276k stars) and Benchmark (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Salary Benchmarking?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.