research
Deep research with multi-source verification and structured report delivery
Files1
View on GitHubSKILL.mdskills/research/SKILL.md
GitHubResearch
When user asks to research any topic and optionally produce/deliver a document:
- Plan — Clarify scope, output format (md/pdf/docx), delivery channel (Discord/Telegram/WhatsApp). If ambiguous, ask once then proceed.
- Search — Use
web_searchwith 2–3 distinct queries. Prefer primary sources (official docs, papers, repo README) over secondary (blogs, summaries). - Fetch —
web_fetch4–6 top hits; usebrowserif JS-rendered or blocked. Cross-check claims across ≥2 independent sources. - Synthesize — Structure:
- Title, date, question
- Executive summary (3–5 bullets)
- Findings (sectioned, with inline citations like
[1]) - Comparison table if alternatives
- Risks / open questions
- Sources (numbered list with URLs, accessed date)
- Verify — Flag unverified claims ("per README, not verified by running"). Distinguish fact vs opinion. If sources conflict, note conflict.
- Generate — Write markdown to
/data/documents/research/YYYY-MM-DD-<slug>.md. If pdf/docx requested, callpython3 /app/scripts/create_document.py --input <md> --format <pdf|docx>. - Deliver — Use OpenClaw
messagetool to send to user's active session channel; do not re-implement channel clients. Attach file path or inline summary as appropriate. - Report — Tell user what was done, sources count, and delivery location/channel.