research

Research technical solutions and architectures to produce reproducible evidence-based reports.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/lukebaze/forex-rebate-bot --skill research-lukebaze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/lukebaze/forex-rebate-bot/tree/main/.opencode/skill/research
Command: npx skills add https://github.com/lukebaze/forex-rebate-bot --skill research-lukebaze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of researching technical solutions, architectures, and requirements to support informed, evidence-based decisions across projects.

Core Features & Use Cases

  • Systematic Information Gathering: Multi-source collection of official docs, repositories, and expert analyses.
  • Evaluation & Comparison: Structured criteria to compare options for scalability, security, and maintainability.
  • Deliverables: Reproducible research reports including executive summaries, methodology, and recommendations.
  • Use Case: Deploy a new microservice and compare tech stacks, selecting the best-fit solution with documented trade-offs.

Quick Start

Initiate a focused, multi-source tech research session to produce a reproducible evidence-based report.

Frequently Asked Questions about research

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

FAQPage Schema
How do I systematically evaluate and compare tech stacks for a new microservice architecture?

Tech stack evaluation uses multi-source information gathering and structured criteria to compare options for scalability, security, and maintainability. It generates a reproducible research report with documented trade-offs to support your microservice architecture decision.

What is included in a reproducible technical research report for architecture evaluation?

A reproducible technical research report includes an executive summary, methodology, evaluation criteria, risk/benefit analysis, and mitigation recommendations. It synthesizes official documentation, repositories, and expert analyses to support evidence-based architecture decisions.

How do I gather requirements and define evaluation criteria for selecting technical solutions?

Requirements gathering defines scope and methodologies to collect multi-source technical information including official docs and expert analyses. Evaluation criteria structure comparisons across scalability, security, and maintainability dimensions to identify the best-fit technical solution.

What's the best way to compare technical solutions with documented risk and benefit analysis?

Comparing technical solutions requires structured evaluation criteria applied to multi-source data, emphasizing recency and source reliability. The methodology produces a risk/benefit analysis with mitigation recommendations, ensuring trade-offs are documented for informed decision-making.

Can I use systematic research methodologies for both technology selection and requirements gathering?

Systematic research methodologies apply to both technology selection and requirements gathering across systems. The approach defines scope, collects multi-source information, evaluates options against structured criteria, and delivers reproducible reports with risk analysis for either use case.

When do I need a structured evaluation process for architecture decisions instead of informal research?

Structured evaluation is needed when architecture decisions require evidence-based documentation, reproducible methodology, and risk/benefit analysis. Informal research lacks the systematic criteria comparison and mitigation recommendations necessary for scalable, secure, and maintainable system selection.