Research Ops

This is a workflow coordinator that routes research tasks to the right tools instead of doing the research itself. It decides whether you need quick facts from exa-search, deeper synthesis from deep-research, or a formal recommendation from market-research, then structures the output with clear labels for sourced facts versus inference versus recommendation. The useful bit is the evidence hygiene: it makes you separate what the user already gave you from what you found from what you're guessing. If you're building anything that mixes user context with fresh web lookups, or you keep running the same research question manually, this gives you a consistent shape to work in. Mostly valuable as a pattern rather than automation.

skills.sh installs: 3.5K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --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