tech-search

Decompose queries into parallel web searches and synthesize documentation-only reports.

Updated May 25, 2026
One-click install
npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill tech-search-felipemaines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-search
Source: https://github.com/FelipeMaines/ProjetoWeb/tree/main/.claude/skills/tech-search
Command: npx skills add https://github.com/FelipeMaines/ProjetoWeb --skill tech-search-felipemaines

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It reduces the time and uncertainty of deep technical research by running a structured web-based pipeline that gathers evidence, evaluates coverage, and produces a decision-ready report for experts.

Core Features & Use Cases

  • Evidence-driven research pipeline: Automatically clarifies intent, decomposes questions into targeted sub-queries, searches in parallel, and synthesizes findings into a structured report.
  • Deep page extraction: Extracts concrete technical facts, benchmarks, warnings, expert quotes, and preserved code snippets from the most relevant sources.
  • Guardrails for documentation-only output: Saves research strictly under docs/research/ while explicitly avoiding implementation or production artifacts.
  • Use case: When comparing two technical approaches (e.g., React Server Components vs Client Components), it produces a themed report plus recommendations grounded in high/medium/low credibility sources.

Quick Start

Ask: /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 automate web search and information synthesis for technical research?

Automated web search and information synthesis decomposes a query into parallel searches, extracts deep page content, and synthesizes findings into an evidence-backed report. This pipeline evaluates source credibility to produce decision-ready documentation.

What is the best way to compare technologies using deep research?

The best way to compare technologies using deep research involves decomposing the comparison question into targeted sub-queries, running parallel web searches, and synthesizing the extracted technical facts into a structured report with credibility-rated sources.

Can I generate a documentation-only report for technical best practices?

Yes, you can generate a documentation-only report for technical best practices by running a structured research pipeline that saves output strictly under docs/research/ while explicitly avoiding code implementation or production artifacts.

How does source evaluation work when comparing software frameworks?

Source evaluation during software framework comparison works by extracting concrete technical facts, benchmarks, and expert quotes from relevant pages, then rating the credibility of each source as high, medium, or low during the synthesis phase.

Does this research workflow support queries across web and software domains?

Yes, this research workflow supports queries across web and software domains by clarifying user intent, decomposing questions into targeted searches, and synthesizing up-to-date technical findings into a structured documentation report.

What are the limitations of using automated deep research for technical questions?

The primary limitation of automated deep research is its strict constraint to never implement code, meaning it only produces documentation reports under docs/research/ rather than generating functional software artifacts or production-ready solutions.