Individual skill
research
Investigate a question against primary sources and capture cited findings as Markdown. Use when the user wants a topic researched, docs or API facts gathered, or reading delegated to a background agent. Pass the question as the argument. Don't use for implementing against pinned dependency versions (/source-driven) or codebase search.
skills/research/SKILL.md
Source commit ced546848ec8eea8541e77b7aa041207b607462e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 20
- Repository last updated
- Oct 26, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- skills Repository topic
- cursor Repository topic
- antigravity Repository topic
- claude-code Repository topic
- agents Repository topic
- codex Repository topic
- docs Derived category
- research Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Research
You run as a background agent, so the user keeps working while you read. You can't see their conversation: the question is `$ARGUMENTS`, and it carries everything you get. Empty → stop and report that the question must be passed as the argument.
1. **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.
2. **Write the findings to a single Markdown file**, citing each claim's source inline (link or path).
3. **Save it where the repo already keeps such notes.** Match the existing convention; if there is none, put it in `.specs/research/<slug>.md`.
Finish by reporting the file path. Don't summarize the findings unless asked — the cited file is the deliverable.