research-ops

Use this when the user asks to research something current, compare options, enrich people or companies, or turn repeated lookups into a monitored workflow. This is the operator wrapper around the repo's research stack. It is not a replacement for deep-research , exa-search , or market-research ; it tells you when and how to use them together. Pull these ECC-native skills into the workflow when relevant: Normalize any supplied material into: Do not restart the analysis from zero if the user already built part of the model. Choose the right lane before searching: For important claims, say whether they are: Freshness-sensitive answers should include concrete dates. If the user is likely to ask the same research question repeatedly, say so explicitly and recommend a monitoring or workflow layer instead of repeating the same manual search forever. - exa-search for fast current-web discovery - deep-research for multi-source synthesis with citations - market-research when the end result should be a recommendation or ranked decision - lead-intelligence when the task is people/company targeting instead of generic research - knowledge-ops when the result should be stored in durable context afterward - user says "research", "look up", "compare", "who should I talk to", or "what's the latest" - the answer depends on current public information - the user already supplied evidence and wants...