salary-negotiation-prep

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

Quality

35%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/salary-negotiation-prep/SKILL.md

Quality

Discovery

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 lists specific concrete actions well but lacks critical context about when to use the skill and what domain it applies to (salary negotiation, contract negotiation, etc.). The absence of a 'Use when...' clause and domain-specific trigger terms significantly weakens its utility for skill selection among many options.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about salary negotiation, job offers, compensation packages, or preparing for a raise discussion.'

Include common natural language trigger terms users would say, such as 'salary', 'compensation', 'job offer', 'raise', 'pay negotiation', or 'benefits'.

Clarify the domain context (e.g., salary/job negotiation vs. contract or business negotiation) to reduce conflict risk with other potentially similar skills.

Dimension	Reasoning	Score
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', '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 toward salary/job negotiation, which is somewhat distinctive, but without explicit context (salary? contract? real estate?) it could overlap with other negotiation-related skills.	2 / 3
	Total	8 / 12 Passed

Implementation

27%

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

This skill is a comprehensive but excessively verbose salary negotiation guide that reads more like a blog post or career advice article than a concise skill instruction for Claude. Its strengths are the concrete email/call script templates and the structured output format, but it's severely undermined by extensive padding with general knowledge Claude already possesses (equity definitions, negotiation statistics, basic do's/don'ts). The content would benefit enormously from being cut by 60-70% and split across multiple files.

Suggestions

Remove all explanatory content Claude already knows: equity term definitions, negotiation statistics (84% of employers expect it), the 'Negotiation Mindset' section, and the Do's/Don'ts list. Focus only on the actionable templates and output format.

Split content into multiple files: keep SKILL.md as a concise overview with the output format template, and move scenario scripts to SCENARIOS.md, the comparison framework to COMPARISON.md, and research guidance to RESEARCH.md.

Add validation checkpoints to the workflow: e.g., 'Confirm with user: What are your top 3 priorities?' before building the counter-offer, and 'Verify: Do you have data from at least 3 sources?' before proceeding to strategy.

Trim the research phase to just the output template and source list — Claude doesn't need to be told what factors increase someone's worth or how to calculate total compensation.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~300+ lines. Explains concepts Claude already knows (what RSUs are, that negotiation is expected, career statistics about negotiation). Includes extensive general advice (Do's/Don'ts lists, mindset sections, equity term definitions) that Claude would already understand. Much of this is generic career advice padding rather than actionable skill instructions.	1 / 3
Actionability	Provides concrete email and call script templates which are useful, and the total comp calculation example is helpful. However, the 'research' steps are vague (just listing websites to check rather than providing executable guidance), and much of the content is general advice rather than specific, executable instructions. No actual code or tool usage is involved since this is an instruction-only skill, but the templates are copy-paste ready.	2 / 3
Workflow Clarity	There is a clear timeline template and general sequencing (receive offer → research → counter → discuss → resolve), but the workflow lacks validation checkpoints. For example, there's no explicit step to verify market data quality, no checkpoint to confirm the user's priorities before building the counter-offer, and no feedback loop for iterating on the strategy based on the employer's response patterns.	2 / 3
Progressive Disclosure	Monolithic wall of text with no references to external files. Everything is inline in a single massive document — the scenarios, templates, comparison tables, checklists, and research guidance could all be split into separate referenced files. No bundle files exist to support progressive disclosure.	1 / 3
	Total	6 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: paramchoudhary/resumeskills
Commit: 24c6edc

Reviewed: 12 days ago

Table of Contents

Discovery Implementation Validation

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.