Token导航 LogoToken导航TokenDH.com
研究检索只读clawhub未标认证来源可访问clear审计通过

desk-research案头研究

Agent Skill

desk-research 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

5,010

周安装

213

GitHub Stars

公开资料未说明

下载量

1,755
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:desk-research(案头研究)
来源仓库:https://github.com/draco-kzn/desk-research
安装命令:
openclaw skills install desk-research
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install desk-research

简介

用于查找、检索和筛选相关信息。desk-research 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

  • 适合在 OpenClaw 中根据关键词或任务场景快速定位候选结果。
  • 可针对市场、公司、政策等问题进行结构化案头研究。
  • 使用时需结合来源仓库和原始 README 核验具体用法。
  • 安装前建议确认权限范围和维护状态,注意可能触发联网或命令执行。

SKILL.md

name
desk-research
description
Structured desk research workflow for market, company, policy, product, and competitor questions. Use when a user asks for secondary research, landscape scans, evidence-based summaries, source triangulation, or insight synthesis from public information.

Desk Research

Execute this workflow for any desk-research request.

0) Load methodology checklist (first)

Read references/methodology.md, references/deep-writing-patterns.md, and references/quality-checklist.md and apply all as guardrails.

1) Define the research brief

Write 4 lines before searching:

  • Research question (1 sentence)
  • Scope (time, geography, industry)
  • Must-answer sub-questions (3-6 bullets)
  • Output format needed by user

If the question is vague, propose assumptions explicitly and continue.

2) Build a source plan

Collect evidence in this priority order:

  1. Primary/official sources (government, regulator, company filings, product docs)
  2. Reputable secondary analysis (major research firms, established media)
  3. Community signals (forums/social) only as supporting evidence

Require at least 2 independent sources for every key claim.

3) Gather evidence fast

For each sub-question:

  • Find 3-8 candidate sources
  • Keep the highest-signal sources
  • Extract only claim + evidence + date + link

Reject sources that are undated, anonymous, or purely opinionated unless the user asked for sentiment.

4) Score source reliability

Tag each source:

  • A = official primary source
  • B = credible secondary source
  • C = weak/indicative source

When claims conflict, prefer newer A/B sources and explicitly note uncertainty.

5) Synthesize insights

Convert notes into:

  • Facts (well-supported)
  • Interpretations (reasoned but inferential)
  • Unknowns (gaps needing validation)

Never present interpretation as fact.

Source hard rule (critical)

For all final research outputs:

  • Every major factual claim must include source + date.
  • Every key viewpoint, analytical framework, stage model, or category split must either:

1. cite a source, or 2. be explicitly labeled as the report author's synthesis / working model.

  • Do not present an unsupported framework as if it were an established industry fact.
  • If a conclusion combines multiple sources, cite the main supporting sources inline or in the same paragraph.

5.5) Deepening loop (mandatory)

Before final delivery, run at least 2 rounds of self-questioning:

Round A — Coverage challenge

  • What did I miss by source type, time window, or geography?
  • Which category/conclusion is over-dependent on one source?
  • What contradicts my current conclusion?

Round B — Decision challenge

  • If this conclusion is wrong, what evidence would prove it wrong?
  • Which part is descriptive but not decision-useful?
  • What next data pull would most change the recommendation?

After each round, update findings and confidence.

6) Deliver in concise structure

Use this exact section order:

  1. Core Questions (2 questions)
  2. One-sentence Verdict
  3. Executive Summary (5-8 bullets)
  4. Key Findings by sub-question (with metric anchors)
  5. Evidence Table (claim | source | date | reliability)
  6. Confidence tags (High/Medium/Low per major claim)
  7. Risks / Uncertainty
  8. What would falsify this conclusion
  9. Next Verification Steps / Todo

Inline citation rule:

  • In the body, append source/date after key claims whenever it helps verification.
  • For analytical frameworks or stage models, add Source: or Author synthesis based on: explicitly.
  • Do not leave major frameworks floating without attribution.

For output shape and compact template, use references/output-template.md.

7) Quality bar before sending

Check all items:

  • Every major claim has source/date
  • No single-source critical claim
  • Time/geography scope matches user ask
  • Clear separation of fact vs interpretation
  • Actionable takeaway included
  • Each promising case uses the full 9-part deep case framework
  • Each promising case includes one final case-summary paragraph: what it does / who pays / business model / why pay
  • Each key section ends with decision implication (so-what)

8) Case-depth hard rule (for startup/case research)

When the task is startup/use-case research, apply these hard requirements:

  • For each promising case, collect at least 3 website evidence snippets (feature/pricing/use-flow)
  • Add at least 1 metric anchor from trusted dataset (revenue/MRR/growth)
  • Include at least 1 risk point and 1 falsification condition
  • Do not submit if any case is only descriptive without judgment

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

86.27%
按下载量换算1,514

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills