research

Compare competing technical options and produce a decision matrix with a recommendation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SalesTeamToolbox/frood --skill research-salesteamtoolbox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/SalesTeamToolbox/frood/tree/main/skills/builtins/research
Command: npx skills add https://github.com/SalesTeamToolbox/frood --skill research-salesteamtoolbox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Research skill helps you turn an ambiguous technical question into a structured comparison with an evidence-based recommendation, reducing decision fatigue and analysis paralysis.

Core Features & Use Cases

  • Structured research methodology: Define the question, gather diverse sources, compare across clear criteria, and produce a decision-ready output.
  • Evidence-aware comparison: Builds a comparison matrix and evaluates authority, recency, relevance, evidence quality, and bias.
  • Actionable deliverables: Outputs question, context, options considered, comparison, recommendation, trade-offs/risks, next steps, and sources.

Quick Start

Use the research skill to compare three candidate technologies for your next feature and return a recommendation with a comparison table and cited sources.

Frequently Asked Questions about research

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

FAQPage Schema
How do I compare technology options using a decision matrix?

To compare technology options, this skill builds a decision matrix evaluating performance, cost, and maintainability. It separates facts from opinions, assesses source authority and recency, and outputs an evidence-based recommendation with trade-offs and next steps.

What is the best way to structure technical research for architecture trade-off analysis?

Structured technical research converts ambiguous architecture questions into evidence-based evaluations. It defines the question, gathers diverse sources, compares options across explicit criteria, and produces a decision-ready output with trade-offs, risks, and cited links.

Can I use this for technology selection with specific performance and cost criteria?

Yes, technology selection applies explicit criteria such as performance, cost, and maintainability. The evaluation builds a comparison matrix to ensure coverage, evaluates source quality, and returns a clear recommendation with identified risks.

How do I evaluate source authority and recency during evidence-based evaluations?

Evidence-based evaluations assess source authority, recency, relevance, and bias. The methodology separates verified facts from opinions, ensuring the final recommendation and trade-off analysis rely on high-quality, recent technical sources.

What should a technical recommendation include to avoid analysis paralysis?

A technical recommendation should include the context, options considered, a comparison matrix, trade-offs, risks, next steps, and sources. This structured deliverable reduces decision fatigue by converting competing options into actionable advice.

When should I not use structured research for comparing options?

Structured research is less suited for scenarios lacking explicit decision criteria or requiring immediate tactical choices. If options cannot be measured against performance, cost, or maintainability, the decision matrix output will lack actionable trade-offs.