CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

comp-analysis

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.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./human-resources/skills/comp-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well structured with a concrete output contract and clear input triage, but it spends tokens explaining compensation basics Claude already knows and never lays out an explicit step sequence with validation checkpoints. Tightening the framework section and adding an ordered workflow with data-verification steps would lift the two weakest dimensions.

Suggestions

Delete the 'Components of Total Compensation' section and the redundant intro sentence restating the description — Claude already knows what base salary, equity, and bonuses are (conciseness).

Replace the implicit flow with an explicit numbered workflow (e.g., 1. Confirm role/level/location, 2. Gather benchmark data, 3. Validate data freshness/coverage, 4. Produce the output template) so each input mode has a traceable sequence with checkpoints (workflow_clarity).

Name concrete fallback sources and methods for the no-connector path (e.g., specific public salary datasets, how to derive percentile bands from sparse data) instead of the vague "Use web research, public salary data" (actionability).

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes unnecessary explanation Claude already knows — "Base salary: Cash compensation", "Equity: RSUs, stock options", "Benefits: Health, retirement, perks" — and the opening line "Helps benchmark compensation against market data for hiring, retention, and equity planning" duplicates the frontmatter description. This matches the level-3 anchor (mostly efficient, some unnecessary explanation) rather than level 4, since a whole section could be cut without losing information.

3 / 5

Actionability

The output template with percentile and band-analysis tables is concrete and copy-paste ready, and the three input options are clearly specified with example phrasings. Minor gaps remain: the no-connector path says only "Use web research, public salary data" without naming sources or how to compute percentile bands, matching the level-4 anchor (mostly executable guidance, minor gaps) rather than fully-executable level 5.

4 / 5

Workflow Clarity

A sequence is implicitly present (gather input via Options A/B/C → check data sources → produce the templated output) but steps are never explicitly ordered and validation checkpoints are largely missing — only "Always note data freshness and source limitations" acts as a weak check. This matches the level-3 anchor (sequence present but checkpoints missing or implicit); it is above level 2 because the input handling and output contract are well defined.

3 / 5

Progressive Disclosure

The body is well organized into short, clearly headed sections (Usage, Framework, Output, Connectors, Tips) and needs no external bundle files; the only reference, CONNECTORS.md, is one level deep and clearly signaled. It sits at level 4 rather than 5 because the ~85-line body slightly exceeds the lean single-file ideal and the full output template is a candidate for trimming, leaving minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it states concrete capabilities in third person, provides explicit natural-language trigger phrases, and clearly separates what the skill does from when to use it. The only improvement would be adding a few common synonyms (salary, pay band, total comp) to the trigger vocabulary.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "benchmarking, band placement, and equity modeling", "find outliers and retention risks" — that comprehensively cover the skill's capabilities as shown in the body. This matches the anchor for multiple specific concrete actions with comprehensive coverage, not the level-4 anchor with minor gaps.

5 / 5

Completeness

It clearly answers both questions: what ("Analyze compensation — benchmarking, band placement, and equity modeling") and when ("Trigger with ... or when uploading comp data") with concrete trigger phrases. This directly matches the level-5 anchor; it is well above the level-4 anchor where 'when' is only implicit.

5 / 5

Trigger Term Quality

Quoted user phrasings like "what should we pay a [role]", "is this offer competitive", "model this equity grant", and "comp data" are exactly what users would naturally say. A few natural synonyms are missing (e.g., "salary", "pay bands", "total comp"), which keeps it at good-but-not-comprehensive keyword coverage rather than the level-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The compensation niche is clear and triggers like "is this offer competitive" and "model this equity grant" are domain-specific, so conflict risk is low. However, "uploading comp data to find outliers" has minor overlap risk with general data-analysis and HR skills, matching the level-4 anchor rather than minimal-conflict level 5.

4 / 5

Total

18

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository

anthropics/knowledge-work-plugins

Path

human-resources/skills/comp-analysis/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.