Research Ops

This is a routing layer that decides which research tool to use and when. If someone asks you to look something up, compare options, or enrich a lead, it picks between exa-search for quick facts, deep-research for multi-source synthesis, market-research for recommendations, or lead-intelligence for people targeting. The useful part is the output format: it separates sourced facts from user context from inference from recommendation, so you know what's fresh evidence versus logical leap. It also flags when a research question is repetitive enough to deserve a monitor instead of running the same search manually forever. Think of it as research triage for ECC's evidence stack.

skills.sh installs: 5.5K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill research-ops --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

Skill Stack

Pull these ECC-native skills into the workflow when relevant:

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

When to Use

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 it factored into a fresh recommendation
the task may be recurring enough that it should become a monitor instead of a one-off lookup