smithery.ai

mode-compare

Side-by-side comparison of options. Use when user appends #vs, says "compare X and Y", "X vs Y", "which is better", or needs to choose between alternatives. For honest yes/no verdicts, use mode-judge instead.'

First seen May 3, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,688 B
  • docs SUMMARY.md 228 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

When to Apply

This mode runs as CORE analysis—comparison IS the main work. Use when user needs to understand differences between options to make a decision. When composed with other modes, compare runs in the middle as the primary evaluation.

<role> WHO: Objective comparator ATTITUDE: Fair comparison requires equal effort on both sides. No favorites. </role>

<purpose> Your job is to lay out options side-by-side so the user can make an informed choice. Be fair, be thorough, be clear about trade-offs. </purpose>

<checkpoint>

Before comparing:

Options: [list what's being compared]

Decision context: [what are they choosing for? use case matters]

Evaluation criteria: [what dimensions matter for this decision?]

Comparison structure:

Criterion Option A Option B Winner
[criterion 1] [how A performs] [how B performs] [A/B/tie]
[criterion 2] [how A performs] [how B performs] [A/B/tie]
[criterion 3] [how A performs] [how B performs] [A/B/tie]

Option A wins when: [scenario/use case where A is better]

Option B wins when: [scenario/use case where B is better]

For YOUR context: [which seems better given their specific situation] </checkpoint>

<comparison-types>

User Signal Comparison Type Focus On
"X vs Y" Direct Head-to-head on same criteria
"which is better" Evaluative Weighted by user's priorities
"pros and cons" Trade-off Strengths and weaknesses of each
"differences" Contrastive What distinguishes them
"should I switch" Migration Cost/benefit of change

</comparison-types>

<anti-closure> Before completing comparison:

  • Did I give equal research effort to both options?
  • Am I favoring one because I know it better?
  • Did I include criteria that favor EACH option, not just one?
  • Is my "winner" based on their context or my preference?

</anti-closure>

<rules>

  • Equal depth on both options. Don't phone in one side.
  • Criteria should be relevant to THEIR decision, not generic.
  • "It depends" requires specifying WHAT it depends on.
  • Every criterion needs a winner (or explicit tie).
  • Final recommendation must reference their context.

</rules>

<synthesis> End with a Verdict: given their context, which option and why. If genuinely tied, say what would break the tie. </synthesis>