CtrlK
BlogDocsLog inGet started
Tessl Logo

offer-comparison-analyzer

Compare multiple job offers side-by-side with total compensation analysis

37

Quality

33%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/offer-comparison-analyzer/SKILL.md

The canonical home for this skill is offer-comparison-analyzer in paramchoudhary/resumeskills

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 is a comprehensive but bloated reference document that reads more like a career advice blog post than a concise skill instruction. While it contains useful templates (compensation calculator, side-by-side comparison, weighted matrix), it's buried under excessive explanatory content that Claude already knows. The lack of any progressive disclosure structure and the absence of validation steps in the workflow significantly reduce its effectiveness as a skill file.

Suggestions

Cut the content by 60%+ by removing sections Claude already knows: 'The Comparison Challenge', 'Questions to Ask Yourself', 'Red Flags to Watch', and general career advice. Focus on the templates and calculation methodology.

Split into multiple files: keep SKILL.md as a concise overview with the core workflow and output format, then reference separate files like TEMPLATES.md (calculation templates), FACTORS.md (non-monetary scoring framework), and RED_FLAGS.md.

Add an explicit workflow sequence with validation: Step 1: Gather offer details (list required inputs), Step 2: Calculate total comp (verify all components accounted for), Step 3: Score non-monetary factors (confirm weights with user), Step 4: Present comparison and recommendation.

Remove filler phrases like 'The Problem:', 'The Solution:', and rhetorical questions. Replace with direct instructions like 'Always calculate Year 1 and Ongoing totals separately because signing bonuses are one-time.'

DimensionReasoningScore

Conciseness

Extremely verbose at ~300+ lines. Explains concepts Claude already knows well (what makes comparing offers hard, gut check questions, Monday morning test). Sections like 'The Comparison Challenge' and 'Questions to Ask Yourself' are padded filler that don't add actionable value. Red flags lists and self-reflection questions are general knowledge Claude doesn't need spelled out.

1 / 3

Actionability

Provides concrete templates and calculation examples which are useful, but these are static markdown templates rather than executable code. The weighted decision matrix walkthrough is a good example but is more of a manual process description than something Claude can directly execute. No actual computation scripts or tools are referenced.

2 / 3

Workflow Clarity

The weighted decision matrix has a clear 3-step process, and the output format provides a structured template. However, there are no validation checkpoints or feedback loops — no guidance on verifying calculations, confirming data completeness with the user, or handling missing information. The overall flow from input gathering to recommendation is implicit rather than explicitly sequenced.

2 / 3

Progressive Disclosure

Monolithic wall of text with everything inline. No references to external files, no separation of the detailed templates from the overview. The compensation calculator, comparison templates, non-monetary frameworks, red flags, and self-reflection questions could all be separate reference files, but instead everything is dumped into one massive document.

1 / 3

Total

6

/

12

Passed

Description

40%

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 identifies a clear niche (job offer comparison with compensation analysis) which makes it distinctive, but it lacks explicit trigger guidance ('Use when...') and could benefit from more specific capability listing and natural keyword variations. The 'what' is moderately described but the 'when' is entirely absent.

Suggestions

Add a 'Use when...' clause such as 'Use when the user wants to compare job offers, evaluate compensation packages, or decide between multiple offers including salary, equity, bonuses, and benefits.'

Expand specific capabilities, e.g., 'Compare multiple job offers side-by-side including base salary, equity/RSU valuation, signing bonuses, benefits, and total compensation over time.'

Include more natural trigger terms users would say, such as 'salary comparison', 'offer letter', 'TC', 'equity', 'RSU', 'benefits', and 'negotiate'.

DimensionReasoningScore

Specificity

Names the domain (job offers) and some actions (compare side-by-side, total compensation analysis), but doesn't list multiple specific concrete actions like salary breakdown, equity valuation, benefits comparison, or negotiation guidance.

2 / 3

Completeness

Describes what the skill does (compare job offers with compensation analysis) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and since the 'what' is also only moderate, this scores a 1.

1 / 3

Trigger Term Quality

Includes relevant terms like 'job offers', 'compensation', and 'compare', which users might naturally say. However, it's missing common variations like 'salary', 'equity', 'benefits', 'offer letter', 'negotiate', 'RSU', 'signing bonus', or 'TC'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'job offers', 'side-by-side comparison', and 'total compensation analysis' creates a clear, distinct niche that is unlikely to conflict with other skills. This is a well-defined use case.

3 / 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.