tech-search

Generate evidence-backed technical research reports via parallel web search and synthesis.

Updated May 6, 2025
One-click install
npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill tech-search-rodrigo-altissimo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-search
Source: https://github.com/rodrigo-altissimo/qiartificial/tree/main/.claude/skills/tech-search
Command: npx skills add https://github.com/rodrigo-altissimo/qiartificial --skill tech-search-rodrigo-altissimo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the time and effort required to research complex technical topics by automatically running a structured web research pipeline and producing a consolidated report.

Core Features & Use Cases

  • Self-contained deep research: Runs a multi-phase workflow that clarifies intent, decomposes the question, searches in parallel, evaluates coverage, and synthesizes results.
  • Evidence-focused extraction: Uses page extraction to capture key facts, code examples for reference only, expert quotes, and actionable insights from reliable sources.
  • Safe documentation output: Saves research outputs only under docs/research/{YYYY-MM-DD}-{slug}/ and avoids implementation or production artifacts.

Quick Start

Ask the skill to research a topic by sending: /tech-search "React Server Components vs Client Components".

Frequently Asked Questions about tech-search

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

FAQPage Schema
How do I generate evidence-backed technical research reports from a single question?

Evidence-backed technical research reports are generated by decomposing a user question into parallel web searches, extracting deep page content, evaluating coverage, and synthesizing findings into structured documentation. This multi-phase workflow clarifies intent and captures key facts from reliable sources.

What is query decomposition and how does it work for deep web research?

Query decomposition for deep web research breaks a complex technical question into multiple targeted sub-queries. These sub-queries run in parallel across web search and fetch tools to extract key facts, code examples, and expert quotes, ensuring comprehensive coverage evaluation before final evidence synthesis.

Can I run automated web search and page extraction without external API dependencies?

Automated web search and page extraction can optionally use MCP tools when available, but the workflow falls back to standard web search and fetch mechanisms without them. No explicit external dependencies are required to execute the multi-phase research pipeline and generate documentation.

How do I compile a technical comparison report using multiple web sources?

Compiling a technical comparison report uses parallel web search and deep page extraction to gather evidence from multiple sources. The workflow evaluates coverage gaps, extracts structured JSON data, and synthesizes expert recommendations into a consolidated report for comparison and general deep technical topics.

Where does the deep research workflow save its output files?

The deep research workflow saves output files strictly under the docs/research/{YYYY-MM-DD}-{slug}/ directory. This guardrail ensures research outputs are safely contained as documentation and avoids writing implementation or production artifacts to unintended locations.