---
name: Research
slug: research-2
category: Automation
description: Investigates a question using primary sources such as official docs, source code, and specs, then writes the findings to a Markdown file in the repo. Use when you need facts gathered or reading work delegated to a background agent.
github: "https://github.com/tt-a1i/matt-skills-with-to-goal/tree/main/skills/research"
language: Shell
stars: 14
forks: 3
install: "git clone https://github.com/tt-a1i/matt-skills-with-to-goal"
added: 2026-07-16T13:43:25.393Z
last_synced: 2026-07-18T04:41:58.192Z
canonical_url: "https://dirskills.com/skills/research-2"
---

# Research

Investigates a question using primary sources such as official docs, source code, and specs, then writes the findings to a Markdown file in the repo. Use when you need facts gathered or reading work delegated to a background agent.

**Install:** `git clone https://github.com/tt-a1i/matt-skills-with-to-goal`

## README

Spin up a **background agent** to do the research, so you keep working while it reads.

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.
