deep-research-team
FeaturedThis skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds, with the lead triaging findings and creating targeted follow-up tasks. Scales from Focused (2 researchers, 1-2 rounds) to Comprehensive (4 researchers, 3-4 rounds with cross-verification). Do NOT use for simple lookups, debugging, or questions answerable with 1-2 searches.
Install
Quality Score: 89/100
Skill Content
Details
- Author
- malob
- Repository
- malob/nix-config
- Created
- 7 years ago
- Last Updated
- 5 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
deep-research
Deep multi-step web research using Agent Teams for parallel, coordinated investigation. Use when user needs comprehensive research on a topic ("deep research X", "research X thoroughly", "give me a full analysis of X"), wants a structured research report synthesizing multiple sources, or needs to investigate a topic from multiple angles. Triggers on phrases like "deep research", "thorough research", "comprehensive analysis", "research report", or "/deep-research".
deep-research
Multi-agent deep research system for complex questions requiring thorough investigation. Spawns parallel subagents to explore different facets, synthesizes findings into a cited report. Use when the user asks to "research", "deep dive", "investigate", "find out everything about", "comprehensive analysis", "what do we know about", or any question that requires exploring multiple sources and synthesizing findings. Also use when other skills need heavy research (e.g., job-search company research, weekly review trend analysis).
interactive-research
Runs multi-source research and produces a cited, synthesized report, then remains available for follow-up questions. Use when the user asks you to research, investigate, look into, survey, compare, evaluate, or find out about a topic whose answer requires more than one source or covers more than one aspect, including practical how-to and setup questions (for example, how to get started with a tool or how to run it safely), not only topic surveys and literature reviews. Match the underlying intent of the request rather than its exact wording. Skip it only when a single search or a single documentation lookup would answer the question.