Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Research a documentation topic — locate affected files, understand the problem, identify what to change.
Install Research
$ npx skills add docker/docs --skill research -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install docker/docs research --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/research .claude/skills/research && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "research" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/research into .claude/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/docker/docs/tree/main/.agents/skills/researchType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add docker/docs --skill research -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install docker/docs research --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/research .agents/skills/research && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "research" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/research into .agents/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add docker/docs --skill research -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install docker/docs research --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/research .cursor/skills/research && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "research" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/research into .cursor/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/docker/docs.git --path .agents/skills/research--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add docker/docs --skill research -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install docker/docs research --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/research .gemini/skills/research && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "research" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/research into .gemini/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install docker/docs researchInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add docker/docs --skill research -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/research .github/skills/research && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "research" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/research into .github/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add docker/docs --skill research -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install docker/docs research --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/docker/docs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/research .opencode/skills/research && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "research" agent skill from https://github.com/docker/docs/tree/main/.agents/skills/research into .opencode/skills/research/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "research", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
research- GitHub stars
- 4.7k
- Token cost
- ~797 tokens
- SKILL.md length
- 396 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Research a documentation topic — locate affected files, understand the problem, identify what to change.
- Works in 7 steps: Gather context → Locate affected files → Check vendored ownership → …
- Investigating an issue
- SKILL.md covers 1. Gather context, 2. Locate affected files, 3. Check vendored ownership and 4. Find related content, plus 4 more sections
- Calls gh; reaches docs.docker.com
What it does
Research is an agent skill from docker/docs, published by the product's own GitHub organization. Research a documentation topic — locate affected files, understand the problem, identify what to change. Use when investigating an issue, a question, or a topic before writing a fix. Triggers on: "research issue 1234", "investigate what needs changing for 500", "what files are affected by 200", "where is X documented", "is our docs page about Y accurate", "look into how we document Z".
Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. The repository describes itself as: Source repo for Docker's Documentation. The licence is Apache-2.0.
When your agent uses it
- Investigating an issue
- A topic before writing a fix
- : research issue 1234
- Investigate what needs changing for 500
Example prompts
- “research issue 1234”
- “investigate what needs changing for 500”
- “what files are affected by 200”
- “/research”
Requirements
- Docker
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 65aa5cd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
docs.docker.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Research loads about 797 tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 396 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from docker/docs at commit 65aa5cd, republished under its Apache-2.0 licence (© docker). 396 words, ~797 tokens.
Download SKILL.mdSave it as
.claude/skills/research/SKILL.md (or your agent's skills folder).- name
- research
- description
- Research a documentation topic — locate affected files, understand the problem, identify what to change. Use when investigating an issue, a question, or a topic before writing a fix. Triggers on: "research issue 1234", "investigate what needs changing for #500", "what files are affected by #200", "where is X documented", "is our docs page about Y accurate", "look into how we document Z".
Research
Thoroughly investigate the topic at hand and produce a clear plan for the fix. The goal is to identify exact files, named targets within those files, and the verified content needed for the fix.
1. Gather context
If the input is a GitHub issue number, fetch it:
gh issue view <number> --repo docker/docs \
--json number,title,body,labels,commentsOtherwise, work from what was provided — a description, a URL, a question, or prior conversation context. Identify the topic, affected feature, or page to investigate.
2. Locate affected files
Search content/ using the URL or topic from the issue. Remember the
/manuals prefix mapping when converting URLs to file paths.
For each candidate file, read the relevant section to confirm it contains the reported problem.
3. Check vendored ownership
Before planning any edit, verify the file is editable locally:
_vendor/— read-only, vendored via Hugo modulesdata/cli/— read-only, generated from upstream YAMLcontent/reference/cli/— read-only, generated fromdata/cli/- Everything else in
content/— editable
If the fix requires upstream changes, identify the upstream repo and note it as out of scope. See the vendored content table in CLAUDE.md.
4. Find related content
Look for pages that may need updating alongside the primary fix:
- Pages that link to the affected content
- Include files (
content/includes/) referenced by the page - Related pages in the same section describing the same feature
Show full SKILL.md (184 more words)Show less
5. Verify facts
If the issue makes a factual claim about how a feature behaves, verify it. Follow external links, read upstream source, check release notes. Do not plan a fix based on an unverified claim.
If the fix requires a replacement URL and that URL cannot be verified (e.g. network restrictions), report it as a blocker rather than guessing.
6. Check the live site (if needed)
For URL or rendering issues, fetch the live page:
https://docs.docker.com/<path>/7. Report findings
Summarize what you found — files to change, the specific problem in each, what the fix should be, and any constraints. This context feeds directly into the write step.
Be specific: name the file, the section or element within it, and the
verified content needed. "Fix the broken link in networking.md" is not
specific enough. "In compose/networking.md, the 'Custom networks' section,
remove the note about driver_opts being ignored — this was fixed in
Compose 2.24" is.
Notes
- Research quality bounds write quality. Vague research produces broad changes; precise research produces minimal ones.
- Do not create standalone research files — findings stay in conversation context for the write step.
© docker, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/research of docker/docs.
Open the folder on GitHubat commit 65aa5cd
Compare with similar skills
Research next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Research this skilldocker/docs | 4.7k | — | ~797 | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from docker/docs
All 13 skills in this repo- Official
Agent Readiness Audit
docker/docs
Audit a documentation site for agent-friendliness: discovery, markdown delivery, crawlability, semantic structure, machine-readable surfaces, and content legibility.
- Official
Migrate Content Ia
docker/docs
Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…
- Official
Write
docker/docs
Write or edit reader-facing technical prose for immediate comprehension.
- Official
Create Lab Guide
docker/docs
Clone a dockersamples Labspace repo, extract learning objectives and module structure from labspace.yaml, and produce a Hugo guide page under content/guides/ with correct frontmatter…
- Official
Curate Whats New
docker/docs
Curate noteworthy Docker launches from documentation pull requests merged during a requested period.
- Official
Fix Issue
docker/docs
Fix a single GitHub issue end-to-end: triage, research, write the fix, review, and create a PR.
Related
Categories
Questions about Research
What does Research do?
Research a documentation topic — locate affected files, understand the problem, identify what to change. Research is an agent skill from docker/docs, published by the product's own GitHub organization. Research a documentation topic — locate affected files, understand the problem, identify what to change.
When should I use Research?
Research fits situations like: investigating an issue; A topic before writing a fix; : research issue 1234; investigate what needs changing for 500.
How do I install Research in Claude Code?
Run `npx skills add docker/docs --skill research -a claude-code`. Or copy the skill folder (.agents/skills/research in docker/docs) into .claude/skills/research in your project. Claude Code loads it when a task matches its description.
How do I install Research in Codex?
Run `npx skills add docker/docs --skill research -a codex`. Or copy the skill folder (.agents/skills/research in docker/docs) into .agents/skills/research in your project. Codex loads it when a task matches its description.
Can I use Research in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add docker/docs --skill research -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/research, .gemini/skills/research, .github/skills/research and .opencode/skills/research in your project.
What does Research need to run?
Going by SKILL.md and its folder, Research needs the command-line tools its instructions call (gh). Our summary lists: Docker.
Does Research access the network?
SKILL.md names 1 domain. In commands or code: docs.docker.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Research safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Research use?
Research is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Research use?
About 797 tokens (SKILL.md is roughly 3.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Research?
Skills that share tags, products or a category with Research: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Research?
docker (a GitHub organization, an official publisher) maintains it in docker/docs, which has 4,666 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.
Source: docker/docs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.