research

Research a topic and create a comprehensive note in the inbox.

Arguments

topic: A sentence, question, or topic to research

Instructions

Clarify the research scope:

Before researching, ask the user:
- Purpose: "What do you want to use this research for?"
  - Learning/understanding
  - Implementing something
  - Making a decision
  - Reference material
  - Other
- Depth: "How deep should I go?"
  - Quick overview (key points only)
  - Standard (balanced coverage)
  - Deep dive (comprehensive)
- Focus: "Any specific aspects to focus on?"
  - Let user specify particular angles or sub-topics
  - Or say "general overview"
- Context (if helpful): "What do you already know about this?"
  - Helps avoid repeating basics if user is advanced
  - Or know to start from fundamentals
Conduct research:

Based on the topic and user's answers:
- Use web search to find current information
- Gather key concepts, definitions, examples
- Find practical applications if relevant
- Note different perspectives or approaches
- Identify related topics for further exploration

Create the note in inbox/:

Filename: research-[topic-slug].md

---
title: "Research: [Topic]"
date: YYYY-MM-DD
tags:
  - type/research
  - [domain-specific tags]
purpose: [user's stated purpose]
depth: [quick/standard/deep]
---

# [Topic]

> [!info] Research Context
> **Purpose:** [why user wanted this]
> **Researched:** YYYY-MM-DD

## Overview
[Brief summary of the topic - 2-3 sentences]

## Key Concepts
- **Concept 1**: Explanation
- **Concept 2**: Explanation
- **Concept 3**: Explanation

## Details
[Main content based on depth level]
[Use subheadings as needed]

## Practical Applications
[How this is used in practice, if applicable]

## Considerations
[Trade-offs, limitations, things to watch out for]

## Sources
- [Source 1](url)
- [Source 2](url)

---

## Related
- [[potential-related-topic]]

> [!question] Open Questions
> - Questions that came up during research
> - Areas for further exploration

Present to user:
- Show the created note
- Ask if they want to expand any section
- Ask if they have follow-up questions
- Remind them to run /organize when ready to file it

Example usage

/research how does OAuth2 work
/research best practices for API design
/research Rust vs Go for backend services
/research what is event sourcing

Example interaction

User: /research kubernetes networking

Claude: I'll research Kubernetes networking for you. A few questions first:

1. What's the purpose of this research?
   - Learning K8s from scratch
   - Troubleshooting a specific issue
   - Designing a new deployment
   - Reference material

2. How deep should I go?
   - Quick overview
   - Standard coverage
   - Deep dive

3. Any specific focus?
   - Service mesh, ingress, CNI plugins, network policies, etc.

User: Learning, standard depth, focus on how pods communicate

Claude: [Conducts research and creates note]

Instructions

Clarify the research scope:

Before researching, ask the user:

Purpose: "What do you want to use this research for?"
- Learning/understanding
- Implementing something
- Making a decision
- Reference material
- Other
Depth: "How deep should I go?"
- Quick overview (key points only)
- Standard (balanced coverage)
- Deep dive (comprehensive)
Focus: "Any specific aspects to focus on?"
- Let user specify particular angles or sub-topics
- Or say "general overview"
Context (if helpful): "What do you already know about this?"
- Helps avoid repeating basics if user is advanced
- Or know to start from fundamentals

Conduct research:

Based on the topic and user's answers:

Use web search to find current information
Gather key concepts, definitions, examples
Find practical applications if relevant
Note different perspectives or approaches
Identify related topics for further exploration

Create the note in inbox/:

Filename: research-[topic-slug].md

---
title: "Research: [Topic]"
date: YYYY-MM-DD
tags:
  - type/research
  - [domain-specific tags]
purpose: [user's stated purpose]
depth: [quick/standard/deep]
---

# [Topic]

> [!info] Research Context
> **Purpose:** [why user wanted this]
> **Researched:** YYYY-MM-DD

## Overview
[Brief summary of the topic - 2-3 sentences]

## Key Concepts
- **Concept 1**: Explanation
- **Concept 2**: Explanation
- **Concept 3**: Explanation

## Details
[Main content based on depth level]
[Use subheadings as needed]

## Practical Applications
[How this is used in practice, if applicable]

## Considerations
[Trade-offs, limitations, things to watch out for]

## Sources
- [Source 1](url)
- [Source 2](url)

---

## Related
- [[potential-related-topic]]

> [!question] Open Questions
> - Questions that came up during research
> - Areas for further exploration

Present to user:

Show the created note
Ask if they want to expand any section
Ask if they have follow-up questions
Remind them to run /organize when ready to file it

Example interaction

User: /research kubernetes networking Claude: I'll research Kubernetes networking for you. A few questions first: 1. What's the purpose of this research? - Learning K8s from scratch - Troubleshooting a specific issue - Designing a new deployment - Reference material 2. How deep should I go? - Quick overview - Standard coverage - Deep dive 3. Any specific focus? - Service mesh, ingress, CNI plugins, network policies, etc. User: Learning, standard depth, focus on how pods communicate Claude: [Conducts research and creates note]

research

Additional Files (9)

research

Arguments

Instructions

Example usage

Example interaction

Related Skills

<h1 align="center">

Frontend Typescript Linting.mdc

2. Apply Deepthink Protocol (reason about dependencies

Additional Files (9)

research

Arguments

Instructions

Example usage

Example interaction