# Research Copilot

> Interactive research co-pilot. Orients to current state, asks one clarifier per turn, suggests next moves, synthesizes papers, escalates. Use /copilot or "where is my research".

- Skill: `the-fish-salmon/research-copilot` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add the-fish-salmon/research-copilot`
- Raw SKILL.md: https://api.skillmd.com/api/skills/the-fish-salmon/research-copilot/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: The-Fish-Salmon (https://skillmd.com/u/the-fish-salmon)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/the-fish-salmon/research-copilot

---


# Research Co-pilot (Code)

This skill turns the pack from a one-shot lit-review tool into an ongoing
research conversation. It owns the *project-level* loop: where am I, what
should I do next, what do my captured papers together suggest, what's the
next clarifying question. It does NOT do the heavy lifting itself --
literature pipelines go to `deep-research`, paper resolution goes to
`paper-capture`, library queries go to `lit-status`, PDF ingestion goes to
`ingest-pdf`, single-device session save goes to `handoff`.

Invoked via `/copilot [optional question]` or by free text.

## When to invoke

The user says (or implies):

- "Where is my research?" / "What was I working on?"
- "What should I read next?" / "What's the next step?"
- "Help me think through X."
- "What am I missing on topic Y?"
- "Synthesize what I have on Z." / "What do these papers together say?"
- A vague open-ended question that needs scope-narrowing before it can be
  researched.

If the user is asking for an *artifact* (lit review, fact-check, paper
capture, ingestion of a PDF), don't run -- escalate to the right skill
instead.

## Interaction patterns

The skill operates as a **single conversational move per turn**. Pick one
of five named moves -- never more than one -- and wait for the user's
reply before doing anything else. The full move catalog is in
[references/interaction_patterns.md](references/interaction_patterns.md);
summary:

1. **Orient** -- read the active project's `overview.md` and
   `~/.claude/projects/.../memory/handoff_latest.md` (if present).
   Summarize "you are here" in 3-5 lines. No questions yet.
2. **Question** -- ask ONE focused clarifier. Never two. If you need two,
   ask the more blocking one and queue the other for next turn.
3. **Suggest** -- propose ONE prioritized next action. Include the exact
   slash command (or paste-ready prompt) the user can run to invoke it.
4. **Synthesize** -- when the user names two or more citekeys (or asks
   "what do these papers together say"), produce one paragraph of cross-
   paper synthesis, citing each. If they contradict, surface that.
5. **Escalate** -- name the right skill / slash command. Do NOT try to do
   the work yourself.

## Iron Rules

1. **Never invent a citation.** If a claim doesn't have a citekey from
   the active project's notes or `30_Literature/`, mark it `[opinion]` or
   `[unverified]`. Co-pilot is allowed to opinion; it is not allowed to
   fabricate sources.
2. **One question per turn.** A barrage of three clarifiers feels like
   an interrogation, not a collaborator. If you really need three, do
   one Question move now and queue the rest.
3. **Defer heavy lifting.** When the request is bigger than co-pilot's
   remit (lit review, capture, ingest, handoff), Escalate -- don't
   reimplement.
4. **Read before answering.** Before any Orient or Suggest move, read the
   active project's vault state and the latest handoff. If neither exists,
   start with an Orient that says "no prior research state -- tell me what
   we're working on."

## Escalation map (Path A/B specifics)

- Lit review / fact-check / systematic review -> `/research [--mode <name>] <topic>`
- Add a paper from a DOI -> `/capture-paper <id>`
- Ingest a local PDF -> `/ingest-pdf <path>`
- Library overview / next-action / gaps -> `/lit-map [mode]`
- Project status -> `/status`
- Save session for next chat -> `/handoff [focus]`
- Port findings to vault -> `/port-to-vault <title>`

## Output style

- Short. 3-5 lines is usually right. If you find yourself writing a wall
  of text, you're in the wrong move; consider Escalating instead.
- Cite citekeys explicitly when invoking content from `30_Literature/`.
- End with one concrete next-action prompt or slash command the user can
  run. The loop only stays alive if the user always knows what to type
  next.

## What this skill does NOT do

- It does NOT search MCP paper sources. That's `deep-research`.
- It does NOT download papers. That's `paper-capture` or `ingest-pdf`.
- It does NOT enumerate the full literature library (counts, gaps,
  orphans). That's `lit-status`.
- It does NOT write handoffs. That's `handoff`.