comp-analysis — Claude Code skill: compensation benchmarking
Benchmarks salaries against market data, places roles in bands, and models equity grants. Shows whether an offer is competitive and where retention risks sit.
npx skills add anthropics/knowledge-work-plugins --skill comp-analysis -a claude-codeWhat comp-analysis does
The skill analyzes compensation: base, equity, bonuses. Returns percentile bands (25th, 50th, 75th, 90th) by role, location, and company stage — startup, growth, public. Upload a CSV of team data and it will flag who sits above or below band, and where retention risks are.
Models stock options and refresh grants. With ~~compensation data connected, it pulls verified benchmarks; with ~~HRIS, it loads current comp data automatically. Without connectors, it uses web research and public salary sources.
Location drives the numbers: San Francisco, Austin, and London are different markets. Output is a table by role, level, and total comp, not just base.
What it helps with
- check if an offer is competitive for a candidate
- find employees below band and retention risks
- model the cost of a four-year refresh grant
- compare base and equity against market percentiles
Example prompts for the agent
- What should we pay a Senior Backend Engineer in Berlin?
- Is this offer competitive: $180k base, $50k equity, 20% bonus?
- Model a refresh grant of 10,000 shares over four years at $50 per share
How to install comp-analysis
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill comp-analysis -a claude-code2Manually: put the files in place
~/.claude/skills/comp-analysis/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/comp-analysis/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill comp-analysis -a codex2Manually: put the files in place
.agents/skills/comp-analysis/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill comp-analysis -a cursor2Manually: put the files in place
.cursor/skills/comp-analysis/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install anthropics/knowledge-work-plugins comp-analysis2Manually: put the files in place
.github/skills/comp-analysis/SKILL.md1Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill comp-analysis -a gemini-cli2Platform CLI
gemini skills install https://github.com/anthropics/knowledge-work-plugins --path human-resources/skills/comp-analysisManually: put the files in place
.devin/skills/comp-analysis/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add anthropics/knowledge-work-plugins --skill comp-analysis -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about comp-analysis
How to install comp-analysis in Claude Code?
Run npx skills add anthropics/knowledge-work-plugins --skill comp-analysis -a claude-code. The skill will appear at ~/.claude/skills/comp-analysis/SKILL.md.
What does comp-analysis do?
It benchmarks salaries against market data by role, level, and city, returns percentile bands for base and equity, models options, and flags employees outside their band.
Do I need connectors for it to work?
No, but with ~~compensation data or ~~HRIS connected, the skill will pull verified benchmarks and current team data. Without them, it uses public sources and web research.
Source text
SKILL.md · Apache-2.0
--- name: comp-analysis description: Analyze compensation — benchmarking, band placement, and equity modeling. Trigger with "what should we pay a [role]", "is this offer competitive", "model this equity grant", or when uploading comp data to find outliers and retention risks. argument-hint: "<role, level, or dataset>" --- # /comp-analysis > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Analyze compensation data for benchmarking, band placement, and planning. Helps benchmark compensation against market data for hiring, retention, and equity planning. ## Usage ``` /comp-analysis $ARGUMENTS ``` ## What I Need From You **Option A: Single role analysis** "What should we pay a Senior Software Engineer in SF?" **Option B: Upload comp data** Upload a CSV or paste your comp bands. I'll analyze placement, identify outliers, and compare to market. **Option C: Equity modeling** "Model a refresh grant of 10K shares over 4 years at a $50 stock price." ## Compensation Framework ### Components of Total Compensation - **Base salary**: Cash compensation - **Equity**: RSUs, stock options, or other equity - **Bonus**: Annual target bonus, signing bonus - **Benefits**: Health, retirement, perks (harder to quantify) ### Key Variables - **Role**: Function and specialization - **Level**: IC levels, management levels - **Location**: Geographic pay adjustments - **Company stage**: Startup vs. growth vs. public - **Industry**: Tech vs. finance vs. healthcare ### Data Sources - **With ~~compensation data**: Pull verified benchmarks - **Without**: Use web research, public salary data, and user-provided context - Always note data freshness and source limitations ## Output Provide percentile bands (25th, 50th, 75th, 90th) for base, equity, and total comp. Include location adjustments and company-stage context. ```markdown ## Compensation Analysis: [Role/Scope] ### Market Benchmarks | Percentile | Base | Equity | Total Comp | |------------|------|--------|------------| | 25th | $[X] | $[X] | $[X] | | 50th | $[X] | $[X] | $[X] | | 75th | $[X] | $[X] | $[X] | | 90th | $[X] | $[X] | $[X] | **Sources:** [Web research, compensation data tools, or user-provided data] ### Band Analysis (if data provided) | Employee | Current Base | Band Min | Band Mid | Band Max | Position | |----------|-------------|----------|----------|----------|----------| | [Name] | $[X] | $[X] | $[X] | $[X] | [Below/At/Above] | ### Recommendations - [Specific compensation recommendations] - [Equity considerations] - [Retention risks if applicable] ``` ## If Connectors Available If **~~compensation data** is connected: - Pull verified market benchmarks by role, level, and location - Compare your bands against real-time market data If **~~HRIS** is connected: - Pull current employee comp data for band analysis - Identify outliers and retention risks automatically ## Tips 1. **Location matters** — Always specify location for benchmarking. SF vs. Austin vs. London are very different. 2. **Total comp, not just base** — Include equity, bonus, and benefits for a complete picture. 3. **Keep data confidential** — Comp data is sensitive. Results stay in your conversation.
© anthropics · Apache-2.0 · anthropics/knowledge-work-plugins