research

Investigate questions against primary sources and save findings as cited Markdown notes.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/filippolmt/skills --skill research-filippolmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/filippolmt/skills/tree/main/skills/research
Command: npx skills add https://github.com/filippolmt/skills --skill research-filippolmt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Researching a technical question properly means reading official docs, source code, and specs rather than secondhand blog posts, and that reading takes time away from your main work. This Skill delegates that legwork to a background agent so you keep working while the investigation runs. ## Core Features & Use Cases - Primary-source investigation: The agent follows every claim back to official documentation, source code, specs, or first-party APIs instead of relying on secondary write-ups. - Cited Markdown output: Findings are written to a single Markdown file with each claim's source cited. - Convention-aware placement: The report is saved where the repo already keeps such notes, matching existing conventions or a sensible default location. - Use Case: Ask how a specific API rate limit behaves; the background agent reads the vendor's official docs and source, then drops a cited summary file into your repo's notes directory while you continue coding. ## Quick Start Ask the agent to research how a specific library or API feature works using primary sources and save the findings as a Markdown note in the repo.

Frequently Asked Questions about research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research a technical question without stopping my own work?

Delegate the question to a background agent that reads primary sources while you continue working. The agent investigates official docs, source code, and specs, then writes its findings to a Markdown file in your repo.

How to gather API documentation facts with cited sources?

Have the agent follow every claim back to the source that owns it, such as official documentation or first-party API references. Each claim in the resulting Markdown report includes a citation to its source.

Where does the research report get saved?

The report is saved where the repository already keeps such notes, matching the existing convention. If no convention exists, the agent picks a sensible location and tells you where it put the file.

Does the research agent use blog posts and tutorials as sources?

No, the agent is instructed to investigate against primary sources only: official docs, source code, specs, and first-party APIs. Secondary write-ups are avoided so claims trace back to authoritative origins.

When should I not use a background research agent?

Avoid it for questions answerable from code already open in your session or when you need interactive back-and-forth reasoning. It suits self-contained reading tasks whose output is a written findings document.