technical-research

Evaluate technologies with defined criteria and documented findings.

5|2|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/ZacharyLuz/github-copilot-chat-exporter --skill technical-research-zacharyluz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-research
Source: https://github.com/ZacharyLuz/github-copilot-chat-exporter/tree/main/.claude/skills/research/technical-research
Command: npx skills add https://github.com/ZacharyLuz/github-copilot-chat-exporter --skill technical-research-zacharyluz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, repeatable approach to evaluating technologies, libraries, and approaches to support evidence-based decisions.

Core Features & Use Cases

  • Structured methodology for defining questions, establishing criteria, evaluating options, and documenting results.
  • Systematic candidate analysis with scoring, comparison, and hands-on verification (POCs).
  • Documentation & decision trails to inform architecture choices and team alignment.
  • Use cases: evaluating a new framework for a project, comparing cloud tools, or selecting between integration approaches.

Quick Start

Ask the AI to guide a tech evaluation by defining a research question, selecting criteria, scoring candidates, validating with a POC, and documenting the decision.

Frequently Asked Questions about technical-research

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

FAQPage Schema
How do I evaluate technologies to make evidence-based architecture decisions?

Systematic technical research provides a structured methodology for technology evaluation by defining research questions, selecting criteria, scoring candidates, and validating with proofs of concept. It produces actionable recommendations for architecture decisions.

What is the best way to compare libraries and cloud tools for a new project?

Comparing libraries and cloud tools requires a criteria-based evaluation methodology that scores candidates against predefined requirements and verifies results with proofs of concept. This ensures documented findings for team alignment.

How do I document architecture decisions and technology evaluations for team alignment?

Documenting architecture decisions involves capturing the research question, evaluation criteria, candidate scoring, and proof of concept verification results into a decision trail. This provides evidence-based documentation for team alignment.

When do I need a proof of concept during technology selection?

A proof of concept is needed during technology selection after establishing criteria and scoring candidates to perform hands-on verification. It validates documented findings before committing to architecture decisions or large-scale migrations.

Can I use this structured research methodology for small proofs of concept or only large migrations?

This structured research methodology applies to both small proofs of concept and large-scale migrations. It uses criteria-based evaluation and systematic candidate analysis to produce actionable recommendations regardless of project scale.