CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

comparison-tool-design

Designing side-by-side comparison tools (plan-compare, product-compare, alternative-compare) that help users decide rather than just listing features. Axis selection, default-comparison logic, recommendation discipline. Honest about feature-list-dump (every feature in a row, no decision support), hidden-recommendation (biased comparison pretending to be neutral), and honest-comparison-with-guidance (genuine comparison plus opinionated recommendation) patterns. Triggers on comparison tool, plan compare, product compare, alternative compare, vs page, decision support tool. Also triggers when conversion through comparison stages is poor, when users are abandoning at the comparison step, or when a comparison tool is being scoped for the first time.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-structured playbook skill: clear overview, strong reference discipline (all links resolve, one level deep), and concrete design guidance with a usable framework. Its main weakness is redundancy — the core three-pattern framing is repeated three times across the body.

Suggestions

State the feature-list-dump / hidden-recommendation / honest-comparison-with-guidance taxonomy once (in its dedicated section) and have the opening and closing link to it instead of restating each pattern, trimming ~20-30 lines of repetition.

Fold the 'The voice is the senior product marketing director...' paragraph and the repeated 'The recommendation is visible, defended, and not the only path' phrasing into a single statement — the voice and principle are each conveyed more than once.

In the 12-consideration framework, pair measurement items (audience-fit, conversion-as-success-metric) with a concrete validation step or pointer to how/when to re-run them, turning the checklist into a verify-then-act sequence.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific guidance rather than general-knowledge padding, but it repeats itself: the three-pattern taxonomy is stated in the opening (lines 13-15), restated in the keystone section (67-73), and restated again in the closing (263-267), and phrases like 'The recommendation is visible, defended, and not the only path' appear multiple times. Sections could be tightened by stating each pattern once and pointing to the reference file.

3 / 5

Actionability

Concrete, specific instruction throughout for a design skill: the 8-12 axis rule, explicit strong/weak axis lists, named recommendation patterns with quoted templates ('For [audience], choose [option] because [reasons]'), a litmus test, eight failure-mode diagnoses, and a 12-item framework. Not a 5 because much of the operational detail is deferred to references and some guidance (e.g., 'conversion typically improves') is asserted rather than made verifiable.

4 / 5

Workflow Clarity

There is a clear sequence: the comparison-tool decision ('is the comparison tool the right tool for this decision'), then the keystone framing with a litmus-test checkpoint, then design sections, closing with a 12-consideration framework as a checklist. Not a 5 because validation of outcomes (e.g., how to measure per-segment conversion, when to revisit axis selection) is mentioned as considerations but not built into explicit verify-then-act checkpoints.

4 / 5

Progressive Disclosure

Each section is a concise overview ending with a well-signaled link to a real one-level-deep reference file, and a consolidated 'Reference files' list with one-line descriptions aids navigation; all 9 referenced files exist in references/ and the body appropriately summarizes rather than inlining their detail.

5 / 5

Total

16

/

20

Passed

Description

83%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: third-person, concrete about both capability and scope, with an explicit, natural trigger list plus situational triggers. Its only gaps are a few missing synonyms and the absence of in-description boundary markers against sibling skills.

DimensionReasoningScore

Specificity

Names the domain ('Designing side-by-side comparison tools (plan-compare, product-compare, alternative-compare)') and several concrete capabilities ('Axis selection, default-comparison logic, recommendation discipline'), plus a specific three-pattern taxonomy (feature-list-dump, hidden-recommendation, honest-comparison-with-guidance). Not a 5 because the actions are one governing verb ('Designing') plus named sub-domains rather than the multiple distinct verb-object actions of the top anchor.

4 / 5

Completeness

Both halves are explicit: 'what' is stated up front ('Designing side-by-side comparison tools... that help users decide rather than just listing features') and 'when' is stated concretely ('Triggers on comparison tool, plan compare... Also triggers when conversion through comparison stages is poor, when users are abandoning at the comparison step, or when a comparison tool is being scoped for the first time'). Matches the anchor for explicit what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Triggers on comparison tool, plan compare, product compare, alternative compare, vs page, decision support tool' gives good natural coverage, plus situational triggers ('conversion through comparison stages is poor', 'abandoning at the comparison step'). A few natural variations are missing (e.g., 'comparison chart', 'comparison table', 'versus page'), so it falls short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

A clear niche (side-by-side comparison tooling with vs-page and decision-support triggers) with distinct trigger vocabulary. Minor overlap risk with adjacent skills it does not disambiguate in the description itself (quiz/recommendation tools, calculators, pricing-page copy), keeping it just below the minimal-conflict anchor.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/comparison-tool-design/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.