competitive-analyst

Compare tools and products with evidence-backed evaluation criteria and tradeoffs.

22|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill competitive-analyst-jshsakura
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competitive-analyst
Source: https://github.com/jshsakura/awesome-opencode-skills/tree/main/skills/competitive-analyst
Command: npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill competitive-analyst-jshsakura

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grounded competitive analysis to compare tools, products, libraries, or implementations to support decision-making across teams.

Core Features & Use Cases

  • Structured evaluation criteria: defines explicit decision factors to compare options.
  • Evidence-backed comparisons: aggregates signals from docs, benchmarks, and real-world usage.
  • Decision-ready outputs: provides a recommended option with tradeoffs and uncertainties for a given context.

Quick Start

Compare two candidate tools for a project and output a clear, justified recommendation.

Frequently Asked Questions about competitive-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is competitive analysis for tool selection?

Competitive analysis for tool selection compares candidate tools, products, or libraries using structured evaluation criteria and evidence-backed signals. It defines explicit decision factors to evaluate tradeoffs, costs, and vendor ecosystems, yielding a decision-ready recommendation.

How do I compare two tools or libraries for a project?

To compare two tools, define explicit evaluation criteria and aggregate evidence from documentation, benchmarks, and real-world usage. This structured comparison evaluates tradeoffs, costs, and roadmaps to output a clear, justified recommendation for your specific context.

Can I use this for vendor evaluation across product and engineering teams?

Yes, you can use this for vendor evaluation across product, engineering, and operations teams. The analysis applies to decision contexts where tradeoffs, costs, roadmaps, and vendor ecosystems influence tool selection, ensuring a decision-ready output with defined uncertainties.

What is the best way to structure selection criteria for a product comparison?

The best way to structure selection criteria is to define explicit decision factors tailored to your context. Evidence-backed comparisons then aggregate signals from docs and benchmarks against these criteria, producing a final recommendation with explicit tradeoffs and uncertainty.

Does the comparison include risk assessment and uncertainty?

Yes, the comparison includes risk assessment by providing a final recommendation with explicit tradeoffs and uncertainty. It evaluates vendor ecosystems and roadmaps to ensure decision-ready outputs account for potential risks and context-specific limitations.