Skip to content

/deep-research-glim

Conducts deep, multi-angle research using glim MCP tools and parallel subagents. Use for deep research, competitive landscape analysis, strategic intelligence, or /deep-research-glim [topic]. Triggers - deep research, deep dive on, competitive landscape, strategic intelligence,

shell
$ npx -y skills add tenequm/skills --skill deep-research-glim --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/deep-research-glim
How auto-invocation works

Context preview

The summary Claude sees to decide when to auto-load this skill.

Conducts deep, multi-angle research using glim MCP tools and parallel subagents. Use for deep research, competitive landscape analysis, strategic intelligence, or /deep-research-glim [topic]. Triggers - deep research, deep dive on, competitive landscape, strategic intelligence,

SKILL.md

deep-research-glim.SKILL.md
name: deep-research-glim
description: Conducts deep, multi-angle research using glim MCP tools and parallel subagents. Use for deep research, competitive landscape analysis, strategic intelligence, or /deep-research-glim [topic]. Triggers - deep research, deep dive on, competitive landscape, strategic intelligence, multi-source synthesis.
metadata:
  version: "0.2.6"
  openclaw:
    homepage: https://github.com/tenequm/skills/tree/main/skills/deep-research-glim
    emoji: "🔭"

Deep Research (glim)

You are conducting deep, multi-angle research using the glim MCP suite and parallel subagents. The goal is strategic intelligence with cross-source validation, evidence-rich findings, and orthogonal insights that single-pass searches miss.

Invocation pattern: `/deep-research-glim [topic]` or any of the trigger phrases in the description. The user may also pass an explicit `[topic]` argument; if absent, ask once before fanning out.

Tool policy

Always prefer glim MCP tools (`mcp__glim__*`) over `WebSearch` or `WebFetch`, both for yourself and for every subagent you spawn. glim primitives cover web search, web crawl, GitHub, Reddit, Twitter / X, Amazon, and YouTube subtitles. Read each tool's schema at invocation time for current parameters and capabilities.

Core Principles

  • **Context engineering**: smaller context budgets for broad scanning, larger budgets for critical deep dives.
  • **Search depth control**: match search depth to the task - quick scan for landscape mapping, comprehensive search for authoritative sources.
  • **Progressive disclosure**: start broad and light, identify key sources, then deep-dive only where it pays off.
  • **Synthesis over summarization**: extract cross-source patterns and actionable insights, not sequential source descriptions.
  • **Explicit novelty seeking**: actively search for contrarian views, unique angles, and lesser-known insights that complement mainstream findings.
  • **Plain hyphens only**: no emdashes, en-dashes, em-dashes, or `--`. Use `-` everywhere in output.

Execution

Stage 0: Topic Assessment & Source Planning

Before spawning anything, internally commit to a one-paragraph plan covering:

1. **What is the actual question?** Restate the topic in your own words. If ambiguous, identify 2-3 interpretations and pick the most useful, or ask the user once. 2. **Where should we look?** Available glim primitives: web (search + crawl), GitHub, Reddit, Twitter / X, Amazon, YouTube subtitles. Pick whichever fit the topic. 3. **What is already known?** If the user provided context (a doc, prior conversation, design file), read it first. Subagents must know what NOT to repeat.

Stage 1: Multi-Angle Discovery (always 3 parallel subagents)

Spawn three subagents in parallel via the Task tool (`subagent_type=general-purpose`, `run_in_background=true`). Each gets a distinct angle.

Subagent 1A: Broad Overview

Mission: establish baseline; identify themes, key players, dominant narrative.

Searches: 2-3 broad queries via glim web search.

Sample queries:

  • `"[topic] overview 2025-2026"`
  • `"[topic] comprehensive guide"`
  • `"what is [topic] how it works"`

Returns: themes, key players, 2-3 areas requiring deep dives, source URLs.

Subagent 1B: Diversified Perspectives

Mission: cover technical, user, comparative, leadership, and critical angles with balanced context.

Searches: 6-8 queries across categories via glim web search. Reach for glim GitHub, Reddit, or Twitter primitives where the topic warrants.

Query categories (one or two queries each):

  • Technical / implementation: `"[topic] architecture design patterns"`, `"[topic] technical deep dive engineering"`
  • User / community: `"[topic] developer experience feedback"`, `"[topic] user testimonials reviews"`
  • Comparative: `"[topic] vs [alternatives] comparison benchmarks"`, `"[topic] alternatives competitors"`
  • Case studies: `"[topic] case studies customer success stories"`, `"[topic] real-world use cases"`
  • Leadership / strategy: `"[topic] founder interview CEO strategy"`, `"[topic] company blog announcements"`
  • Critical: `"[topic] limitations problems challenges"`, `"[topic] criticism drawbacks cons"`

Returns: per-category findings with URLs, quotes, data points.

Subagent 1C: Novelty & Trend Search

Mission: contrarian views, lesser-known strategies, emerging signals.

Searches: 2-3 queries via glim web search. Reddit and X are often where contrarian opinions live.

Sample queries:

  • `"[topic] contrarian opinions different perspective"`
  • `"[topic] lesser-known strategies hidden tactics"`
  • `"[topic] emerging trends future directions 2026"`

Returns: orthogonal insights, contrarian views, emerging signals.

Stage 1 contract

Each subagent returns structured findings under 1500 words containing: themes, evidence (quotes, data, dates), source URLs as clickable markdown links, unique angles. Wait for all three before Stage 2.

Stage 2: Critical Deep Dives (dynamic N parallel subagents)

After Stage 1 returns, evaluate the aggregated findings. Identify the critical sources or angles that warrant full content extraction:

  • Founder / CEO interviews with strategic insight
  • Comprehensive case studies with metrics
  • Technical deep-dives requiring full context
  • Primary sources with unique data
  • Specific GitHub repos worth deep audit (README + commits + issues)
  • Reddit threads with high-signal discussion
  • YouTube videos whose transcripts hold unique content

Decide N based on what Stage 1 surfaced. N is your judgment - could be 2, could be 6. Spawn N subagents in parallel via the Task tool, one per critical source or angle. Each uses the appropriate glim detail primitive (web crawl, GitHub get, Reddit post, Twitter tweet, YouTube subtitles) for full-content extraction.

Each Stage 2 subagent returns: full extracted content, key quotes, data points, why this source matters.

Stage 3: Coverage Validation

Run the gap-detection checklist on the aggregated

Read more
Read it on GitHub ↗

Showing the first part of this file.

Ships withtenequm-skills

Claude Code skills for founders, developers, and web3 builders. This repository publishes reusable skill folders under skills//, ships stable bundle downloads through GitHub Releases, and publishes changed skills to ClawHub.

Get the whole plugin, auto-invoked