tech-search

Orchestrate six-phase web research and save findings under docs/research.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Andre-cardia/nivel-ia --skill tech-search-andre-cardia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-search
Source: https://github.com/Andre-cardia/nivel-ia/tree/main/.claude/skills/tech-search
Command: npx skills add https://github.com/Andre-cardia/nivel-ia --skill tech-search-andre-cardia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep technical research is time-consuming and fragmented. This Skill coordinates web search, content extraction, and structured synthesis to deliver comprehensive findings without external dependencies.

Core Features & Use Cases

  • Orchestrates multi-phase research: Query, Decompose, Parallel Search (Haiku), Evaluate, Synthesize, Document.
  • Zero external dependencies; saves results to docs/research/{YYYY-MM-DD}-{slug}/.
  • Suitable for R&D, tech benchmarking, competitive analysis, and knowledge capture with reproducible workflows.

Quick Start

Query a topic, for example 'React Server Components vs Client Components', to start the six-phase workflow.

Frequently Asked Questions about tech-search

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

FAQPage Schema
How do I automate deep technical research across multiple web sources?

You automate deep technical research by orchestrating a multi-phase pipeline that coordinates web search, content reading, and structured synthesis to deliver comprehensive findings without external dependencies.

What is the best way to structure software technology benchmarking and knowledge capture?

The best way to structure software technology benchmarking is using a reproducible workflow that enforces phased analysis, multi-source validation, and saves results under dated, slugged documentation directories.

How does multi-phase web search synthesis work for R&D documentation?

Multi-phase web search synthesis works by decomposing a query, executing parallel searches, evaluating sources, and synthesizing findings into structured documentation directories with zero external dependencies.

Can I use this automated research pipeline for competitive tech analysis without code generation?

Yes, you can use this automated research pipeline for competitive tech analysis because it enforces strict constraints that prevent code generation and focuses entirely on structured documentation synthesis.

Does the deep tech research workflow require external dependencies or API integrations?

No, the deep tech research workflow requires zero external dependencies and operates entirely self-contained, coordinating web search and content extraction internally to save results to local documentation paths.

When should I avoid using an automated web search and synthesis pipeline for research?

You should avoid using an automated web search and synthesis pipeline when your inquiry does not require phased analysis or multi-source validation, or when you need code generation rather than structured documentation outputs.