mmahalwy/comp-analysis
.agents/skills/comp-analysis/SKILL.md
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.
data-ai
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add mmahalwy/cooper comp-analysisInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 4, 2026, 2:16 PM5.7s1 file scanned
SKILL.md
- 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.
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.
Related Skills
mmahalwy/xlsx
development
VerifiedTrustedCommunity
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
SKILL.mdUpdated Apr 17, 2026
mmahalwy/view-pdf
content-media
VerifiedTrustedCommunity
Interactive PDF viewer. Use when the user wants to open, show, or view a PDF and collaborate on it visually — annotate, highlight, stamp, fill form fields, place signature/initials, or review markup together. Not for summarization or text extraction (use native Read instead).
SKILL.mdUpdated Apr 17, 2026
mmahalwy/ux-copy
documentation
VerifiedTrustedCommunity
Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.
SKILL.mdUpdated Apr 17, 2026
mmahalwy/triage-nda
development
VerifiedTrustedCommunity
Rapidly triage an incoming NDA and classify it as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). Use when a new NDA arrives from sales or business development, when screening for embedded non-solicits, non-competes, or missing carveouts, or when deciding whether an NDA can be signed under standard delegation.
SKILL.mdUpdated Apr 17, 2026