Individual skill
research
Investigate a question against primary sources, cite every claim, and write the findings into the repository's own notes.
skills/research/SKILL.md
Source commit 9ed2e1695357402f5eedc1b540f73b638a5bfba7
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 6, 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)
- 351
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- cli Repository topic
- developer-tools Repository topic
- claude Repository topic
- claude-code Repository topic
- context-engineering Repository topic
- ai-developer-tools Repository topic
- anthropic Repository topic
- automation Repository topic
- autonomous-agents Repository topic
- productivity Derived category
- research Derived category
- productivity-notes 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
SKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesSKILL.mdcore · 7,249 bytesagents/openai.yamlasset · 256 bytes
Read excerpt
# Research
Answer a question from the sources that own the facts, and leave a document another agent can act on without repeating the reading. Research writes notes; it never edits source, configuration, or state.
The reading half is a saved workflow, not a procedure this skill performs inline. Its single source of truth is `.claude/workflows/research-sweep.js` in the genie repository's canonical workflow catalog (see `.claude/workflows/README.md` there); this skill is its front door. On a runtime that runs saved workflows, run the script at `<repository root>/.claude/workflows/research-sweep.js` when that file exists, otherwise `~/.claude/workflows/research-sweep.js` (delivered by `genie install` / `genie update`); give the runtime that explicit script path, never a bare name — both scopes now carry these names and the order a name resolves in is undocumented. Pass `{question, sources[], notesHint?, maxReaders?, model?, timestamp?}`. The question and the source list are settled here and arrive FROZEN: the workflow never re-asks, narrows or widens the question, and never adds a source of its own. Relay the returned findings document unchanged, and list `notConvened` (agents that returned nothing), the unread sources, and every injection attempt beside it rather than filling any of those gaps yourself.
## What stays with you
1. **Settle the question.** One question, stated as the caller means it. Splitting it into sub-questions, or widening it after the first surprising finding, is a second sweep with a second frozen question — not an edit to this one.
2. **Name the sources you already know.** URLs or repository-relative paths, the primary ones first. The sweep reads the list it is handed and adds nothing; a source you did not name is a source nobody opens.
3. **Write the findings into the repository's notes.** The sweep writes no file. Record the notes inside the repository, under the brainstorm directory for the work that prompted them, or in the wish that owns the question. Match the convention already in place. The operating system's temporary directory is not a destination: notes written there are lost before anyone reads them, and they never reach the reviewer.
4. **Take the decision.** A sweep returns evidence, not a verdict. What the findings mean for the work is yours to say, and to say out loud.
## Primary sources only