From de75bcc4a46f1716ec3efe4c6c7220e333e924e7 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 11 Jul 2026 17:40:50 +0000 Subject: [PATCH] #689 - add research skill for delegated primary-source investigation Vendor Matt Pocock's research skill: a background agent investigates a question against primary sources and leaves a single cited markdown file where the repo keeps such notes. Needed as a wayfinder research ticket type and fills the dangling research delegate in the journal work. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01SdH2gxRtfjoqUWa5hG8SvF --- .claude/skills/research/SKILL.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 .claude/skills/research/SKILL.md diff --git a/.claude/skills/research/SKILL.md b/.claude/skills/research/SKILL.md new file mode 100644 index 00000000..0ba594a0 --- /dev/null +++ b/.claude/skills/research/SKILL.md @@ -0,0 +1,12 @@ +--- +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. + +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.