research-methodology

Guide systematic research of technical documentation with source verification and organized briefs.

15|3|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/richardcb/oh-my-gemini --skill research-methodology-richardcb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-methodology
Source: https://github.com/richardcb/oh-my-gemini/tree/main/skills/research-methodology
Command: npx skills add https://github.com/richardcb/oh-my-gemini --skill research-methodology-richardcb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of efficiently and reliably gathering, verifying, and synthesizing technical information from various sources, ensuring that research is thorough, accurate, and actionable.

Core Features & Use Cases

  • Structured Research Process: Guides users through a systematic approach to information gathering.
  • Source Prioritization: Emphasizes reliable sources like official documentation and reputable code repositories.
  • Verification: Mandates cross-referencing and checking publication dates to ensure information quality.
  • Synthesized Output: Formats findings into clear "Research Briefs" with summaries, key findings, code examples, and recommendations.
  • Use Case: When tasked with understanding a new API, finding best practices for a specific technology, or comparing different technical approaches, this skill provides a framework to ensure comprehensive and trustworthy results.

Quick Start

Use the research methodology skill to find and synthesize documentation for the 'gemini-python-sdk'.

Frequently Asked Questions about research-methodology

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically research and synthesize technical documentation for a new API?

Systematic API research involves gathering technical information from official documentation, verifying sources through cross-referencing, and synthesizing findings into actionable research briefs with code examples and recommendations.

What is the best way to verify technical information found in code examples and blogs?

Verifying technical information requires cross-referencing multiple sources, prioritizing official documentation, checking publication dates, and comparing against reputable code repositories to ensure accuracy.

How do I structure a research brief when investigating different technical approaches?

Structure a research brief by organizing synthesized findings into summaries, key findings, reputable code examples, and actionable recommendations based on verified technical information.

Can I use this methodology to gather best practices for a specific technology?

Yes, this methodology guides gathering best practices by prioritizing official documentation, investigating APIs, and synthesizing technical information with source verification for accurate results.

What are the limitations of relying on technical blogs instead of official documentation?

Technical blogs may lack verification and current accuracy, whereas official documentation provides authoritative technical information, making cross-referencing essential for reliable research briefs.

When do I need a structured research process for technical information gathering?

A structured research process is needed when investigating new APIs, comparing technical approaches, or finding best practices, ensuring thoroughness, accuracy, and clear presentation of technical information.