SN Deep Research for Openclaw

SN Deep Research orchestrates multi-agent research, evidence validation, citation rendering, and report production across quick, normal, and heavy workflows.

sensenova-skills
v2026.9.11
Sep 11, 2026
0
429
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install sn-deep-research

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install sn-deep-research using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is SN Deep Research?

SN Deep Research is a structured research orchestration skill for Openclaw Skills, designed for deep research, market analysis, competitor reviews, policy investigations, trend analysis, technical studies, fact-checking, and evidence-based reports. It coordinates scout, planning, research, review, writing, stitching, and citation-rendering agents instead of relying on a few unverified searches.

The skill uses explicit workflow modes, absolute file paths, validated JSON artifacts, source-aware evidence collection, and controlled handoffs between agents. It supports quick synthesis, parallel normal research, and a heavy audit workflow with perspectives, supplemental research, draft review, and final citation checks.

SN Deep Research Use Cases

  • Conduct deep research requiring evidence from multiple independent sources.
  • Compare competitors, products, technologies, policies, markets, or pricing.
  • Produce research reports, white papers, industry analyses, investigative documents, or structured memos.
  • Verify current regulations, policies, market conditions, product details, prices, and time-sensitive facts.
  • Run technical or academic research with source categories, freshness requirements, and scope ownership.
  • Use a fast single-dimension workflow for focused research tasks.
  • Use parallel research dimensions when the topic can be divided into independent work packages.
  • Perform high-risk or controversial research that needs review, perspective coverage, gap analysis, and supplemental evidence.

How SN Deep Research Works

  1. Detect whether the request requires deep research, cross-source verification, comparison, investigation, or a formal report; simple summaries and single-source整理 tasks are excluded.
  2. Detect mandatory capabilities for file I/O, command execution, web search, and webpage retrieval. The workflow pauses if any required capability is unavailable.
  3. Establish the request-level language, format, confirmed scope, and workflow mode: quick, normal, or heavy.
  4. Create a uniquely named report directory using the date, topic, and random hexadecimal run identifier, then write request.md and initialize progress tracking.
  5. Start the Research Workbench at the root research route and publish progress events for each major stage.
  6. In quick mode, dispatch one research agent, generate a single evidence artifact, synthesize it with one writer, and render the final report.
  7. In normal mode, dispatch a planning agent, split the topic into independent dimensions, run research agents in parallel, combine all evidence, and write one complete draft.
  8. In heavy mode, run scouting, planning, parallel research, evidence reviews, perspective checks, supplemental research planning, content-unit planning, writing, stitching, and final-draft review.
  9. Pass large content through absolute file paths rather than embedding large documents in agent messages. Every payload explicitly includes the original query, language, format, scope, and output paths.
  10. Validate required artifacts and retry only according to the documented stage limits. Invalid or missing artifacts stop downstream execution.
  11. Render the final source-backed document with citation preparation, deduplicated footnotes, report.md, and citations.json. Orphan citations and unresolved claim identifiers block delivery.

SN Deep Research Setup

  1. Install or enable the SN Deep Research skill in the OpenClaw skills directory, then resolve the actual skill directory exposed by the runtime. OpenClaw uses the {baseDir} placeholder; replace it with the resolved absolute path.
  2. Ensure the runtime provides file read/write, command execution, web search, and webpage-fetching capabilities. These are mandatory for reliable research.
  3. Configure optional credentials in the repository root .env file or through the runtime environment. Do not place secrets in payloads, command-line arguments, reports, logs, or transcripts.
  4. Create a unique report workspace before dispatching agents:
run=$(openssl rand -hex 2 2>/dev/null || printf '%04x' "$RANDOM")
report_dir="$PWD/deep-research-reports/$(date +%F)-{topic}-$run"
mkdir -p "$report_dir"/sub_reports "$report_dir"/board "$report_dir"/sections "$report_dir"/content_units
echo "$report_dir"
  1. Write the original request and start progress tracking before research artifacts are generated. The shared helper is located under the plugin skills directory:
python3 {plugin_skills_dir}/sn-ppt-standard/scripts/progress_event.py \
  --deck-dir "$report_dir" \
  --workflow deep-research \
  --stage mode-selection \
  --status running \
  --artifact request.md \
  --label "Research workflow started"
  1. Launch the required Research Workbench:
python3 {plugin_skills_dir}/sn-ppt-standard/scripts/launch_workbench.py \
  --deck-dir "$report_dir" \
  --product research \
  --progress-route / \
  --source-session-id "${HERMES_SESSION_KEY:-}" \
  --agent-managed 1 \
  --require-webui \
  --host 0.0.0.0
  1. For Windows systems without python3, use python. In Git Bash or MSYS, prefix the command with MSYS_NO_PATHCONV=1 when passing the / route.
  2. Render the final report after the selected workflow completes:
python3 {plugin_skills_dir}/sn-prepare-citations/scripts/prepare_citations.py \
  --report {report_dir}/stitched.md \
  --evidence {report_dir}/sub_reports/d*.evidence.json \
  --outline {report_dir}/outline.json \
  --no-l0 \
  --output {report_dir}/report.md

For quick and normal, use sections/s_full.md as the --report input and omit --outline. Optional credentials include SN_IMAGE_GEN_API_KEY, SN_API_KEY, platform cookies, TIKHUB_TOKEN, YOUTUBE_API_KEY, GitHub credentials, HF_TOKEN, SO_API_KEY, and academic API keys. Missing optional credentials reduce coverage or increase rate-limit risk but do not necessarily stop the workflow.

SN Deep Research Data Schema & Taxonomy

All artifacts live under one uniquely named absolute report directory:

Artifact Purpose Modes
request.md Original request and start context All
.workbench/progress.json Live workflow state All
briefing.json Scout findings and heavy-mode briefing Heavy
plan.json Research dimensions, work packages, lenses, and mode Normal, Heavy
sub_reports/dN.evidence.json Dimension-level facts, claims, sources, and evidence status All research modes
sub_reports/dN.review.md Evidence review findings and gaps Heavy
sub_reports/dN.perspectives/ Lens-based coverage checks Heavy
sub_reports/dN.supplement_plan.json Planned follow-up research items Heavy
outline.json Content units and organization decisions Heavy
content_units/uN.evidence_subset.json Evidence assigned to a content unit Heavy
content_units/uN.md Draft or revised content unit Heavy
sections/s_full.md Complete quick or normal draft Quick, Normal
stitched.md Assembled heavy-mode draft Heavy
report.md Final rendered report All
citations.json Deduplicated citation metadata All

Metadata and routing conventions include:

  • Report directories follow YYYY-MM-DD-{topic}-{hex4} to prevent collisions between repeated runs.
  • Research dimensions use stable IDs such as d1, d2, and d3; quick mode uses d1.
  • Heavy-mode content units use IDs such as u1 and receive bounded evidence subsets.
  • Every source record preserves its original URL and is selected according to a source category.
  • language and format are request-level runtime parameters passed to every child agent; they are not stored as separate state files.
  • mode determines the pipeline: quick uses research plus writer, normal uses plan plus parallel research plus writer, and heavy uses the complete audited pipeline.
  • Evidence must record unresolved gaps honestly, including partial, no_data, or out_of_scope conditions.
  • Citation rendering checks for orphan citations and unresolved claim identifiers such as [^dN.cM] before delivery.

SN Deep Research Advanced Features

  • Three explicit workflow modes let users balance speed, parallelism, and audit depth without lowering evidence standards.
  • Multi-agent orchestration assigns specialized roles for scouting, planning, research, reviewing, perspective analysis, supplemental research, writing, stitching, and rendering.
  • Parallel dimension research reduces duplicated searches while preserving clear scope ownership.
  • Heavy mode supports lens-based perspective coverage, evidence-gap detection, supplemental research plans, and final-draft review.
  • Strict payload contracts require absolute paths, original queries, language, format, output locations, and role instructions.
  • File-based agent communication prevents large evidence and draft documents from being copied into messages.
  • JSON schemas and validators gate briefing, planning, evidence, supplement plans, and final citation output.
  • Retry routing is stage-specific and bounded, preventing infinite loops and preventing invalid artifacts from reaching downstream agents.
  • Progress WebUI integration exposes research stages such as mode selection, scouting, planning, research, review, writing, finalization, and completion.
  • Source credentials are environment-based, keeping API keys, cookies, and tokens out of reports and transcripts.
  • Format-aware reporting supports reports, papers, tables, memos, and user-defined output labels rather than imposing a fixed document structure.
  • Citation preparation deduplicates footnotes, generates numbered citations, and blocks delivery when citation integrity checks fail.
  • Openclaw Skills users can reuse the same evidence-first lifecycle for market intelligence, policy research, technical analysis, and fact verification.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*