research
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-s
Profile →npx skills add alirezarezvani/claude-skills --skill research --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Research — Hybrid Router + Fallback **The runtime orchestrator for the research domain.** Architecture C: deterministic classification → specialist delegation OR own plan-decompose-search-synthesize-cite workflow. ## Portability Requires `WebSearch` + `WebFetch` for the fallback workflow; specialist skills (`pulse`, `grants`, `litreview`, `syllabus`, `patent`, `dossier`) must be present for delegation to work. Node.js with `docx` package required if Q2 = document mode. Works in Claude Code CLI natively. In Claude.ai with web tools + Code Execution, the workflow is supported. ## Distinct From `engineering/autoresearch-agent` These two skills share the word "research" but serve **completely different use cases**: - **`research/research/`** (this skill) — research-query router + fallback workflow ("Research X") - **`engineering/autoresearch-agent/`** — Karpathy's autonomous file-optimization experiment loop ("Make this code faster") No overlap. They coexist. ## Hybrid Architecture (C) Every invocation produces one of three outcomes: 1. **Delegation** — Classified as specialist-domain. Routes there. User sees the specialist's output. 2. **Fallback execution** — Classified as general
- Portability
- Distinct From engineering/autoresearch-agent
- Hybrid Architecture (C)
- Specialist Registry
- Agent Integrity Rules
- Phase 1: Grill-Me Intake (2–4 Questions)
- Q1 (always) — Research question
- Q2 (always) — Output preference
- Phase 2: Deterministic Classification
- Phase 3a: Specialist Delegation (≥2 signals OR one strong multi-word phrase)
- Phase 3b: Own Fallback Workflow
- Routing Transparency Protocol (Mandatory)
- Output Format
- Audit log block (fallback mode)
What does the research skill do?
Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-s
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill research --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.