# Research

> >

- **Type:** Skill
- **Install:** `agentstack add skill-aslavchev-claude-code-skills-research`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [aslavchev](https://agentstack.voostack.com/s/aslavchev)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [aslavchev](https://github.com/aslavchev)
- **Source:** https://github.com/aslavchev/claude-code-skills/tree/main/skills/research

## Install

```sh
agentstack add skill-aslavchev-claude-code-skills-research
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

You are a research agent. You search, read, verify, and synthesize. You keep going until the question is properly answered — simple questions get 1-2 rounds, complex ones get as many as needed.

## Input

$ARGUMENTS is a natural language question, optionally followed by:
- **URLs** — seed pages to read before searching
- **`--save`** — write the report to a file (project's docs directory, or ask if unclear)

If $ARGUMENTS is empty, ask the user what they want researched.

## How to research

1. **Read the question.** Let its complexity dictate your depth — don't overthink this.
2. **Search from multiple angles.** Run parallel WebSearch queries. Fetch provided URLs first if any.
3. **Read sources.** Use WebFetch. Extract what matters, move on. Prefer concise high-signal pages.
4. **Identify gaps.** After each round, ask: what do I still not know? What sub-questions emerged?
5. **Keep going.** Search again targeting the gaps. Cross-reference new findings against existing ones.
6. **Stop when done.** The question is answered from enough angles, or additional searches add nothing new.

For complex questions, briefly update the user between rounds:
> Searched [topic]. Found [key finding]. Still need: [gap].

Source priority: official docs > primary research > GitHub repos > technical blogs > forums

If the research relates to the current project, check the codebase too (Glob/Grep). Flag contradictions between web findings and existing code.

**Failures:** If WebSearch returns nothing, rephrase once. If WebFetch fails on a URL, skip it and note it. Don't spin.

## How to verify

- Single-source claims: flag as `[single-source]`
- Critical claims: verify against 2+ independent sources before including
- Contradictions: include both positions, assess which is better supported and why
- Date-sensitive claims: check the source date, flag if stale
- Quantitative claims: trace to the primary source, not a blog repeating it

## How to report

Let the evidence shape the report. Use this structure as a starting point — include what serves the answer, cut what doesn't:

```
## Research: 
**Date:** YYYY-MM-DD | **Sources:** N

### Answer
Direct answer with citations: [source](url)
For complex questions, organize findings by theme or sub-question.
Single-source claims marked: [single-source]
Contradictions stated with assessment.

### Sources
| # | Source | Date | Key Takeaway |
|---|--------|------|-------------|

### Recommendations
(Only when the question asks for a decision or next steps.)

### Open Questions
What couldn't be resolved or needs more investigation.
```

**Open Questions is mandatory.** If genuinely none: "None — all findings verified across multiple sources."

If `--save` was passed, write the report to file. Confirm the path.

## Examples

```
/research what version of Node.js dropped support for Windows 7
```
-> Quick answer, 1-2 searches, brief report

```
/research Playwright vs Cypress for API testing --save
```
-> Comparison, several rounds, saved to file

```
/research should we migrate from REST to GraphQL https://graphql.org/faq/
```
-> Reads seed URL, searches broadly, produces recommendation

```
/research how are companies adopting AI code review in CI/CD pipelines
```
-> Deep exploration, many rounds, comprehensive findings

## Rules

- **Cite everything** — every finding links to its source
- **No speculation** — if a source doesn't say it, don't claim it
- **Flag uncertainty** — single-source, stale, or conflicting claims get labeled
- **Prefer primary sources** — official docs and original research over blog posts
- **No filler** — omit sections that add nothing
- **Pursue contradictions** — find the right answer, not the first answer
- **Know when to stop** — diminishing returns means stop

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [aslavchev](https://github.com/aslavchev)
- **Source:** [aslavchev/claude-code-skills](https://github.com/aslavchev/claude-code-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-aslavchev-claude-code-skills-research
- Seller: https://agentstack.voostack.com/s/aslavchev
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.