Quick Web Research Strategy

What This Skill Does

Provides fast, targeted search methodology for simple questions requiring direct factual answers from authoritative sources. Implements single-pass workflow with precise query formulation and minimal citation overhead.

When to Use This Skill

Use this skill when the research question requires:

• Version lookups: "What version of React Router was released in 2025?"
• Documentation finding: "Find docs for Terraform AWS provider"
• Simple definitions: "What is GraphQL?"
• Existence checks: "Does Next.js support Server Components?"
• URL/link requests: "Link to Python asyncio documentation"

Triggers: Keywords like "what version", "find docs", "link to", "what is", "does X support", "URL for"

Instructions

Single-Pass Workflow

Objective: Execute 1-2 targeted queries, identify 1-2 authoritative sources, extract concise answer.

Step 1: Targeted Query Formulation (1-2 Queries)

Generate 1-2 highly specific queries using advanced operators:

Query Strategy:

• Official Source Priority: Use site: operator for authoritative domains
• File Type Targeting: Use filetype: for specific document types
• Exact Phrase Matching: Use "exact phrase" for precision
• Recent Content: Use after:YYYY for latest information

Examples:

Version Lookup:
- site:npmjs.com "react-router" "version"
- site:github.com "react-router" "releases" after:2025

Documentation Finding:
- site:terraform.io "aws provider" "documentation"
- site:docs.python.org "asyncio"

Simple Definition:
- site:graphql.org "what is GraphQL"
- "GraphQL definition" site:official-docs

Existence Check:
- site:nextjs.org "Server Components" "support"
- "Next.js Server Components" site:vercel.com

Step 2: Authoritative Source Identification (1-2 Sources)

Target Authoritative Sources:

• Official documentation: Framework/library official sites
• Package registries: npm, PyPI, Maven Central
• Official GitHub repos: Releases, changelog
• Peer-reviewed sources: Academic papers (rare for quick lookups)

Credibility Hierarchy:

1. Official docs (highest authority)
2. Official GitHub/package registry
3. Established tech publications (MDN, Smashing Magazine)
4. Community sources (Stack Overflow) - only if official unavailable

Step 3: Extract Concise Answer

Extract direct answer with minimal context:

Answer Format:

{Concise 1-3 sentence answer with inline citation [1]}

Optional: {1 sentence additional context if needed} [2]

Examples:

Version Lookup:
React Router v7.2.0 was released on March 15, 2025 [1]. The release introduced new data loading APIs and improved TypeScript support [1].

Documentation Finding:
The Terraform AWS Provider documentation is available at https://registry.terraform.io/providers/hashicorp/aws/latest/docs [1].

Simple Definition:
GraphQL is a query language for APIs that allows clients to request exactly the data they need [1].

Existence Check:
Yes, Next.js 14+ supports Server Components as a stable feature [1]. Server Components are enabled by default in the App Router [1].

Step 4: Minimal Citation

Provide 1-2 citations with essential information only:

Citation Format:

[1] **{Source Title}**
    - URL: {URL}
    - Author/Org: {organization}
    - Date: {YYYY-MM-DD}
    - Excerpt: "{1-sentence quote}"

Example:

[1] **React Router v7 Release Notes**
    - URL: https://github.com/remix-run/react-router/releases/tag/v7.2.0
    - Author/Org: Remix Team
    - Date: 2025-03-15
    - Excerpt: "React Router v7.2.0 introduces new data loading APIs..."

Step 5: Verify Factual Accuracy

Quick verification checklist:

• Answer directly addresses the question?
• Source is authoritative (official or highly credible)?
• Information is recent (if time-sensitive)?
• Citation includes URL for user verification?

No iteration - single pass only for quick mode.

Output Template

# Web Research Analysis (Quick Mode)

**Research Mode**: quick
**Objective**: {1-sentence: what was researched}

---

## Answer

{Concise 1-3 sentence answer with inline citations [1][2]}

---

## Source Citations

[1] **{Source Title}**
    - URL: {URL}
    - Author/Org: {author/org}
    - Date: {date}
    - Excerpt: "{quote}"

[2] **{Source Title}** (if applicable)
    - URL: {URL}
    - Author/Org: {author/org}
    - Date: {date}
    - Excerpt: "{quote}"

Examples

Example 1: Version Lookup

Scenario: "What version of React Router was released in 2025?"

Process:

Query (1):
site:github.com "react-router" "releases" "2025"

Source Identified (1):
React Router GitHub Releases [1]

Answer Extracted:
React Router v7.2.0 was released on March 15, 2025 [1].

Citation:
[1] React Router v7.2.0 Release
    - URL: https://github.com/remix-run/react-router/releases/tag

...