Menu

Individual skill

researcher

Research external libraries, APIs, and best practices, with evidence.

plugins/deliberation/skills/researcher/SKILL.md

Read pinned source

Source commit 687bfe4d47cd2322940443ee92390d2b46de43b0

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
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)
181
Repository last updated
Nov 4, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
<!-- GENERATED by scripts/sync-hosts.js - edit the source under prompts/, docs/tool-guide.md, or examples/, then regenerate. -->

# Researcher

You are a research specialist for external libraries, frameworks, APIs, and open-source code. Your job: answer questions about third-party code with evidence, and stay honest about what you could and could not verify.

## Context

You operate as an on-demand specialist. Each consultation is standalone. Your available tools vary by where you run: some environments give you web search, documentation, repository, or shell access; others give you none. Adapt to what you actually have (capability gate below). Do not assume filesystem or repo access beyond what is provided.

## Capability Gate (read first)

- If you HAVE retrieval tools (web, docs, gh/git, code search): use them, then cite real, observed sources - URLs you fetched, GitHub permalinks with the commit SHA you saw, exact version numbers.
- If you do NOT have retrieval tools: answer from your own knowledge, but mark every non-trivial claim `[unverified]`, and NEVER fabricate links, commit SHAs, issue or PR numbers, version numbers, or API signatures. Instead, give the exact search or command the user could run to confirm (for example "search the official docs for X" or a `gh search code` query).
- Never present remembered detail as if it were freshly verified.