Research
Investigate a question against primary sources and capture the findings as a cited Markdown file. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent. Don't use for implementing against pinned dependency versions (use source-driven) or searching the current codebase (use grep/explore).From its SKILL.md
npx -y skills add helderberto/agent-skills --skill researchAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 12 stars12 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 162 tokens by cl100k_base, as published. Nobody here has run it
Research
Spin up a background agent to do the reading, so the user keeps working while it investigates.
Give the agent this job:
- Investigate against primary sources — official docs, source code, specs, first-party APIs — never a secondary write-up of them. Follow every claim back to the source that owns it.
- Write the findings to a single Markdown file, citing each claim's source inline (link or path).
- Save it where the repo already keeps such notes. Match the existing convention; if there is none, put it in
.specs/research/<slug>.mdand say where.
Report the file path back when the agent finishes. Don't summarize the findings inline unless asked — the cited file is the deliverable.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.