Skill Tracer
Skills › Skills For Real Engineers › research

research

skill · 12 lines · MIT · skills/engineering/research/SKILL.md

The facts

Its 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.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent picks this skill when someone asks for a topic to be investigated and the findings written down — gathering docs or API facts, or delegating the reading legwork to a background agent that works while the main conversation continues.

Things a person might say (the model's guesses)

  • “Can you research how Stripe's webhook signature verification actually works and write it up?”
  • “I need the real facts on Postgres advisory locks — dig into the docs and save notes in the repo.”
  • “Delegate the reading on this to a background agent and leave me a Markdown file with sources.”

A model's summary of when it is used.

A model's reading

What leads to it

Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.

A model's reading

Licence

MIT, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text
Other files in this skill (1) Close

The text

Open on GitHub
1---
2name: research
3description: 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.
4---
5
6Spin up a **background agent** to do the research, so you keep working while it reads. Start it with a fresh context window.
7
8Its job:
9
101. 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.
112. Write the findings to a single Markdown file, citing each claim's source.
123. 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.

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.
Raw lines 1 to 12

From mattpocock/skills at 4ae2317, 2026-10-31. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.