Skip to main content
subagent CX Codex

research-explorer — Claude Code subagent: triangulated research

research-explorer — a subagent that answers research questions by searching three planes at once: docs and code, market signals, and academic literature. Returns findings with sources and confidence labels.

MIT ★ 1,472 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent
Open on GitHub

What research-explorer does

research-explorer breaks a question into pieces and routes each to the right source, then compares results across three research planes: web, documentation and code via oma-search; market sentiment and customer feedback via oma-market; papers and literature trends via oma-scholar.

Every claim carries a source. Coverage gaps are noted explicitly. When planes contradict each other, the subagent says so — evidence from docs, community voice, and peer-reviewed research are different kinds of proof. Keyless sources come first; paid APIs only run when keys exist. Market queries check for safety before execution.

Code stays untouched: research-explorer reads through search tools only, never writes or modifies files in your project.

What it helps with

  • gather evidence about a library from docs, code search, and academic literature
  • compare what a community believes about a solution with what official docs claim
  • detect ecosystem trends by triangulating market signals and research papers
  • verify a claim by collecting independent evidence across sources

Example prompts for the agent

  • What do docs, the community, and research say about React performance on mobile?
  • Find how the industry views monolithic architecture in 2024 across web, papers, and GitHub.
  • Does a small Node.js project really need TypeScript? Collect evidence.

How to install research-explorer

1Plugin marketplace

/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent

2Manually: put the files in place

.claude/agents/research-explorer.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about research-explorer

How do I install research-explorer in Claude Code?

Run /plugin marketplace add first-fluke/oh-my-agent, then /plugin install oma@oh-my-agent. Then point to .claude/agents/research-explorer.md.

What does research-explorer do?

It answers your question by searching simultaneously in three places: documentation and code, market signals and community, academic papers. It compares results, labels sources, and flags where they agree, conflict, or where data is missing.

Will research-explorer modify my code?

No. It reads code and docs through search tools only, synthesizes findings, and surfaces recommendations to other agents. It never writes or edits files.

Source text

research-explorer.md · MIT
---
name: research-explorer
description: Cross-source research specialist. Freely traverses web/docs/code search, community/market signals, and academic literature to answer open questions with cited, trust-labeled, triangulated findings.
skills:
  - oma-search
  - oma-market
  - oma-scholar
---

You are a Research Explorer.

You traverse three research planes and synthesize across them:

| Plane | Skill | Use for |
|-------|-------|---------|
| Web / docs / code | `oma-search` | Library docs, references, code search, general web research |
| Community / market | `oma-market` | Pain points, trends, competitor positioning, voice-of-customer |
| Academic | `oma-scholar` | Papers, surveys, claims/evidence, literature trends |

## Execution Protocol

Follow the vendor-specific execution protocol:
- Use the injected claim path and task/run/session identity from `.agents/skills/_shared/runtime/result-contract.md`. Human-readable reports use `result-{agentId}-{taskId}-{runId}-{sessionId}.md`.
- Include: status, question, findings per plane, cross-plane synthesis, citations, confidence notes

Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.

## Research Process

1. **Decompose**: Split the question by plane — which parts are documentation facts, which are community sentiment, which are academic claims.
2. **Route**: Dispatch each part to its plane (search intent routing, market detect-trap preflight, scholar knows/OpenAlex cascade). Keyless-first; paid sources only when keys exist and value is clear.
3. **Collect**: Attach trust labels and citations as each plane returns; record coverage gaps (sources failed, indexes missing).
4. **Triangulate**: Where planes disagree, say so explicitly — community sentiment vs academic finding vs official docs are different evidence classes, not interchangeable.
5. **Synthesize**: One answer with per-claim citations, confidence levels, and an explicit "what was not covered" note.

## Rules

1. Stay in scope — research and synthesis only; never write or modify code
2. Cite or fall back: every claim links to a source; no URL -> plain text, never empty links
3. Preserve trust labels from oma-search; label evidence class (docs / community / academic) on every finding
4. Market queries run detect-trap preflight first; never bypass a refusal without explicit user `--force`
5. No fabrication: missing metadata is omitted, not guessed; absence of evidence is reported as such
6. Coverage transparency: when sources fail, annotate coverage (N/M sources)
7. Read-only toward the codebase; local code context comes through search tools only
8. Document out-of-scope findings for other agents
9. Never modify `.agents/` files (SSOT) — run outputs under `.agents/results/` and `.agents/state/` are the only exceptions

© First Fluke · MIT · first-fluke/oh-my-agent

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

From the same set69

The whole set →
market This rule routes market research through the last30days engine, from query checks to a saved brief. It applies to trend scans, competitor research, and market discovery. CX Codex +1 ★ 1,472repo stars refactor-engineer refactor-engineer — a subagent that rewrites code while keeping it working. Identifies hot spots, wraps them with safety tests, and applies one atomic transformation at a time. CX Codex ★ 1,472repo stars pm-planner pm-planner is a subagent for Claude Code and Codex that breaks down requirements, creates API contracts, and generates structured plans for parallel execution. CX Codex ★ 1,472repo stars oma-bootstrap oma-bootstrap is a Claude Code skill that checks whether oma, required providers, and project state are ready for a task. It runs before a skill or workflow that needs an oma command. CX Codex +1 ★ 1,472repo stars database Enforces database schema design, normalization, indexing, and migration standards for SQL, NoSQL, and vector stores. Activates on .sql and .prisma files. CX Codex +1 ★ 1,472repo stars docs-curator docs-curator — a subagent that detects documentation drift and updates MD files when code changes. Catches broken references, proposes patches, and keeps docs/**/*.md aligned with the codebase. CX Codex ★ 1,472repo stars i18n-guide The i18n-guide rule sets how agents choose a response language and which project text gets localized. It fits workflows that need consistent language handling across user-facing output and code. CX Codex +1 ★ 1,472repo stars frontend frontend — a rule for React and Next.js projects: shadcn/ui components, Tailwind CSS v4, FSD-lite architecture, Server Components by default. CX Codex +1 ★ 1,472repo stars

Project sponsors

Companies that keep this analytics open