---
name: research
description: Use when the user asks how others or the industry handle something, what the standard is, or wants evidence before a decision.
title: research
canonical_url: https://skilld.dev/gh/onmax/skills/research
last_updated: 2026-11-16T18:30:58.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install onmax/skills/research`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/research`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/onmax/skills/research) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/research`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/research --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/research --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Research

Run the research in a subagent. The prompt you write is the research; the subagent's final answer is the result. Write no files: the result comes back in chat.

Skip the subagent when a quick lookup or a few links settle the question.

## Write the prompt

The subagent sees none of this conversation, so the prompt must stand alone. Include:

1. **Question.** One decision in one sentence, e.g. "How do comparable libraries handle X, and which approach fits us?"
2. **Context.** What we're building, constraints, what was already tried or ruled out, and what the user cares about in their own words: the owner of a bug, a unit, a UI behavior, the size of a change.
3. **Where to look.** Name comparable projects or vendors and why each is comparable. Primary sources first: official docs, source repos, RFCs, changelogs, maintainers' writing. For questions about our own work: repo history, issues, PRs, logs.
4. **What would change the answer.** The facts that would flip the recommendation, so the subagent looks for them.
5. **Limits.** Read-only: no repo edits, files, PRs, or deploys. Say how deep to go.
6. **Return format.** Paste the one below.

```md
Return, in this order and briefly:
- Answer: the recommendation and its biggest limitation.
- How others do it: per comparable, what they do, a link, and why it applies.
- Common practice vs. what fits our case.
- Disagreements between sources, kept, not smoothed over.
- What is evidence and what is your inference.
- What would reverse the recommendation.
```

Use several subagents only when evidence streams are independent, such as the ecosystem versus our own repo history. Give each its own complete prompt.

## After it returns

- Check that claims rest on linked sources. If something is thin or off-question, ask the same subagent a follow-up instead of filling the gap yourself.
- Reply with the answer first, then only the decisive evidence and links. Fit it to what the user asked: owner, unit, behavior, or scope.
- Research doesn't authorize changes. Act on it only when the user asks.
