research

skills/engineering/research/SKILL.md · 832 B · View on GitHub at 4ae2317

Summary written at import

Starts a background agent with a fresh context that investigates a question against primary sources and writes a cited Markdown file where the repo keeps such notes. Model-invoked when the user wants a topic researched or reading delegated; wayfinder uses it for research tickets.

Files in this skill

File	What it does	Flags
agents/openai.yaml	Codex metadata for the skill: display name “Research” and short description “Research from high-trust sources”.

Frontmatter

name: research
description: Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

Spin up a background agent to do the research, so you keep working while it reads. Start it with a fresh context window.

Its job:

1. Investigate the question against primary sources (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.
2. Write the findings to a single Markdown file, citing each claim’s source.
3. Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.

Original Markdown source

SKILL.md

---
name: research
description: Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
---

Spin up a **background agent** to do the research, so you keep working while it reads. Start it with a fresh context window.

Its job:

1. Investigate the question against **primary sources** (official docs, source code, specs, first-party APIs), not a secondary write-up of them. Follow every claim back to the source that owns it.
2. Write the findings to a single Markdown file, citing each claim's source.
3. Save it where the repo already keeps such notes; match the existing convention, and if there is none, put it somewhere sensible and say where.