# Research

> Use when asked to research a question, look up documentation or API facts, or gather background sources.

- Skill: `sreejithraman/research` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx get-skill add sreejithraman/research`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sreejithraman/research/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: sreejithraman (https://skillmd.com/u/sreejithraman)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/sreejithraman/research

---


# Research

Own a question and the evidence needed to answer it. Resolve the decision and
scope. Use [the General research row](../orchestration/references/models.md#model-defaults)
for investigation and synthesis.

## Note storage

Choose the note path before delegating. Use the host-provided session scratch
directory outside the repo when available; otherwise create a unique directory
under a writable OS temp directory. Save in the project only when explicitly
requested or when the task requires maintained documentation, honoring its
destination.

Record the note's absolute path in task handoffs and compaction summaries.
Reuse and update the same note as findings change; reread it after compaction
or resume. Keep it available while the session or dependent workers need it.

When independent reading helps another owner continue useful work, use
[orchestration](../orchestration/SKILL.md) to delegate a bounded question with
that path. When dispatched as the researcher, own the investigation and synthesis;
assign additional children only when the brief permits it.

## Source routing

Use Gemini for YouTube retrieval and Grok for X posts, with the configured
rows in [the model table](../orchestration/references/models.md#model-defaults).
Honor user overrides. Use orchestration for bounded source retrieval; when
dispatching a researcher, permit these source tasks in its brief. Source
retrievers work directly and return content or grounded extracts with canonical
URLs, relevant dates/timestamps, retrieval method, and access gaps. Inspect the
evidence before using it; a child summary alone does not prove retrieval.

## Findings and acceptance

1. Follow factual claims to primary sources: official documentation, source
   code, specifications, datasets, or first-party APIs. Record the revision/date
   and limits of the evidence; distinguish findings from inference.
2. Write one Markdown note with a direct answer, claim-level citations,
   unresolved gaps, and implications for the requested decision.
3. Inspect the note and sources before accepting it. Finish when the question
   is answered with the required evidence, or report exactly what remains
   unsupported and what would resolve it. Return the note path and conclusion.

