Research

---
name: research
description: Find out what is true about a library, service, or standard by reading whoever owns the facts, and write the answer down with a citation per claim. Use when the user asks to look something up, to check how an API or tool really behaves, or to hand off reading while other work continues.
---

Reading is slow, so it runs beside the main work: a subagent reads while this session carries on. A harness that cannot run one alongside reads inline; say so, since the session waits on it.

Rules:
- What counts as evidence: the party that owns a fact. That means the vendor's own documentation, the source code, the specification, or a response from the live endpoint. A blog post, a forum answer, or a summary is at most a lead toward the owner, never the citation.
- What comes back: one Markdown note, each claim followed by where it came from. It goes to the path the caller asked for. No path given: follow wherever the repo keeps similar notes. No such convention: choose a location and name it in the reply.