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

79%

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 ./dist/codex/.agents/skills/comparison-tool-design/SKILL.md

The canonical home for this skill is comparison-tool-design in rampstackco/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

65%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 instruction skill with excellent progressive disclosure: the body is a genuine overview that defers detail to nine real, one-level-deep reference files. Weaknesses are the recap-heavy opening and closing, one keystone sentence repeated three times, and the absence of any validation or feedback checkpoint in the design/audit workflow.

Suggestions

Cut or compress the closing section and the opening paragraph, which restate the description and re-recap the keystone framing; state "the recommendation is visible, defended, and not the only path; users can override" once.

Add explicit validation checkpoints to the 12-consideration walkthrough, e.g. a step to test the litmus test on a draft tool, a peer review of axis honesty, and a re-check cadence after options or pricing change.

Include one worked example inline or in a reference file — a sample 8-12 axis set with a multi-segment recommendation for a real plan comparison — so the recommendation patterns are concrete rather than templated.

DimensionReasoningScore

Conciseness

The pattern content is domain knowledge Claude does not have and earns its tokens, but there is real tightening available: the opening ("A senior product marketing director's playbook...") restates the frontmatter description almost verbatim, the closing section recaps the entire skill, and "the recommendation is visible, defended, and not the only path; users can override" is repeated at least three times. Matches anchor 3 (mostly efficient, could be tightened) better than anchor 2, since no section explains concepts Claude already knows.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete: the 8-12 axis rule, the strong/weak axis category lists, the litmus test, symptom-to-diagnosis failure modes ("Tool gets traffic; conversion is unchanged. Likely feature-list-dump"), and the 12-consideration framework are all directly usable when designing or auditing. Missing a worked example (e.g., a sample axis set and recommendation for one real plan comparison), which keeps it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

The sections are ordered by design lifecycle and the 12-consideration framework provides a walkthrough, but there are no validation checkpoints or feedback loops — e.g., how to verify the comparison reads as honest, when to re-check axis relevance, or what to do when per-segment conversion does not improve. Anchor 3 (sequence present, checkpoints missing or implicit) fits; not 4 because most checkpoints are absent, not 2 because the sequence itself is coherent.

3 / 5

Progressive Disclosure

Each section is a compact overview that hands off with "Detail in references/..." to a real file (all nine referenced files exist in ./references/), plus a consolidated "Reference files" section with one-line descriptions; references are exactly one level deep. The unreferenced _claude-frontmatter-extras.yaml is a port artifact, not skill content, and does not meaningfully break navigation — a direct match for anchor 5.

5 / 5

Total

15

/

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: explicit what and when with concrete trigger phrases, natural keywords, and third-person voice. The inline definitions of the three patterns add length without adding trigger value, and a few common synonyms (comparison table, versus) are absent.

DimensionReasoningScore

Specificity

Names several specific design actions — "Axis selection, default-comparison logic, recommendation discipline" plus "Designing side-by-side comparison tools (plan-compare, product-compare, alternative-compare)" — but the actions are design-activity level rather than fully concrete operations, so it sits between anchor 4 (several specific actions, minor gaps) and anchor 5. It is above anchor 3 because more than 1-2 concrete actions are named with subgenre enumerations.

4 / 5

Completeness

Explicitly answers both: what ("Designing side-by-side comparison tools... Axis selection, default-comparison logic, recommendation discipline") and when ("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") with concrete trigger phrases — a direct match for anchor 5.

5 / 5

Trigger Term Quality

Good natural-term coverage: "comparison tool, plan compare, product compare, alternative compare, vs page, decision support tool" plus scenario phrases ("conversion through comparison stages is poor", "abandoning at the comparison step"). Falls short of anchor 5 because common variations like "comparison table", "versus page", or "compare plans" are missing; well above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche (side-by-side comparison/decision-support tooling) with distinct trigger phrases like "vs page" and "plan compare" that few other skills would claim; minor overlap risk remains with adjacent growth skills (pricing pages, recommendation tools) that the description does not explicitly disambiguate, so anchor 4 rather than 5.

4 / 5

Total

17

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rampstackco/claude-skills

Path

dist/codex/.agents/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.