research
Investigates a question against primary sources (official docs, source code, specs, first-party APIs) and writes the findings, with a citation for every claim, to a Markdown file. Use when the user wants a topic researched or facts gathered from documentation, when a decision waits on facts from outside the repo, and when reading legwork should run while other work continues.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-19
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- research
- description
- Investigates a question against primary sources (official docs, source code, specs, first-party APIs) and writes the findings, with a citation for every claim, to a Markdown file. Use when the user wants a topic researched or facts gathered from documentation, when a decision waits on facts from outside the repo, and when reading legwork should run while other work continues.
02 资源文件 1
- 参考文档agents/openai.yaml122 B
03 SKILL.md 正文
Research
Delegate the reading to a subagent running in the background where the host supports one (Claude Code's Agent tool, Codex's spawned agents), so other work continues; otherwise do the reading yourself. The brief carries the question and any constraints from where it came from (a ticket, the conversation), and asks it to:
- Answer the question from primary sources: official documentation, source code, specifications, first-party APIs. Follow each claim back to the source that owns it rather than a secondary write-up of it.
- Write the findings to one Markdown file, citing the source of every claim, and say plainly what couldn't be verified.
- Save it where the repo already keeps such notes; with no convention, pick a sensible place and report the path.
Done when the file exists, every claim in it carries a citation, and its path is reported back.
04 同仓库更多 Skills
teach
Teach yourself a topic over several sessions, with lessons, references, and a record of what you've learned.
svg-logo-designer
Generate SVG logos with multiple concepts, layouts, and color variations.
documentation-writer
Writes and revises human-facing documentation — READMEs, contributor and setup guides, reference pages, architecture notes, CLAUDE.md, and changelog entries. Covers picking the right document type for the question being asked, structuring for skimming, writing examples that actually run, and keeping docs from going stale. Use when creating or rewriting docs, when a README has drifted from the code, or when deciding where a piece of information belongs. For SKILL.md and agent files, use /skill-writer instead.
adhd-mode
Shapes every response for a reader with ADHD: the next action first, numbered steps, progress restated each turn, tangents held back, concrete time estimates, wins made visible. Stays on for the rest of the session until the reader says "stop adhd mode". On Claude Code, the harness-kit:adhd output style does the same without invoking this skill.
wait-what
That last message didn't land: re-explain it with the missing context.
to-questionnaire
Turn a decision you can't make alone into a questionnaire for the one person who can answer it, filled in async or together in a meeting.