---
name: cited-research-note
description: "Answers a technical question as a short note where each claim carries its source and the date it was checked. Use when a technical question needs a short written answer in which every claim is sourced and dated. Do not use for opinion pieces, brainstorming, or answering from memory with no sources. Related topics: research, writing."
---

# Cited Research Note

Answers a technical question as a short note where each claim carries its source and the date it was checked.

## When to use

Use this skill when a technical question needs a short written answer in which every claim is sourced and dated. Do not use it for opinion pieces, brainstorming, or answering from memory with no sources.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Restate the question and write the short answer first with a confidence level.
3. Support each factual claim with a link or file reference and the date it was checked.
4. Prefer primary sources and say plainly when only secondary ones were found.
5. Show disagreements between sources and state which one is trusted and why.
6. List uncertainties with what would resolve them, then the dated source list.

## Inputs

- **Question** (longer free text)
- **Why it matters** (free text, e.g. "The decision it informs")
- **Sources allowed** (choose any: Official docs, Source code, Release notes, Issue trackers, Papers, Blog posts)
- **Version or date range** (free text, e.g. "Versions the answer must hold for")
- **Length** (choose one: Half a page, One page, Two pages)

## Output

A note with a one-line question, a short answer with confidence, cited evidence paragraphs, uncertainties and a dated sources list.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Cited Research Note

Research this question and write it up as a note with sources.

- Question: {{Question}}
- Why it matters: {{Why it matters}}
- Sources allowed: {{Sources allowed}}
- Version or date range: {{Version or date range}}
- Length: {{Length}}

Restate the question in one line and give the short answer first, with a confidence level of high, medium or low. Then give the supporting evidence in a few short paragraphs. Every factual claim needs a source link or a file and line reference, plus the date it was checked, because technical facts expire. Prefer primary sources over summaries, and say when you could only find secondary ones. Where sources disagree, show both and say which you trust and why. Test claims against the stated versions. Separate what the sources state from what you infer. End with open uncertainties and what would resolve them, then a sources list with dates.

## Pitfalls

- Citing a blog summary for a claim the official docs state differently.
- Giving an answer true for a newer version than the one in use.
- Mixing inference into sourced statements so the reader cannot tell them apart.