CtrlK
BlogDocsLog inGet started
Tessl Logo

salary-negotiation-prep

Research market rates, build negotiation strategy, and create counter-offer scripts

38

Quality

35%

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 ./skills/salary-negotiation-prep/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

27%

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

This skill reads more like a comprehensive career advice blog post than a focused Claude skill. It's extremely verbose, explains many concepts Claude already knows (equity definitions, negotiation psychology, career statistics), and packs everything into a single monolithic file. The email/call script templates and output format are the strongest elements, but the lack of actionable research methods (Claude can't browse salary websites) and the excessive general advice significantly weaken the skill's utility.

Suggestions

Cut the content by 50-60%: remove equity term definitions, negotiation psychology/statistics, do's/don'ts lists, and other general knowledge Claude already has. Focus on the templates, output format, and decision framework.

Make the research phase actionable for Claude: instead of listing websites Claude can't browse, instruct Claude to ask the user for their market research data or competing offers, then help analyze and structure it.

Split scenarios, scripts, and comparison templates into separate referenced files (e.g., SCENARIOS.md, TEMPLATES.md, COMPARISON.md) to improve progressive disclosure.

Add a validation/feedback loop: after generating the strategy, prompt the user to confirm key assumptions (walk-away point, priorities, market data accuracy) before finalizing the counter-offer script.

DimensionReasoningScore

Conciseness

Extremely verbose at ~300+ lines. Explains concepts Claude already knows (what RSUs are, what negotiation is, that '84% of employers expect candidates to negotiate'). The 'Negotiation Mindset' section, equity term definitions, and extensive do's/don'ts lists are padding that Claude doesn't need. Much of this is general career advice rather than actionable skill instructions.

1 / 3

Actionability

Provides concrete email/call script templates and a structured output format, which is good. However, much of the content is advisory rather than executable — there are no actual commands or code to run, and the 'research' steps just list website names without actionable methods Claude can use (Claude can't browse these sites). The templates are useful but the market research guidance is not actionable for Claude.

2 / 3

Workflow Clarity

There is a clear timeline template and general sequencing (receive offer → research → counter → discuss → resolve). However, the workflow lacks validation checkpoints — there's no step to verify market data quality, no feedback loop for iterating on the strategy based on user input, and the many scenarios are presented as independent blocks rather than a coherent decision tree.

2 / 3

Progressive Disclosure

Monolithic wall of text with no references to external files and no bundle structure. All content — scenarios, templates, comparison tables, checklists, timelines — is crammed into a single file. The scenarios, detailed scripts, and comparison templates could easily be split into separate referenced files for better organization.

1 / 3

Total

6

/

12

Passed

Description

42%

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

The description effectively lists three concrete actions, giving it strong specificity. However, it critically lacks a 'Use when...' clause, making it unclear when Claude should select this skill over others. Adding explicit trigger terms around salary, compensation, job offers, and related user phrases would significantly improve its utility for skill selection.

Suggestions

Add a 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about salary negotiation, job offer evaluation, compensation discussions, or preparing for a raise conversation.'

Include common user-facing trigger terms like 'salary', 'compensation', 'job offer', 'raise', 'pay negotiation', 'total comp' to improve matching against natural user language.

Clarify the domain context (e.g., 'salary/compensation negotiation') to distinguish from other negotiation-related skills like sales or contract negotiation.

DimensionReasoningScore

Specificity

Lists three specific concrete actions: 'Research market rates', 'build negotiation strategy', and 'create counter-offer scripts'. These are clear, actionable capabilities.

3 / 3

Completeness

Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and since the 'when' is entirely absent, this scores a 1.

1 / 3

Trigger Term Quality

Contains relevant keywords like 'market rates', 'negotiation strategy', and 'counter-offer scripts' that users might use, but misses common variations like 'salary negotiation', 'job offer', 'compensation', 'raise', or 'pay'.

2 / 3

Distinctiveness Conflict Risk

The combination of market rates, negotiation strategy, and counter-offer scripts points to a salary/job negotiation niche, but without explicit context it could overlap with general negotiation skills, sales negotiation, or business strategy skills.

2 / 3

Total

8

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
paramchoudhary/resumeskills
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.