research-synthesizer — Claude Code skill: what it does, how to install
research-synthesizer compares your Littlebird context with current sources to show what has changed on a topic. Use it to catch up or check whether an earlier view still holds.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install littlebird-toolkit@wasp-nestWhat research-synthesizer does
The skill builds a concise research brief from two sides: material you encountered or comments you made in Littlebird, and current external sources. It separates familiar context from new developments, so the main result is the change rather than a repeat of everything you might have read.
Before searching, it asks you to define the question, boundaries, useful terms, and what you already believe. The internal search requires Littlebird MCP on a Power or Pro plan; without search_user_context, the run stops. External comparison depends on web search and page-fetch tools available in the session. Without those tools, the brief covers internal context only, so it cannot establish the full change between both sides.
What it helps with
- check whether an earlier view still matches current information
- separate new findings from material already encountered
- combine personal context with current sources in a short brief
- track new developments on an ongoing topic
Example prompts for the agent
- Compare what I already know about this topic with current sources and highlight what changed.
- Check whether my current view of this topic is still accurate.
- Track this topic and report what has appeared since the previous report.
How to install research-synthesizer
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install littlebird-toolkit@wasp-nestThis installs the whole littlebird-toolkit plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill research-synthesizer -a claude-code3Manually: put the files in place
~/.claude/skills/research-synthesizer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/research-synthesizer/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill research-synthesizer -a codex2Manually: put the files in place
.agents/skills/research-synthesizer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill research-synthesizer -a cursor2Manually: put the files in place
.cursor/skills/research-synthesizer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/littlebird-toolkit/skills/research-synthesizer2Manually: put the files in place
.github/skills/research-synthesizer/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill research-synthesizer -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/littlebird-toolkit/skills/research-synthesizerManually: put the files in place
.devin/skills/research-synthesizer/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about research-synthesizer
How do I install research-synthesizer in Claude Code?
Add the marketplace with /plugin marketplace add legioncodeinc/vibe-coding-tools, then install the plugin with /plugin install littlebird-toolkit@wasp-nest.
What does research-synthesizer do?
It combines context retrieved from Littlebird with current external research to produce a topic brief. The brief distinguishes what the user has already encountered from what has changed.
What does research-synthesizer need to work?
It requires Littlebird MCP on a Power or Pro plan. External comparison also needs web search and page-fetch tools in the session; without them, only the internal research runs.