Research Orchestrator
costrict-plugins-repo/alirezarezvani-claude-code-skills-research-orchestrator
Roteador híbrido inteligente para pesquisa com fallback especializado
Ver no GitHubSkill que funciona como um roteador inteligente para requisições de pesquisa. Classifica determinísticamente qualquer pergunta de pesquisa e delega para um especialista (pulse, grants, litreview, syllabus, patent, dossier) ou executa seu próprio workflow de planejamento, decomposição, busca multi-fonte, síntese e citação.
Instalação
npx convez-ai costrict-plugins-repo/alirezarezvani-claude-code-skills-research-orchestrator1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Pesquisas gerais que precisam de síntese de múltiplas fontes
- Roteamento automático para domínios especializados (grants, literatura acadêmica, patents)
- Pesquisa de tendências em redes sociais e buzz de mercado
- Due diligence e pesquisa de concorrentes com relatórios estruturados
Veredito

Skill robusto que implementa roteamento determinístico sofisticado com transparência de decisão. Preenche lacuna importante entre pesquisa genérica e especializada, com fallback confiável para casos ambíguos. Dependência clara de WebSearch/WebFetch e especialistas irmãos limita uso standalone.
README
A tradução para o português deste README ainda está na fila.
research
The runtime orchestrator for the research domain. Hybrid router + fallback (Architecture C) — classifies any research request deterministically and either delegates to a specialist or runs its own plan-decompose-multi-source-search-synthesize-cite workflow.
Distinct from engineering/autoresearch-agent/
These two skills share the word "research" but serve completely different use cases:
| Skill | Use case |
|---|---|
research/research/ (this skill) | "Research X" — a query router. Routes to specialist (pulse, grants, litreview, etc.) or runs own fallback workflow. |
engineering/autoresearch-agent/ | Karpathy's "autoresearch" — autonomous file-optimization experiment loop. "Make this code faster", "improve my prompts." File-optimization, not query routing. |
No overlap. They coexist.
What this skill does
Every invocation produces one of three outcomes:
- Delegation — classified as specialist-domain, routes there. User sees specialist's output.
- Fallback execution — classified as general research. Runs own plan → search → synthesize workflow.
- Clarification request — classification ambiguous. Asks one forcing question to disambiguate, then routes.
The skill never silently runs its fallback when a specialist would have done better. Routing transparency is the key trustability property.
The 6 routing targets
| Specialist | Routes when question mentions | Domain |
|---|---|---|
pulse | reddit / hn / x / buzz / sentiment / trending / "what's people saying" / "pulse on" / "take the pulse" | Multi-source recency research |
grants | NIH / grant / R01 / K-award / RePORTER / NOSI / "grants for" | NIH grant-funding intelligence |
litreview | literature review / PICO / SPIDER / systematic review / "review papers on" | Academic literature orientation |
syllabus | syllabus attached / course outline / "reading list for my class" | Course supplementary reading |
patent | prior art / FTO / freedom to operate / patent / invention novelty | Patent prior-art + landscape |
dossier | "dossier on" / "due diligence" / "background check" / "competitor research" / "prep me for [meeting]" | Decision-grade entity research |
All 6 routing targets now exist in research/ (post-cleanup PR #667).
Source spec
megaprompts/13-research-megaprompt.md (PR #657).
Plugin layout
research/research/
├── .claude-plugin/plugin.json
├── README.md
├── agents/cs-research.md ← router persona, routing-transparency enforcer
├── commands/cs-research.md ← /cs:research <question>
└── skills/research/
├── SKILL.md
├── references/
│ ├── hybrid_router_architecture.md ← router-vs-run + routing transparency (7+ sources)
│ ├── deterministic_classification_canon.md ← keyword > LLM for routing (7+ sources)
│ └── fallback_workflow_canon.md ← plan-decompose-search-synthesize (7+ sources)
└── scripts/
├── classifier.py ← stdlib: deterministic signal matching → routing decision
├── routing_transparency_logger.py ← stdlib: JSON audit of routing decisions + overrides
└── fallback_decomposer.py ← stdlib: heuristic question → 3-5 sub-questions
Dependencies
WebSearch+WebFetch— Required for fallback workflow- Specialist skills — Required for delegation (research/pulse, grants, litreview, syllabus, patent, dossier)
- Node.js
docxlibrary — Required if user picks document output (Q2 = standalone) - Consensus MCP — Optional; used in fallback if academic sub-questions surface
License
MIT.