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, deepread for evidence-first reading of supplied documents) 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. …
Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format
Category: Search — see all ranked ›
Work: Web research · Literature review
Who it is for: Researcher · Operations
Install (Claude Code):
cp -r research ~/.claude/skills/- Adoption: 9 repos
- Upkeep: 91.0
- Freshness: 81.0
- Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- Contributors: 30
- License: MIT
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
Its own instructions
Its SKILL.md says when to use it, shows worked examples, covers setup and states a limitation.
Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.
What changed recently
- 2026-08-21 the tashan score for research rose to 55.0, from 47.0 Upkeep, freshness or adoption moved enough to change how this measures.
- 2026-08-24 the tashan score for research fell to 49.0, from 55.0 Upkeep, freshness or adoption moved enough to change how this measures.
- 2026-08-26 the tashan score for research rose to 57.0, from 52.0 Upkeep, freshness or adoption moved enough to change how this measures.
You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.
You searched for one. Check the rest of your stack:
npx tashan-cli doctorReads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.
We recorded 4 changes to Research in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.
- The whole series behind any row, back to the first day we measured it
- The replacement, named — not just the news that something died
tashan doctorover your own config, on your own machine
Start a 7-day trial › Everything measured on this page stays free.
source ↗ · skill:alirezarezvani/research
Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.
Measured 2026-09-13 · scorer s5 · how · something wrong here?