mcpbeat Sign in

Comp Analysis Skill for Claude

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.

815 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
23273
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill comp-analysis

The instruction itself

10 sections, as written by the author

/comp-analysis

> If you see unfamiliar placeholders or need to check which tools are connected, see 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.

## 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

  • Location matters — Always specify location for benchmarking. SF vs. Austin vs. London are very different.
  • Total comp, not just base — Include equity, bonus, and benefits for a complete picture.
  • Keep data confidential — Comp data is sensitive. Results stay in your conversation.

Other skills for the same job

different authors, same section of the catalogue
Geo Database
by christophacham
×4

Access NCBI GEO for gene expression/genomics data. Search/download microarray and RNA-seq datasets (GSE, GSM, GPL), retrieve SOFT/Matrix files, for transcriptomics and expression analysis.

12k tokens
Pymc Bayesian Modeling
by christophacham
×4

Bayesian modeling with PyMC. Build hierarchical models, MCMC (NUTS), variational inference, LOO/WAIC comparison, posterior checks, for probabilistic programming and inference.

24k tokens scripts
Pymoo
by christophacham
×4

Multi-objective optimization framework. NSGA-II, NSGA-III, MOEA/D, Pareto fronts, constraint handling, benchmarks (ZDT, DTLZ), for engineering design and optimization problems.

19k tokens scripts
Statsmodels
by ComeOnOliver
×4

Statistical modeling toolkit. OLS, GLM, logistic, ARIMA, time series, hypothesis tests, diagnostics, AIC/BIC, for rigorous statistical inference and econometric analysis.

41k tokens
Add Uint Support
by pytorch
vendor ×3

Add unsigned integer (uint) type support to PyTorch operators by updating AT_DISPATCH macros. Use when adding support for uint16, uint32, uint64 types to operators, kernels, or when user mentions enabling unsigned types, barebones unsigned types, or uint support.

2k tokens
At Dispatch V2
by pytorch
vendor ×3

Convert PyTorch AT_DISPATCH macros to AT_DISPATCH_V2 format in ATen C++ code. Use when porting AT_DISPATCH_ALL_TYPES_AND*, AT_DISPATCH_FLOATING_TYPES*, or other dispatch macros to the new v2 API. For ATen kernel files, CUDA kernels, and native operator implementations.

2k tokens
Docstring
by pytorch
vendor ×3

Write docstrings for PyTorch functions and methods following PyTorch conventions. Use when writing or updating docstrings in PyTorch code.

3k tokens
Finetuning
by microsoft
vendor ×3

Fine-tune models on Azure AI Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).

47k tokens scripts

How to use it

Copy the folder

Take anthropics/comp-analysis from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.