Investigate a technical or product question using current primary sources and relevant repository evidence, then synthesize cited facts, explicit inferences, uncertainties, and implications. Use when freshness, external documentation, comparisons, or multi-source evidence matter; do not use for simple stable facts, pure code implementation, or a review confined to an already provided patch.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add bigduu/Bamboo-agent --skill research --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Research?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bigduu-research)More formats (shields.io, HTML) on the badges page.
---
name: research
description: Investigate a technical or product question using current primary sources and relevant repository evidence, then synthesize cited facts, explicit inferences, uncertainties, and implications. Use when freshness, external documentation, comparisons, or multi-source evidence matter; do not use for simple stable facts, pure code implementation, or a review confined to an already provided patch.
---
# Research
Research the decision, not just the keywords.
1. Define the question, decision context, freshness requirement, and what evidence would change the answer.
2. Inspect relevant local code and documentation when the question concerns the workspace.
3. Prefer official documentation, specifications, standards, source repositories, and research papers. Use secondary sources only to discover or contrast primary evidence.
4. Verify dates, versions, scope, and definitions. Cross-check material claims when independent primary sources exist.
5. Separate sourced facts from inference and recommendation. Cite the direct source next to each material claim and explain uncertainty or conflicting evidence.
Keep research read-only unless the user separately asks for changes. If browsing, repository access, or a source is unavailable, state the limitation and avoid presenting memory as current verification. End with a concise synthesis tailored to the user's decision and list unresolved questions only when they matter.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!