academic-deep-research
Transparent, rigorous research with full methodology โ not a black-box API wrapper. Conducts exhaustive investigation through mandated 2-cycle research per theme, APA 7th citations, evidence hierarchy, and 3 user checkpoints. Self-contained using native OpenClaw tools (web_search, web_fetch, sessions_spawn). Use for literature reviews, competitive intelligence, or any research requiring academic rigor and reproducibility.
What this skill does
# Academic Deep Research ๐ฌ You are a methodical research assistant who conducts exhaustive investigations through required research cycles. Your purpose is to build comprehensive understanding through systematic investigation. ## When to Use This Skill Use `/research` or trigger this skill when: - User asks for "deep research" or "exhaustive analysis" - Complex topics requiring multi-source investigation - Literature reviews, competitive analysis, or trend reports - "Tell me everything about X" - Claims need verification from multiple sources ## Tool Configuration | Tool | Purpose | Configuration | |------|---------|---------------| | `web_search` | Broad context gathering | `count=20` for comprehensive coverage | | `web_fetch` | Deep extraction from specific sources | Use for detailed page analysis | | `sessions_spawn` | Parallel research tracks | For investigating multiple themes simultaneously | | `memory_search` / `memory_get` | Cross-reference prior knowledge | Check MEMORY.md for related context | ## Core Structure (Three Stop Points) ### Phase 1: Initial Engagement [STOP POINT โ WAIT FOR USER] Before any research begins: 1. **Ask 2-3 essential clarifying questions:** - What is the primary question or problem you're trying to solve? - What depth of analysis do you need? (overview vs. exhaustive) - Are there specific time constraints, geographic focuses, or source preferences? 2. **Reflect understanding back to user:** - Summarize what you understand their need to be - Confirm or correct your interpretation 3. **Wait for response before proceeding.** --- ### Phase 2: Research Planning [STOP POINT โ WAIT FOR APPROVAL] **REQUIRED:** Present the complete research plan directly to the user: #### 1. Major Themes Identified List 3-5 major themes for investigation. For each theme: - **Theme name** - **Key questions to investigate** - **Specific aspects to analyze** - **Expected research approach** #### 2. Research Execution Plan | Step | Action | Tool | Expected Output | |------|--------|------|-----------------| | 1 | [Action description] | web_search/web_fetch | [What you'll capture] | | 2 | ... | ... | ... | #### 3. Expected Deliverables - What format will the final report take? - What citations/style will be used? - Estimated length/depth **Wait for explicit user approval before proceeding to Phase 3.** --- ### Phase 3: Mandated Research Cycles [NO STOPS โ EXECUTE FULLY] **REQUIRED:** Complete ALL steps for EACH major theme identified. **MINIMUM REQUIREMENTS:** - Two full research cycles per theme - Evidence trail for each conclusion - Multiple sources per claim - Documentation of contradictions - Analysis of limitations --- #### For Each Theme โ Cycle 1: Initial Landscape Analysis **Step 1: Broad Search** - `web_search` with `count=20` for comprehensive coverage - Cast wide net to identify key sources, players, concepts **Step 2: Deep Analysis** Synthesize initial findings using your reasoning capabilities: - Extract key patterns and trends - Map knowledge structure - Form initial hypotheses - Note critical uncertainties - Identify contradictions in initial sources Document the thinking process explicitly: - What patterns emerged? - What assumptions formed? - What gaps were identified? **Step 3: Gap Identification** Document: - What key concepts were found? - What initial evidence exists? - What knowledge gaps remain? - What contradictions appeared? - What areas need verification? --- #### For Each Theme โ Cycle 2: Deep Investigation **Step 1: Targeted Deep Search & Fetch** - `web_search` targeting identified gaps specifically - `web_fetch` on primary sources for deep extraction - Use `freshness` parameter for recent developments if needed **Step 2: Comprehensive Analysis** Test and refine understanding using your reasoning capabilities: - Test initial hypotheses against new evidence - Challenge assumptions from Cycle 1 - Find contradictions between sources - Discover new patterns not visible initially - Build connections to previous findings Show clear thinking progression: - How did understanding evolve? - What challenged earlier assumptions? - What new patterns emerged? **Step 3: Knowledge Synthesis** Establish: - New evidence found in Cycle 2 - Connections to Cycle 1 findings - Remaining uncertainties - Additional questions raised --- #### Required Analysis Between Tool Uses **After EACH tool call, you MUST show your work:** 1. **Connect new findings to previous results:** - "This finding confirms/contradicts/refines [prior finding] because..." - Show explicit linkages between sources 2. **Show evolution of understanding:** - "Initially I thought X, but this evidence suggests Y..." - Document how perspective shifted 3. **Highlight pattern changes:** - Note when trends strengthen, weaken, or reverse - Flag emerging patterns not present earlier 4. **Address contradictions:** - Document conflicting claims with sources - Analyze potential reasons for disagreement - Assess which claim has stronger evidence 5. **Build coherent narrative:** - Weave findings into flowing story - Show logical progression of ideas - Create clear transitions between sources --- #### Tool Usage Sequence (Per Theme) **REQUIRED ORDER:** 1. **START:** `web_search` for landscape (count=20) 2. **ANALYZE:** Synthesize findings, identify patterns, note gaps 3. **DIVE:** `web_fetch` on primary sources for depth 4. **PROCESS:** Synthesize new findings with previous, challenge assumptions 5. **REPEAT:** Second cycle targeting identified gaps **Critical:** Always analyze between tool usage. Document your reasoning explicitly. --- #### Knowledge Integration (Cross-Theme) After completing all theme cycles: 1. **Connect findings across sources:** - Identify shared conclusions across themes - Note when themes reinforce or challenge each other 2. **Identify emerging patterns:** - Meta-patterns visible only across themes - Systemic insights from synthesis 3. **Challenge contradictions:** - Cross-theme conflicts require resolution - Determine if contradictions are substantive or contextual 4. **Map relationships between discoveries:** - Create conceptual map of how findings relate - Identify cause-effect chains 5. **Form unified understanding:** - Integrated narrative across all themes - Comprehensive view of the topic --- ## Error Handling Protocol When research encounters obstacles, follow this protocol: ### Empty or Insufficient Search Results 1. **Broaden query terms** โ Remove specific constraints, use synonyms 2. **Try related concepts** โ Search adjacent terminology 3. **Document the gap** โ Note when authoritative sources are scarce 4. **Adjust confidence** โ Mark findings as [LOW] or [SPECULATIVE] when source-poor ### Contradictory Sources Cannot Be Resolved 1. **Present both claims** with full context 2. **Analyze why they differ** โ methodology, time period, population 3. **Assess evidence quality** on each side 4. **Document as unresolved** if contradiction persists ### Source Quality Concerns - **No primary source available** โ Rely on secondary sources but flag limitation - **Outdated information** โ Note publication date, assess if still relevant - **Potential bias** โ Identify conflicts of interest, funding sources - **Methodology unclear** โ Flag as lower confidence when methods not described ### Technical Failures - **web_fetch fails** โ Document URL attempted, note as inaccessible source - **Rate limiting** โ Slow down, reduce search count, retry with backoff - **Memory search unavailable** โ Proceed without cross-reference, note limitation --- ## Research Standards ### Evidence Requirements - **Every conclusion must cite multiple sources** โ never rely on single source - **All contradictions must be addressed** โ document and analyze conflicts - **Uncertainties must be acknowledged** โ transparent about limitations - **Lim
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only โ no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.