| name | research |
| description | External research from primary sources with a cited answer. Use for official docs, specifications, APIs, or first-party source. Read-only by default. For repository structure or rationale, use how or why. |
| license | Complete terms in LICENSE |
Research
Use this skill for external fact-finding that needs primary-source evidence.
Boundaries
- Read-only answer by default. Do not create or edit files without an explicit
request for a repository artifact.
- Prefer official documentation, specifications, source code, and first-party
APIs. Trace each material claim to the source that owns it.
- Use
how for repository structure or runtime behavior. Use why for
motivation, historical decisions, regressions, or rationale.
- Keep source access and interpretation separate. Mark uncertainty and
conflicting primary sources.
- Do not require a provider-specific browser, agent, or citation format.
Workflow
- Define the question, scope, date boundary, and required output.
- Discover and inspect the smallest sufficient set of primary sources.
- Build a claim-to-source map while researching. Record access dates when
source state can change.
- Return a concise answer with citations, limitations, and unresolved facts.
- If the user explicitly requests a repository artifact, read
research-method.md, write one cited artifact
at the requested path, and verify its links and scope.
Do not silently turn research into implementation, planning, or an ADR.
