Index of every page on this site: llms.txt
All skills
onmax avatar

/research

@f6b18e9
Run it yourself

Use when the user asks how others or the industry handle something, what the standard is, or wants evidence before a decision.

Use this Skill: https://skilld.dev/gh/onmax/skills/research

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈34 tokens for metadata: the name and description. ≈519 when used: this file.

Description uses 1.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈137 characters, or 1.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.
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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill functions as a research assistant that gathers information from primary sources such as documentation and source code. No security issues were detected.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at f6b18e9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 5 days ago

README badge

README badge for onmax/skills/research