Research Ops
Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Research Ops when an AI agent needs a reusable SKILL.md workflow for this job: Evidence-first current-state research workflow for ECC. Use when the user wants fresh facts, comparisons, enrichment, or a recommendation built from current public evidence and any supplied local context.
When not to use it
Skip Research Ops when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/research-ops # Save SKILL.md to ~/.claude/skills/research-ops/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/research-ops/SKILL.md. For a shared project, commit the folder at .claude/skills/research-ops/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Research Ops skill for this task: user says "research", "look up", "compare", "who should I talk to", or "what's the latest". Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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
## Guardrails
- do not answer current questions from stale memory when fresh search is cheap - separate: - sourced fact - user-provided evidence - inference - recommendation - do not spin up a heavyweight research pass if the answer is already in local code or docs
## Workflow
### 1. Start from what the user already gave you
Normalize any supplied material into:
- already-evidenced facts - needs verification - open questions
Do not restart the analysis from zero if the user already built part of the model.
### 2. Classify the ask
Choose the right lane before searching:
- quick factual answer - comparison or decision memo - lead/enrichment pass - recurring monitoring candidate
### 3. Take the lightest useful evidence path first
- use `exa-search` for fast discovery - escalate to `deep-research` when synthesis or multiple sources matter - use `market-research` when the outcome should end in a recommendation - hand off to `lead-intelligence` when the real ask is target ranking or warm-path discovery
### 4. Report with explicit evidence boundaries
For important claims, say whether they are:
- sourced facts - user-supplied context - inference - recommendation
Freshness-sensitive answers should include concrete dates.
### 5. Decide whether the task should stay manual
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.
## Output Format
```text QUESTION TYPE - factual / comparison / enrichment / monitoring
EVIDENCE - sourced facts - user-provided context
INFERENCE - what follows from the evidence
RECOMMENDATION - answer or next move - whether this should become a monitor ```
## Pitfalls
- do not mix inference into sourced facts without labeling it - do not ignore user-provided evidence - do not use a heavy research lane for a question local repo context can answer - do not give freshness-sensitive answers without dates
## Verification
- important claims are labeled by evidence type - freshness-sensitive outputs include dates - the final recommendation matches the actual research mode used
Intended uses
- 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
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.